Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update main readme for new devs. #1119

Merged
merged 2 commits into from
Nov 14, 2023
Merged

docs: update main readme for new devs. #1119

merged 2 commits into from
Nov 14, 2023

Conversation

olizilla
Copy link
Contributor

Create a terse, developer focused "just show me" style readme for the main landing page of the w3up repo. this does not attempt to explain everything, just to show, with as little overhead as possible, how to do the basics with the new api.

previous readme was more of contributing guide so move it there per https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors#adding-a-contributing-file

License: MIT

Create a terse, developer focused "just show me" style readme for the main landing page of the w3up repo.

previous readme was more of contributing guide so move it there per https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors#adding-a-contributing-file

License: MIT
Signed-off-by: Oli Evans <oli@protocol.ai>
@olizilla olizilla merged commit 59cf925 into main Nov 14, 2023
@olizilla olizilla deleted the main-readme branch November 14, 2023 13:40

## Usage

Store your files with web3.storage and retrieve them via their unique Content ID. Our tools make it simple to hash your content locally, so you can verify the service only ever stores the exact bytes you asked us to. Pick the method of using with web3.storage that works for you!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Store your files with web3.storage and retrieve them via their unique Content ID. Our tools make it simple to hash your content locally, so you can verify the service only ever stores the exact bytes you asked us to. Pick the method of using with web3.storage that works for you!
Store your files with web3.storage and retrieve them via their unique Content ID. Our tools make it simple to hash your content locally, so you can verify the service only ever stores the exact bytes you asked us to. Pick the method of using web3.storage that works for you!


// lets go!
const files = await getFilesFromPaths(process.env.PATH_TO_ADD)
const cid = await client.put(files)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
const cid = await client.put(files)
const cid = await client.uploadDirectory(files)


### Command Line

Install [`@web3-storage/w3cli`](https://github.com/web3-storage/w3cli#readme) globally and save your api token then add your files to web3! It calculates the root CID for your files locally before sending them to web3.storage.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Install [`@web3-storage/w3cli`](https://github.com/web3-storage/w3cli#readme) globally and save your api token then add your files to web3! It calculates the root CID for your files locally before sending them to web3.storage.
Install [`@web3-storage/w3cli`](https://github.com/web3-storage/w3cli#readme) globally and save your API token then add your files to web3! It calculates the root CID for your files locally before sending them to web3.storage.

Comment on lines +59 to +66
# verify your email
$ w3 authorize alice@example.com

# create a Space, a DID namespace for your files... like a bucket.
$ w3 space create Documents

# defaults to registering you with web3.storage
$ w3 space register
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# verify your email
$ w3 authorize alice@example.com
# create a Space, a DID namespace for your files... like a bucket.
$ w3 space create Documents
# defaults to registering you with web3.storage
$ w3 space register
# verify your email
$ w3 login alice@example.com
# create a Space, a DID namespace for your files... like a bucket.
$ w3 space create Documents


All welcome! web3.storage is open-source. See the [contributing guide](./CONTRIBUTING.md)

This project uses node v18 and `pnpm`. It's a monorepo that use [pnpm workspaces](https://pnpm.io/workspaces) to handle resolving dependencies between the local [`packages`](https://github.com/web3-storage/w3up/tree/main/packages)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This project uses node v18 and `pnpm`. It's a monorepo that use [pnpm workspaces](https://pnpm.io/workspaces) to handle resolving dependencies between the local [`packages`](https://github.com/web3-storage/w3up/tree/main/packages)
This project uses node v18 and `pnpm`. It's a monorepo that uses [pnpm workspaces](https://pnpm.io/workspaces) to handle resolving dependencies between the local [`packages`](https://github.com/web3-storage/w3up/tree/main/packages)

olizilla added a commit that referenced this pull request Nov 14, 2023
applies fixes raised in #1119

License: MIT
Signed-off-by: Oli Evans <oli@protocol.ai>
@olizilla olizilla mentioned this pull request Nov 14, 2023
olizilla added a commit that referenced this pull request Nov 14, 2023
applies fixes raised in #1119

License: MIT

Signed-off-by: Oli Evans <oli@protocol.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants