- Apr 15, 2019
-
-
Jean-Sébastien Caux authored
-
- Jan 08, 2019
-
-
Jean-Sébastien Caux authored
-
- Apr 14, 2018
-
-
Jorran de Wit authored
-
- Mar 25, 2018
-
-
Jean-Sébastien Caux authored
-
- Mar 22, 2018
-
-
Jorran de Wit authored
-
- Feb 20, 2018
-
-
Jorran de Wit authored
-
- Dec 29, 2017
-
-
Jorran de Wit authored
If you are updating on a machine please follow these steps *BEFORE* updating your code to this commit. If you are installing on a fresh database and do not need to think about existing data, ignore the following and proceed as usual. 1. Run the following migrations: ``` python manage.py migrate --fake scipost zero python manage.py migrate --fake notifications zero python manage.py migrate --fake partners zero python manage.py migrate --fake affiliations zero python manage.py migrate --fake commentaries zero python manage.py migrate --fake comments zero python manage.py migrate --fake finances zero ``` 2. *** NOW UPDATE/PULL GIT *** 3. Run: `python manage.py migrate --fake-initial`
-
- Oct 16, 2017
-
-
Jorran de Wit authored
-
- Sep 09, 2017
-
-
Jorran de Wit authored
-
- Jul 17, 2017
-
-
Jorran de Wit authored
-
- Jun 07, 2017
-
-
Jorran de Wit authored
The mailing lists member sync was too elementary to be used on production properly. This was for example due to the single calls to MailChimp for each seperate Contributor. Now during sync, only updates are called to MailChimp, not *all* contributors. Also, the batch operation is used instead of seperate calls. Further, some query tweaks were used that expect database calls to improve significant.
-
- Apr 24, 2017
-
-
Jorran de Wit authored
-
- Apr 23, 2017
-
-
Jorran de Wit authored
-
Jorran de Wit authored
-