Updated hackinghowto.rst with info on how to use the new buildout
stuff.
This commit is contained in:
parent
df0953ce45
commit
719f82bad3
@ -22,20 +22,17 @@ to, what needs to be worked on, and other things besides!
|
|||||||
How to set up an environment for hacking
|
How to set up an environment for hacking
|
||||||
========================================
|
========================================
|
||||||
|
|
||||||
The following assumes you have these things installed:
|
If running Debian GNU/Linux or a Debian-derived distro such as Mint or
|
||||||
|
Ubuntu, running the following should install necessary dependencies:
|
||||||
|
|
||||||
1. virtualenv:
|
sudo apt-get install mongodb git-core python python-dev python-lxml
|
||||||
|
|
||||||
http://pypi.python.org/pypi/virtualenv
|
|
||||||
|
|
||||||
2. virtualenv wrapper:
|
|
||||||
|
|
||||||
http://www.doughellmann.com/projects/virtualenvwrapper/
|
|
||||||
|
|
||||||
3. git:
|
|
||||||
|
|
||||||
http://git-scm.com/
|
|
||||||
|
|
||||||
|
Note: The following instructions describe a development environment
|
||||||
|
that uses `zc.buildout <http://www.buildout.org/>`_ because it
|
||||||
|
involves less steps to get things running and less knowledge of python
|
||||||
|
packaging. However, if you prefer to use
|
||||||
|
`virtualenv <http://pypi.python.org/pypi/virtualenv>`_,
|
||||||
|
that should work just fine.
|
||||||
|
|
||||||
Follow these steps:
|
Follow these steps:
|
||||||
|
|
||||||
@ -43,28 +40,20 @@ Follow these steps:
|
|||||||
|
|
||||||
git clone http://git.gitorious.org/mediagoblin/mediagoblin.git
|
git clone http://git.gitorious.org/mediagoblin/mediagoblin.git
|
||||||
|
|
||||||
2. create a virtual environment::
|
2. Bootstrap and run buildout::
|
||||||
|
|
||||||
mkvirtualenv mediagoblin
|
cd mediagoblin
|
||||||
|
python bootstrap.py && ./bin/buildout
|
||||||
|
|
||||||
3. if that doesn't put you in the virtual environment you created,
|
Now whenever you want to update mediagoblin's dependencies, just run::
|
||||||
then do::
|
|
||||||
|
|
||||||
workon mediagoblin
|
./bin/buildout
|
||||||
|
|
||||||
4. run::
|
|
||||||
|
|
||||||
python setup.py develop
|
|
||||||
|
|
||||||
|
|
||||||
When you want to work on GNU MediaGoblin, make sure to enter your
|
Using this method, buildout should create a user_dev directory, in
|
||||||
virtual environment::
|
which certain things will be stored (media, beaker session stuff,
|
||||||
|
etc). You can change this, but for development purposes this default
|
||||||
workon mediagoblin
|
should be fine.
|
||||||
|
|
||||||
Any changes you make to the code will show up in your virtual
|
|
||||||
environment--there's no need to continuously run ``python setup.py
|
|
||||||
develop``.
|
|
||||||
|
|
||||||
|
|
||||||
Running the test suite
|
Running the test suite
|
||||||
@ -72,7 +61,7 @@ Running the test suite
|
|||||||
|
|
||||||
Run::
|
Run::
|
||||||
|
|
||||||
python setup.py test
|
./bin/nosetests
|
||||||
|
|
||||||
|
|
||||||
Creating a new file
|
Creating a new file
|
||||||
|
Loading…
x
Reference in New Issue
Block a user