Mike Fletcher  committed d0791e1

Split out the daemon docs, though they're still quite minimal

  • Participants
  • Parent commits 14b9517

Comments (0)

Files changed (2)

File docs/main/Deployment/Apache.rst

 * you are responsible for keeping your TurboGears process running, starting
   it at boot, and generally making sure that it can receive the requests
-  from the Apache server.  You may need to create an `Upstart`_ or `Sys-V Init`
-  script to kick off your TurboGears process, or you may wish to use a
-  service such as `supervisord`_ to monitor and restart your application.
+  from the Apache server.  See :ref:`deploy_daemon`.
 * You can run the TurboGears process as any user you like, and you can even
   run it in a "screen" session during development
 * You can easily restart the TurboGears process

File docs/main/Deployment/Daemon.rst

 Deploying as a Service/Daemon
-If want to use TurboGears standalone (or behind a proxy like Apache's mod_proxy),
+If want to use TurboGears standalone (i.e. use the Paste web server as your
+primary web-server), or behind a proxy, such as
+:ref:`Apache Mod-Proxy <apache_mod_proxy>` or the :ref:`nginx`
 you need to make sure that the TurboGears server is started automatically.
-On Un*x you can treat your app like every other system daemon by adding a
-custom init script which starts the server automatically when your system boots.
+There are a number of options to accomplish this:
+* `Upstart`_ -- used on newer Linux hosts
+* `Sys-V Init` -- traditional Unix/Linux init system
+* `supervisord`_ -- separate daemon with ability to monitor and restart
+Which one you choose is likely up to your familiarity level with the
+particular tool.
+.. todo:: Provide sample init script
+.. todo:: Provide sample upstart
+.. todo:: Provide sample supervisord config
 .. todo:: Difficulty: Hard. Document usage of to deploy as a Win32 service
+.. _`supervisord`:
+.. _`upstart`: