Confirmed users
1,209
edits
Verbatim:Development/Dev Instance: Difference between revisions
→Setting up a Pootle development instance: virtualenv is not required
(→Setting up a Pootle development instance: virtualenv is not required) |
|||
| Line 9: | Line 9: | ||
** <code>git svn clone -Ttrunk https://translate.svn.sourceforge.net/svnroot/translate/src/ pootle</code> | ** <code>git svn clone -Ttrunk https://translate.svn.sourceforge.net/svnroot/translate/src/ pootle</code> | ||
** if you are using <code>git-svn</code>, make sure to generate an empty <code>dbs</code> directory, as git won't pick up empty directories [http://sourceforge.net/mailarchive/forum.php?thread_name=4A37D896.3070403%40mozilla.com&forum_name=translate-devel] | ** if you are using <code>git-svn</code>, make sure to generate an empty <code>dbs</code> directory, as git won't pick up empty directories [http://sourceforge.net/mailarchive/forum.php?thread_name=4A37D896.3070403%40mozilla.com&forum_name=translate-devel] | ||
* create a clean Python environment for the application, using [http://pypi.python.org/pypi/virtualenv virtualenv] | * if you do not want to install Pootle's requirements into your global Python environment, create a clean, virtual Python environment for the application, using [http://pypi.python.org/pypi/virtualenv virtualenv]. Note that this is not required, but may be helpful if you develop on multiple python-based projects | ||
** <code>virtualenv --no-site-packages --python=path/to/python2.[ | ** <code>virtualenv --no-site-packages --python=path/to/python2.[4-6] pootle-env</code> | ||
** <code>cd pootle-env/</code> | ** <code>cd pootle-env/</code> | ||
** <code>. bin/activate</code> | ** <code>. bin/activate</code> | ||
| Line 19: | Line 19: | ||
*** <code>python setup.py install</code> | *** <code>python setup.py install</code> | ||
* Initialize the database by running the <code>./PootleServer</code> script once. | * Initialize the database by running the <code>./PootleServer</code> script once. | ||
** '''Note for OS X users:''' At this point | ** '''Note for OS X users:''' At this point you may get an error that lxml is not installed. Running <code>easy_install lxml</code> didn't work for me, but it might work for you. Instead what I had to do was download the [http://codespeak.net/lxml/lxml-2.2.1.tgz lxml .tqz] and then: | ||
***<code>tar -xvzf lxml-2.2.1.tgz</code> | ***<code>tar -xvzf lxml-2.2.1.tgz</code> | ||
***<code>cd lxml-2.2.1</code> | ***<code>cd lxml-2.2.1</code> | ||