RPM mod_wsgi installation (Red Hat, Fedora, etc.): | |
---|---|
Setting up a Moksha RPM & mod_wsgi environment (Fedora, RHEL, CentOS) | |
virtualenv installation (OSX, Ubuntu, etc.): | |
Virtualenv installation (Other Linux distros, OSX, Windows, etc) |
$ git clone git://git.fedorahosted.org/git/moksha
$ cd moksha/
$ ./moksha-ctl.py bootstrap
$ ./moksha-ctl.py rebuild
$ workon moksha
(moksha) $ pip install --upgrade mdemos.all
(moksha) $ deactivate
$ workon moksha
(moksha) $ pip install --upgrade mdemos.metrics
(moksha) $ deactivate
$ ./moksha-ctl.py restart:paster
$ ./moksha-ctl.py restart:moksha-hub
$ ./moksha-ctl.py wtf
$ ./moksha-ctl.py logs
$ paver html
$ workon moksha
(moksha) $ python setup.py test
(moksha) $ deactivate
$ ./moksha-ctl.py rebuild restart
$ workon moksha
(moksha) $ python setup.py test
(moksha) $ deactivate
Note
As a developer, performing the full rebuild, reinstall, restart, and test sequence is usually a good habit to get into, however it can take a long time. If you’re hardcore, this RPM patch will speed things up quite a bit.
$ pip freeze -E ~/.virtualenvs/moksha -r requirements.txt production/stable-reqs.txt
Open the moksha/config/app_cfg.py
file and set the base_config.profile variable to True. After surfing around your application, you can then go to http://localhost:8080/__profile__ to view your profiling statistics.