Adjusting fuel-web/docs to build ONLY the API and Objects reference is here:
https://review.openstack.org/147348
Meg should have the inclusion of fuel-web/docs content in fuel-docs tomorrow.
Once these two are done, we can sort out that last step:
>> And finally we will have CI job to publish fin
Ah I got it, I hadn't really considered how much more likely the
requirements are to change for nailgun and the other components that
should have auto-generated API docs. Having those build completely
separately matches OpenStack proper too - I'm on board now :) We can
work out the details over t
There are different types of dependencies:
docs dependencies like sphinx, plantuml and so on are rarely changed
so we can create environment on a slave during slave deployment phase
and keep it there. But nailgun dependencies for example can be changed
at any time, thus we need to update the envir
I think it's worth pursuing these efforts to include the
auto-generated doc components in the fuel-docs build process. The
additional dependencies required to build nailgun are not so
unreasonable, and the preparation of the build environment has already
been put into a single script,
>From the C
Blueprint
https://blueprints.launchpad.net/fuel/+spec/fuel-dev-docs-merge-fuel-docs
suggests us to move all documentation from fuel-web to fuel-docs
repository.
While I agree that moving Developer Guide to fuel-docs is a good idea,
there is an issue with autodocs which currently blocks the whole
