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

feat: inital mdbook docs for rust-ceramic #282

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

3benbox
Copy link
Collaborator

@3benbox 3benbox commented Mar 6, 2024

Checkout the branch, change to the ./rust-ceramic directory and run mdbook serve --open to view the contents.

Took the same directory name as kermaik, happy to move it if it's confusing.

Closes WS1-1515

@3benbox 3benbox requested review from smrz2001 and nathanielc March 6, 2024 13:58
Copy link

linear bot commented Mar 6, 2024

@3benbox 3benbox temporarily deployed to github-tests-2024 March 6, 2024 14:07 — with GitHub Actions Inactive
Copy link
Collaborator

@nathanielc nathanielc left a comment

Choose a reason for hiding this comment

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

Looking good a few comments:

  • I think we should name the directory simply book I find the redundant name confusing
  • I want to make sure these docs are not immediately out of date as soon as we create them. To me that means either a) automate generating some content from the source (i.e. the help text) or b) Do not include any content that is already part of the binary but instead simply refer to it so it can't get out of sync. I would prefer option a but its more work so we can build up to that.
  • How does this work in CI?
    • Does this get deployed as a Github Pages book?
    • Can we add a Makefile target to build the book?
    • Is the book directory the generated content? If so can we add a Makefile target to check its been generated correctly like we do for the api server crates?

rust-ceramic/src/SUMMARY.md Outdated Show resolved Hide resolved
rust-ceramic/src/license.md Outdated Show resolved Hide resolved
rust-ceramic/src/source.md Outdated Show resolved Hide resolved
rust-ceramic/src/docker.md Outdated Show resolved Hide resolved
rust-ceramic/src/usage.md Outdated Show resolved Hide resolved
rust-ceramic/src/configuration.md Outdated Show resolved Hide resolved
- `ceramic_store_value_insert_count_total`: Total number of values inserted into the store
- `ceramic_store_store_query_durations_[sum, buckets, count]`: Store query durations
- `ceramic_api_request_durations_[sum, buckets, count]`: API request durations
- `ceramic_api_api_info`: Information about the Ceramic API
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should we note that there are many more metrics and encourage operators to explore them via the /metrics endpoint? We can highlight these as the important ones but this is not an exhaustive list.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, like the "help" I'd love a way to generate the metrics for the docs.

I don't see a way outside parsing all the source files.

Do you have any ideas how to make a rust command, or entrypoint, that would print the available metrics?

rust-ceramic/src/help.md Outdated Show resolved Hide resolved
@3benbox 3benbox temporarily deployed to github-tests-2024 March 14, 2024 15:54 — with GitHub Actions Inactive
@3benbox 3benbox temporarily deployed to github-tests-2024 March 14, 2024 16:31 — with GitHub Actions Inactive
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