profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/johndmulhausen/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

filecoin-project/filecoin-docs 106

Filecoin Docs

johndmulhausen/gdocs2md 2

Convert a Google Drive Document to the Markdown format, suitable for publishing.

digitalocean/oneclick-quickstarts 1

Contains the code that runs on our One-Click Quickstart Droplet images

digitalocean/katacoda-scenarios 0

Contains source for Katacoda scenarios, which are interactive tutorials with embedded terminals

johndmulhausen/cli 0

The Docker CLI

johndmulhausen/clusterlint 0

A best practices checker for Kubernetes clusters. 🤠

johndmulhausen/CodeRay-GitHub-Theme 0

A stylesheet for the CodeRay syntax highlighter - github style.

johndmulhausen/commonjs-javascript-yaml-parser 0

CommonJS implementation of the javascript-yaml-parser

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 5f01dbe27f8df35ce5f5d953da9f37bac98fe09f

New stuff

view details

push time in 24 days

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 41cd551c2b1c2be23676d675639ecb5615f13946

Google analytics

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 5fcc9cc4124dc8a1ef9daa3cdc2d582f1d49e69d

kermit reword

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha d0af66450d51c46e3cfa90c1e369604ab8829bf4

cryptoad > toad.png

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha ee2116c27898285dac7d2fb797d6ce87bc83ddc8

ribbit

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 5b30073271ddb8f321b87b0256d4b90f6328d59d

project detail fixes

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 6b2728174cf42fe77c1ebd82ea53987f8bade4cc

meh

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 8789d044b7706696b7a863f309446c0fb5f891fb

Better metadata

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha e5e6b6d38e172969ea466df288bd930b44691bca

metadata

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 3082cd218386113c50657ece3d731f74ec45ea08

opacity

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 7137a25c7d2b5650b4df7a993187d67af76c5952

Project detail pages

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

johndmulhausen

commit sha 42182d767e3d96e30ab7a95f2f1d7e64e9b573b7

Progress

view details

push time in a month

push eventjohndmulhausen/johndmulhausen.github.io

John Mulhausen

commit sha 0d458e60e3995d6248c6bed6be3d94c19f7d73f9

Create CNAME

view details

push time in a month

push eventjohndmulhausen/artbad.golf

John Mulhausen

commit sha dc9464e5d019ef0a9871b3fd6c4b0a9dfdbc1001

Delete CNAME

view details

push time in a month

create barnchjohndmulhausen/artbad.golf

branch : master

created branch time in a month

created repositoryjohndmulhausen/artbad

created time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha 4d4b57bb25ec9249d68c0be0c1c15964656bbcd9

HTTP API Reference Docs: ReDoc + schema (#152) Co-authored-by: Yusef Napora <yusef@napora.org> Co-authored-by: Jessica Schilling <jessica@protocol.ai> Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

delete branch web3-storage/docs

delete branch : http-api-redoc

delete time in a month

PR merged web3-storage/docs

HTTP API Reference Docs: ReDoc + schema

See: https://bafybeie7ay5jhqgbk2j3lrmmh743dyiz7ujzx6mmllc73iilvvyfupvlma.on.fleek.co/http-api.html

Writing much of spec from scratch using https://github.com/web3-storage/web3.storage/blob/main/packages/api/src/index.js as a basis.

+634 -22

3 comments

5 changed files

johndmulhausen

pr closed time in a month

Pull request review commentweb3-storage/docs

HTTP API Reference Docs: ReDoc + schema

+openapi: '3.0.2'+info:+  title: Web3.Storage API+  description: |+    This documentation describes the HTTP API for [**Web3.Storage**](https://web3.storage), which allows you to quickly and easily build applications using decentralized data storage persisted by [Filecoin](https://filecoin.io) and available over [IPFS](https://www.ipfs.io).+    +    You can also interact with this API using client libraries. See [**docs.web3.storage**](https://docs.web3.storage) for more information on using a client library, as well as a variety of other guides and how-tos for Web3.Storage as a whole.+  version: '1.0'++servers:+  - url: https://api.web3.storage++tags:+  - name: Web3.Storage HTTP API+paths:+  /upload:+    post:+      tags:+        - Web3.Storage HTTP API+      summary: Upload and store one or more files+      description: |+        Store a file using Web3.Storage. You can upload either a single file or multiple files in a directory.++        Send the POST request with one of the following:+        - a single file, with a single blob/file object as the body+        - multiple files, as `FormData` with `Content-Disposition` headers for each part to specify filenames and the request header `Content-Type: multipart/form-data`++        You can also upload a Content Addressed aRchive ([CAR](https://ipld.io/specs/transport/car/)) file by setting the request body as a single CAR blob/file object and providing the request header `Content-Type: application/car`. Providing a CAR file allows you to pre-compute the root CID for one or more files, and ensures that Web3.Storage will store and provide your assets with the same CID.+      operationId: store-multipart+      requestBody:+        required: true+        content:+          multipart/form-data:+            schema:+              type: object+              properties:+                file:+                  type: array+                  items:+                    type: string+                    format: binary+      responses:+        '200':+          description: OK+          content:+            'application/json':+              schema:+                $ref: '#/components/schemas/UploadResponse'+        '400':+          $ref: '#/components/responses/badRequest'+        '401':+          $ref: '#/components/responses/unauthorized'+        '403':+          $ref: '#/components/responses/forbidden'+        '5XX':+          $ref: '#/components/responses/internalServerError'+  /user/uploads:+    get:+      tags:+        - Web3.Storage HTTP API+      summary: List previous uploads+      description: |+        Lists all previous uploads for the account associated with the API token being used to make the call to `/user/uploads`. These results can be paginated by specifying `before` and `limit` parameters in the query string, using the date associated with the oldest file returned in each batch as the value of `before` in subsequent calls.++        The information returned includes the creation date and file size, as well as details about how the network is storing your data. Using this information, you can identify peers on the [IPFS (InterPlanetary File System)](https://ipfs.io) network that are pinning the data, and [Filecoin](https://filecoin.io) storage providers that have accepted deals to store the data.+      operationId: list+      parameters:+        - $ref: '#/components/parameters/before'+        - $ref: '#/components/parameters/limit'+      responses:+        '200':+          description: OK+          content:+            'application/json':+              schema:+                $ref: '#/components/schemas/ListResponse'+        '401':+          $ref: '#/components/responses/unauthorized'+        '403':+          $ref: '#/components/responses/forbidden'+        '5XX':+          $ref: '#/components/responses/internalServerError'+  /status/{cid}:+    get:+      tags:+        - Web3.Storage HTTP API+      summary: Retrieve information about an upload+      description: Retrieve metadata about a specific file by using `/status/{cid}`, supplying the CID of the file you are interested in. This metadata includes the creation date and file size, as well as details about how the network is storing your data. Using this information, you can identify peers on the [IPFS (InterPlanetary File System)](https://ipfs.io) network that are pinning the data, and [Filecoin](https://filecoin.io) storage providers that have accepted deals to store the data.+      operationId: status+      parameters:+        - name: cid+          in: path+          required: true+          schema:+            $ref: '#/components/schemas/CID'+      responses:+        '200':+          description: OK+          content:+            'application/json':+              schema:+                $ref: '#/components/schemas/GetResponse'+        '401':+          $ref: '#/components/responses/unauthorized'+        '403':+          $ref: '#/components/responses/forbidden'+        '5XX':+          $ref: '#/components/responses/internalServerError'+  /user/uploads/{cid}:+    delete:+      tags:+        - Web3.Storage HTTP API+      summary: Stop storing the specified content+      description: |+        Stop storing content on Web3.Storage by using `/user/uploads/{cid}`, supplying the CID of the file you wish to stop storing. This has the following effects:+        - Unpins the item from Web3.Storage's underlying IPFS pinning service.+        - Ceases renewals for expired Filecoin deals involving the CID.++        ⚠️ **IMPORTANT! While this stops storing the content, it does NOT guarantee removal of the content from the network.** More specifically:+        - It does not terminate any established Filecoin deal.+        - It does not remove the content from other IPFS nodes in the network that already cached or pinned the CID.++        **The content will remain available if another user has stored the CID with Web3.Storage**.+      operationId: delete+      parameters:+        - name: cid+          in: path+          required: true+          schema:+            $ref: '#/components/schemas/CID'+      responses:+        '200':+          description: OK+          content:+            'application/json':+              schema:+                $ref: '#/components/schemas/DeleteResponse'+        '401':+          $ref: '#/components/responses/unauthorized'+        '403':+          $ref: '#/components/responses/forbidden'+        '5XX':+          $ref: '#/components/responses/internalServerError'+  /car:+    post:+      tags:+        - Web3.Storage HTTP API+      summary: Upload a CAR+      description: |+        Upload a [CAR](https://ipld.io/specs/transport/car/) (Content Addressable aRchive) file and store the [IPFS DAG](https://docs.ipfs.io/concepts/merkle-dag/)+        (Directed Acyclic Graph) it contains. This supports partial DAGs, so multiple+        CAR files with the same root but with different sub-trees can be sent. +        +        Note that only one CAR can be uploaded at a time, and only CAR files are accepted. This is in contrast to [`/upload`](#operation/store-multipart), which can upload multiple files at once and accepts both CAR files and files from the client.+      operationId: store-car+      requestBody:+        required: true+        content:+          application/car:+            schema:+              type: string+              format: binary+          application/octet-stream:+            schema:+              type: string+              format: binary+      responses:+        '200':+          description: OK+          content:+            'application/json':+              schema:+                $ref: '#/components/schemas/UploadResponse'+        '400':+          $ref: '#/components/responses/badRequest'+        '401':+          $ref: '#/components/responses/unauthorized'+        '403':+          $ref: '#/components/responses/forbidden'+        '5XX':+          $ref: '#/components/responses/internalServerError'+  /car/{cid}:+    get:+      tags:+        - Web3.Storage HTTP API+      summary: Retrieve information about a CAR+      description: Retrieve metadata about a CAR file by using `/car/{cid}`, supplying the CID of the CAR file you are interested in. This metadata includes the creation date and file size, as well as details about how the network is storing your data. Using this information, you can identify peers on the [IPFS (InterPlanetary File System)](https://ipfs.io) network that are pinning the data, and [Filecoin](https://filecoin.io) storage providers that have accepted deals to store the data.+      operationId: car-cid+      parameters:+        - name: cid+          in: path+          required: true+          schema:+            $ref: '#/components/schemas/CID'+      responses:+        '200':+          description: OK+          content:+            'application/json':+              schema:+                $ref: '#/components/schemas/GetResponse'+        '401':+          $ref: '#/components/responses/unauthorized'+        '403':+          $ref: '#/components/responses/forbidden'+        '5XX':+          $ref: '#/components/responses/internalServerError'+    head:+      tags:+        - Web3.Storage HTTP API+      summary: Retrieve HTTP headers regarding a CAR+      description: |+        This method is useful for doing a dry run of a call to `/car/{cid}`. Because it only returns HTTP header information, it is far more lightweight and can be used to get only the metadata about the given CAR file without retrieving a whole payload in the body of the HTTP response.+      operationId: head-car+      requestBody:

I'm not sure what that tool is but it should be finding the description for CIDs based on $ref: '#/components/schemas/CID' being in the schema -- no need to override the great description that's there or to veer from using a single source of truth.

johndmulhausen

comment created time in a month

PullRequestReviewEvent

push eventweb3-storage/docs

johndmulhausen

commit sha 5be9fe3c8265d0819a74906e6253750694c78508

Re-ordering to emphasize CAR

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha f9e6801c9f9888d11c801e652449cf9402848ae0

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha 0ad6b0cdf6f8defdcad7d2e43a41677c5d59817b

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha 1315ffb13bfb00be23adad31883c3de07781f71c

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha 545de12ed6eeb0f87f785fb85bb75710ecc3ede3

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha cf12d8e0777621a3f0b091a38f7900ea90c00e09

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha 566cb28b275fa0fd1d965ba373e79398ed4c6773

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha b2226fa28f7399ad2e675a0b9d16f5487e95098e

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month

push eventweb3-storage/docs

John Mulhausen

commit sha fb5179bc6d68f269ea3d2a9fd01df37b7f5a4b49

Update docs/.vuepress/public/schema.yml Co-authored-by: Alan Shaw <alan.shaw@protocol.ai>

view details

push time in a month