- move settings to gvafile.settings - use gvafile.settings directly without Django support - initialize Celery without Django - remove Django requirements
1.9 KiB
installation
Install
Working Environment
You have several options in setting up your working environment. We recommend using virtualenv to separate the dependencies of your project from your system's python environment. If on Linux or Mac OS X, you can also use virtualenvwrapper to help manage multiple virtualenvs across different projects.
virtualenv
Virtualenv Only
First, make sure you are using virtualenv. Once that's installed, create your virtualenv:
virtualenv --distribute gvafile $
You will also need to ensure that the virtualenv has the project directory added to the path.
virtualenvwrapper
Virtualenv with virtualenvwrapper
In Linux and Mac OSX, you can install virtualenvwrapper, which will take care of managing your virtual environments and adding the project path to the site-directory for you:
mkdir gvafile
$ mkvirtualenv -a gvafile gvafile-dev
$ cd gvafile && add2virtualenv `pwd` $
pip, requirements, dependencies
Installation of Dependencies
Depending on where you are installing dependencies:
In development:
pip install -r requirements/local.txt $
For production:
pip install -r requirements.txt $
celery, worker, file queue
Running the Celery worker
gvafile uses the Celery distributed task queue system. The gvafile logix is executed by a celery worker. After all dependencies are installed you can go into the gvafile directory and run the celery worker with:
cd gvafile
$ celery -A gvafile worker -Q file -l info $