Jan Dittberner
d5e1128ff6
- add migration to place a unique constraint on MailAddressMailbox.mailaddress and drop existing primary_key - change managemails.models.MailAddressMailbox.mailaddress to OneToOneField |
||
---|---|---|
docs | ||
gnuviechadmin | ||
requirements | ||
.gitignore | ||
CONTRIBUTORS.txt | ||
LICENSE.txt | ||
README.rst | ||
requirements.txt |
gnuviechadmin
Customer center for gnuviech servers.
To use this project follow these steps:
- Create your working environment
- Install Django
- Create the new project using the django-two-scoops template
- Install additional dependencies
- Use the Django admin to create the project
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 Only
First, make sure you are using virtualenv (http://www.virtualenv.org). Once that's installed, create your virtualenv:
$ virtualenv --distribute gnuviechadmin
You will also need to ensure that the virtualenv has the project directory added to the path. Adding the project directory will allow django-admin.py to be able to change settings using the --settings flag.
Virtualenv with virtualenvwrapper
In Linux and Mac OSX, you can install virtualenvwrapper (http://virtualenvwrapper.readthedocs.org/en/latest/), which will take care of managing your virtual environments and adding the project path to the site-directory for you:
$ mkdir gnuviechadmin
$ mkvirtualenv -a gnuviechadmin gnuviechadmin-dev
$ cd gnuviechadmin && add2virtualenv `pwd`
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