-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Break out docs into own repo #46
Comments
It was attempted but we weren't able to get the build on readthedocs.org to work with the custom install location - the import of functions.py for the functions doc generation depends on the virtualenv used to build the docs being able to import it and the install fails (due to /opt/graphite not being writable). Definitely still something we want to do, it's just going to have to wait until we either decide to stop installing in /opt/graphite by default (possible but not yet discussed) or come up with a patch for readthedocs to allow the appropriate options to be passed to pip/setup.py |
I think it's a great idea, but surprise, there be yaks. From my perspective, the layers are:
|
I'd also still love to see this happen. There are few docs experts among the core team so I'm not optimistic this will happen before 1.0.0, but I'm holding out hope for the next release after. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I suggested this when the Great Github Move happened. I recall agreement that it was a good idea.
Either it got forgotten, is yet to be done but planned, or was decided not to be done.
This issue is for that.
The text was updated successfully, but these errors were encountered: