heckyel/mediagoblin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

buildout instructions come first since it's easier if it does work

Browse Source
This commit is contained in:
Christopher Allan Webber 2011-05-12 10:05:35 -05:00
parent 36bb98fbba
commit 95aa6b56b2
1 changed files with 9 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
docs/hackinghowto.rst
View File

@ -215,14 +215,13 @@ To do this, do::
Running the server Running the server
================== ==================
If you did virtualenv, run::
paster serve mediagoblin.ini --reload
If you did buildout, run:: If you did buildout, run::
./bin/paster serve mediagoblin.ini --reload ./bin/paster serve mediagoblin.ini --reload
If you did virtualenv, run::
paster serve mediagoblin.ini --reload
Running celeryd Running celeryd
=============== ===============
@ -231,26 +230,24 @@ You need to do this if you want your media to process and actually
show up. It's probably a good idea in development to have the web show up. It's probably a good idea in development to have the web
server (above) running in one terminal and celeryd in another window. server (above) running in one terminal and celeryd in another window.
If you did virtualenv, run::
CELERY_CONFIG_MODULE=mediagoblin.celery_setup.from_celery celeryd
If you did buildout, run:: If you did buildout, run::
CELERY_CONFIG_MODULE=mediagoblin.celery_setup.from_celery ./bin/celeryd CELERY_CONFIG_MODULE=mediagoblin.celery_setup.from_celery ./bin/celeryd
If you did virtualenv, run::
CELERY_CONFIG_MODULE=mediagoblin.celery_setup.from_celery celeryd
Running the test suite Running the test suite
====================== ======================
If you did virtualenv, run::
nosetests
If you did buildout, run:: If you did buildout, run::
./bin/nosetests ./bin/nosetests
If you did virtualenv, run::
nosetests
Troubleshooting Troubleshooting
=============== ===============