aboutsummaryrefslogtreecommitdiffstats
path: root/docs/source/deploying.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/deploying.rst')
-rw-r--r--docs/source/deploying.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/source/deploying.rst b/docs/source/deploying.rst
index b944a3d3..9c0acf30 100644
--- a/docs/source/deploying.rst
+++ b/docs/source/deploying.rst
@@ -244,7 +244,7 @@ Production MediaGoblin Deployments with Paste
The instance configured with ``lazyserver`` is not ideal for a
production MediaGoblin deployment. Ideally, you should be able to use
-a a control script (i.e. init script.) to launch and restart the
+a control script (i.e. init script.) to launch and restart the
MediaGoblin process.
Use the following command as the basis for such a script: ::
@@ -252,13 +252,13 @@ Use the following command as the basis for such a script: ::
CELERY_ALWAYS_EAGER=true \
/srv/mediagoblin.example.org/mediagoblin/bin/paster serve \
/srv/mediagoblin.example.org/mediagoblin/paste.ini \
- --pid-file=/tmp/mediagoblin.pid \
+ --pid-file=/var/run/mediagoblin.pid \
--server-name=fcgi fcgi_host=127.0.0.1 fcgi_port=26543 \
.. note::
The above configuration places MediaGoblin in "always eager" mode
with Celery. This is fine for development and smaller
- deployments. However, if you're getting into the really large
- deployment category, consider reading the section of this manual on
- Celery.
+ deployments. However, for larger production deployments with larger
+ processing requirements, see the ":doc:`production-deployments`"
+ documentation.