Merge branch 'feat-simple-working-default' of daimrod/coin into master

.gitignore

@@ -12,3 +12,4 @@ coin/settings_local.py
 /smedia
 .idea
 venv
+/coin.sqlite3

DEPLOYMENT.md

@@ -1,5 +1,13 @@
-For production deployment, it is recommended to use a reverse proxy
-setup, for instance using gunicorn.
+Before deploying in production, you should read carefully the django
+deployment checklist :
+
+  https://docs.djangoproject.com/en/1.7/howto/deployment/checklist/
+
+It is highly recommended to set the TEMPATE_DEBUG and DEBUG variables
+to False when deploying in production.
+
+For production deployment, it is also recommended to use a reverse
+proxy setup, for instance using gunicorn.
 
 This is because the access to invoices (PDF) is a bit special: they
 are served by the web server for efficiency, but django itself handles
@@ -13,7 +21,6 @@ For the complete deployment configuration used by Illyse, see:
 
   https://www.illyse.org/projects/ils-si/wiki/Mise_en_place_production
 
-
 ## Gunicorn configuration
 
 Gunicorn on Debian wheezy is very nice, because it can launch automatically

README.md

@@ -78,22 +78,25 @@ See the end of this README for a reference of available configuration settings.
 Database
 --------
 
-At this point, you should setup your database: we highly recommend PostgreSQL.
-SQLite might work, but some features will not be available:
+At this point, you should setup your database. The default setting
+uses SQLite but some features will not be available, namely:
 
 - automatic allocation of IP subnets (needs proper subnet implementation in
   the database)
 - sending automated emails to remind of expiring membership fee
   (needs aggregation on date fields, see Django doc)
 
-For more information on the database setup, see https://doc.illyse.net/projects/ils-si/wiki/Mise_en_place_environnement_de_dev
+If you want to use those features, you will need to setup a PostgreSQL
+database.
+
+For more information on the database setup, see https://www.illyse.org/projects/ils-si/wiki/Mise_en_place_environnement_de_dev
 
 The first time, you need to create the database, create a superuser, and
 import some base data to play with:
 
     python manage.py migrate
     python manage.py createsuperuser
-    python manage.py loaddata offers ip_pool
+    python manage.py loaddata offers ip_pool # skip this if you don't use PostgreSQL
 
 Note that the superuser will be inserted into the LDAP backend exactly in the
 same way as all other members, so you should use a real account (not just

coin/settings.py

@@ -10,7 +10,7 @@ import ldap
 BASE_DIR = os.path.dirname(os.path.dirname(__file__))
 
 PROJECT_PATH = os.path.abspath(os.path.dirname(__file__))
-DEBUG = TEMPLATE_DEBUG = False
+DEBUG = TEMPLATE_DEBUG = True
 
 ADMINS = (
     # ('Your Name', 'your_email@example.com'),
@@ -21,17 +21,17 @@ MANAGERS = ADMINS
 DATABASES = {
     # Base de donnée du SI
     'default': {
-        'ENGINE': 'django.db.backends.postgresql_psycopg2',
-        'NAME': 'coin',
-        'USER': 'coin',
-        'PASSWORD': '',
+        'ENGINE': 'django.db.backends.sqlite3',
+        'NAME': 'coin.sqlite3',
+        'USER': '', # Not needed for SQLite
+        'PASSWORD': '', # Not needed for SQLite
         'HOST': '',  # Empty for localhost through domain sockets
         'PORT': '',  # Empty for default
     },
 }
 
 # Hosts/domain names that are valid for this site; required if DEBUG is False
-# See https://docs.djangoproject.com/en/1.5/ref/settings/#allowed-hosts
+# See https://docs.djangoproject.com/en/1.7/ref/settings/#allowed-hosts
 ALLOWED_HOSTS = []
 
 # Local time zone for this installation. Choices can be found here: