canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093
edits
Labs/Bespin/ProductionDeployment: Difference between revisions
no edit summary
(Created page with '= Production Deployment = This document describes the production deployment of the Python backend. The Python backend is a standard [http://www.python.org/dev/peps/pep-0333/ WSG...') |
No edit summary |
||
| Line 136: | Line 136: | ||
# above is sample config | # above is sample config | ||
#root_log.addHandler(handler2) | #root_log.addHandler(handler2) | ||
# activate profile is responsible for taking the config and creating database | # activate profile is responsible for taking the config and creating database | ||
# connections, etc. | # connections, etc. | ||
| Line 153: | Line 153: | ||
secret=YOUR SECRET USED IN HASHING | secret=YOUR SECRET USED IN HASHING | ||
static_dir=/home/WSGIUSER/BespinServer/frontend | static_dir=/home/WSGIUSER/BespinServer/frontend | ||
== Creating the database == | |||
Assuming bespin.wsgi is in a directory called wsgi-apps that is at the same level as your BespinServer directory, you can then run | |||
paver create_db | |||
To set up your production database. | |||