At Teracy, all our documentations are written with the help from sphinx¹. It’s easy to setup and manage. However, we could not find a good enough deployment solution for sphinx documentation project. What does “good enough” here means? It means:

• The installation and configuration should be easy with git and command line.

• The deployment could be “decoupled” from sphinx project for easy upgrade and maintenance. It’s better if we could have this deployment solution provided by sphinx out of the box.

• The deployment should support as many services as possible: github pages ², Rsync³, and PaaS⁴ services like heroku⁵, etc.

• The usage should be easy like:

  • $ make setup to setup deployment basing on the configurations
  • $ make generate to generate content basing on the configurations
  • $ make deploy to deploy the project basing on the configurations

We could not find a solution good enough meeting our requirements, so we created sphinx-deployment project that implements the ideas and requirements above.

Currently, it’s on very very early development stage to just support deployment on github pages automatically with travis-ci⁶, and https://travis-ci.org/teracy-official/dev as an example.

There are many things that we need to do, please help use to shape the project’s future by contributing with forking, hacking and pull requests or giving your ideas. Your contributions are all welcome. Please head to the development branch at https://github.com/teracy-official/sphinx-deployment/tree/develop

Have a nice day and happy hacking!