Skip to content
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.

create web access to api docs #15

Closed
2 tasks
zippy opened this issue Jun 15, 2018 · 9 comments
Closed
2 tasks

create web access to api docs #15

zippy opened this issue Jun 15, 2018 · 9 comments

Comments

@zippy
Copy link
Member

zippy commented Jun 15, 2018

child of #117

As an container developer and as a core developer, I want web access to rust library documentation, so as to be able to understand and navigate the codebase easily.

cargo doc builds all the docs and puts them into the target directory which is (rightfully) ignored in .gitignore

  • setup github pages on this repo (or other solution) to serve the api docs.
  • create a build script for release (maybe in travis) that deploys the docs build
@zippy zippy changed the title create github pages access to api docs create web access to api docs Jun 15, 2018
@thedavidmeister
Copy link
Contributor

@zippy IIRC, any lib that is pushed to crates.io automatically gets docs built and available at https://docs.rs/

in that case, #18 could kill two birds with one stone :)

@thedavidmeister
Copy link
Contributor

alternatively there is a section in this tutorial explaining gh pages support - https://medium.com/@Razican/continuous-integration-and-code-coverage-report-for-a-rust-project-5dfd4d68fbe5

@Connoropolous
Copy link
Collaborator

Unless we choose to change this around, the github pages for holochain-rust repo is now occupied by the MDBOOK build... so we may have to create a different repo and do the build scripts to that repo to use github pages to host the API docs

@Connoropolous
Copy link
Collaborator

As discussed in other places, the alternative to this issue is to start shipping holochain-rust into crates.io, which would generate and host the API docs out-of-the-box. Seems like a big win.

How soon (if approved) can we do this? Starting to see how those docs look like, and start to polish them seems very important and generative

@thedavidmeister
Copy link
Contributor

@Connoropolous i am for pushing to crates.io ASAP. handle expectations of maturity through versioning/comms, not avoiding publishing. Everything is public on github now.

but...

@zippy @sphinxc0re @AshantiMutinta @lucksus @ddd-mtl need to input into this decision.

if it's not controversial, let's 🚢

if someone wants to wait, then we'll need to plan that wait... ADR? trello?

@Connoropolous
Copy link
Collaborator

Great to hear @thedavidmeister, I am curious to hear others thoughts

@StaticallyTypedAnxiety
Copy link
Contributor

You can go no wrong with crates.io, if that is everyone's first choice for obtaining packages, I would say why not. We should definitely pursue it

@jamesray1
Copy link
Contributor

@thedavidmeister
Copy link
Contributor

ooooh yes!

check this out https://docs.rs/crate/holochain/0.0.38-alpha13

that's awesome :D

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants