You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the DebOps documentation located at http://docs.debops.org/ is built using this repository and git submodules. Unfortunately, this presents two problems:
with more and more submodules, build time is getting longer. Eventually we will hit the limit on https://readthedocs.org/
Recently, documentation management was improved by adding a separate bot that updates the git repository with submodules and pushes the changes back. What if, instead, the bot would get all the changes in different repositories (basically what is done right now) and copied them to a new, separate repository, say debops/debops-doc. Then this single repository could be used as the base for documentation located at http://docs.debops.org/ as well as be easily packaged. This could probably be done with preserved git history as well.
The text was updated successfully, but these errors were encountered:
This is related to #91 but since upstream has not addressed the issue yet I think we can ignore it. There should be a more flexible way to specify links to the source file.
At the moment, the DebOps documentation located at
http://docs.debops.org/
is built using this repository and git submodules. Unfortunately, this presents two problems:git
repositoriesRecently, documentation management was improved by adding a separate bot that updates the
git
repository with submodules and pushes the changes back. What if, instead, the bot would get all the changes in different repositories (basically what is done right now) and copied them to a new, separate repository, saydebops/debops-doc
. Then this single repository could be used as the base for documentation located at http://docs.debops.org/ as well as be easily packaged. This could probably be done with preserved git history as well.The text was updated successfully, but these errors were encountered: