|
|
@@ -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
|
daimrod