Gnuviech admin end user and administration web frontend
Go to file
Jan Dittberner 0ef151f780 Merge branch 'release/0.4.0' into production
* release/0.4.0: (25 commits)
  define version number, update changelog
  set database password at the appropriate place
  remove username argument from delete_pgsql_database call
  remove username argument of pgsqltasks.tasks.delete_pgsql_database
  fix documentation issues
  add autogenerated documentation for module members
  make userdbs admin work properly
  add initial migration for userdbs
  add admin and a bit of documentation
  add new incomplete userdbs app
  document addition of mysqltasks and pgsqltasks
  add mysqltasks and pgsqltasks with placeholders for the real tasks
  set default locale to en-us to avoid translated migrations
  add migration for verbose_name and verbose_name_plural in osusers.models.User
  switch to gvacommon.celeryrouters.GvaRouter
  unify routers, add support for mysql and pgsql tasks
  use taskresults app and delete_ldap_group task
  add taskresults app to handle celery task results
  add new task delete_ldap_group
  define celery timezone, restrict celery content to json
  ...
2015-01-11 15:33:18 +01:00
docs define version number, update changelog 2015-01-11 15:32:46 +01:00
gnuviechadmin set database password at the appropriate place 2015-01-10 18:43:43 +01:00
requirements update dependencies 2014-12-17 21:40:08 +01:00
.gitignore add german translation 2014-12-27 22:58:57 +01:00
CONTRIBUTORS.txt auto generated project 2014-05-18 00:07:32 +02:00
LICENSE.txt auto generated project 2014-05-18 00:07:32 +02:00
README.rst auto generated project 2014-05-18 00:07:32 +02:00
requirements.txt auto generated project 2014-05-18 00:07:32 +02:00

README.rst

gnuviechadmin

Customer center for gnuviech servers.

To use this project follow these steps:

  1. Create your working environment
  2. Install Django
  3. Create the new project using the django-two-scoops template
  4. Install additional dependencies
  5. 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