summaryrefslogtreecommitdiff
path: root/doc/01_getting_started.rst
diff options
context:
space:
mode:
authorAntony Lesuisse <al@openerp.com>2012-11-11 03:39:03 +0100
committerAntony Lesuisse <al@openerp.com>2012-11-11 03:39:03 +0100
commitd9554b698a44bbd2fadcdd23ac60c4477be6ace0 (patch)
treee5bd87dfd38683e718c11b889bd2e91521a611fc /doc/01_getting_started.rst
parent4820450aef943e25aedc7e767e39f08cdadd8f18 (diff)
rearrange toc, remove some deprecated stuff
bzr revid: al@openerp.com-20121111023903-yus5wxlw06ods46f
Diffstat (limited to 'doc/01_getting_started.rst')
-rw-r--r--doc/01_getting_started.rst18
1 files changed, 17 insertions, 1 deletions
diff --git a/doc/01_getting_started.rst b/doc/01_getting_started.rst
index 79b2bc94298..267e2759550 100644
--- a/doc/01_getting_started.rst
+++ b/doc/01_getting_started.rst
@@ -155,7 +155,23 @@ You can specify alternate configuration files with ::
-c CONFIG, --config=CONFIG specify alternate config file
-An example of server configuration file for
+Start-up script
+===============
+
+.. versionadded:: 6.1
+
+To run the OpenERP server, the conventional approach is to use the
+`openerp-server` script. It loads the :ref:`openerp library`, sets a few
+configuration variables corresponding to command-line arguments, and starts to
+listen to incoming connections from clients.
+
+Depending on your deployment needs, you can write such a start-up script very
+easily. We also recommend you take a look at an alternative tool called
+`openerp-command` that can, among other things, launch the server.
+
+Yet another alternative is to use a WSGI-compatible HTTP server and let it call
+into one of the WSGI entry points of the server.
+
Appendix
========