|Jérôme Lebleu 93a6d6ce3e fix(assets): supprime leaflet du dossier static||3 months ago|
|assets||3 months ago|
|ess62_plateforme||3 months ago|
|requirements||10 months ago|
|styleguide||3 months ago|
|.babelrc||3 months ago|
|.browserslistrc||3 months ago|
|.editorconfig||3 months ago|
|.eslintrc||3 months ago|
|.gitignore||3 months ago|
|.stylelintrc||3 months ago|
|CHANGELOG.md||10 months ago|
|LICENSE||10 months ago|
|Makefile||10 months ago|
|README.md||10 months ago|
|config.env.example||10 months ago|
|gulpfile.js||3 months ago|
|manage.py||10 months ago|
|package-lock.json||3 months ago|
|package.json||3 months ago|
|requirements.txt||10 months ago|
|setup.cfg||10 months ago|
La plate-forme pour les organisations de l’Économie Sociale et Solidaire du Pas-de-Calais.
On a Debian-based host - running at least Debian Stretch, you will need the following packages:
Note: if you’re serving the application with uWSGI and NGINX on a sub location, ensure
that you’ve added
route-run = fixpathinfo: to your uWSGI configuration (from
In waiting for a complete
Makefile, you will have to follow those steps to
install the application.
It assumes that you have downloaded the last release of Plate-forme du CDESS, extracted it and that you moved to that folder.
Start by creating a new virtual environment under
./venv and activate it:
$ virtualenv --system-site-packages ./venv $ source ./venv/bin/activate
Install the required Python packages depending on your environment:
$ pip install -r requirements/production.txt ... or ... $ pip install -r requirements/development.txt
Configure the application by setting the proper environment variables
depending on your environment. You can use the
give you the main variables with example values.
$ cp config.env.example config.env $ nano config.env
Note that this
./config.env file will be loaded by default when the
application starts. If you don’t want that, just move this file away or set
DJANGO_READ_CONFIG_FILE environment variable to
Create the database tables - it assumes that you have created the database and set the proper configuration to use it:
$ ./manage.py migrate
That’s it! You should now be able to start the Django development server to check that everything is working fine with:
$ ./manage.py runserver
All the application files - e.g. Django code including settings, templates and
statics - are located into the
ess62_plateforme/. It should
permit in a near future to distribute the application as a Python package and
install it system-wide.
Two environments are defined - either for requirements and settings:
development: for local application development and testing. It uses a SQLite3 database and enable debugging by default, add some useful settings and applications for development purpose - i.e. the
production: for production. It checks that configuration is set and correct, try to optimize performances and enforce some settings - i.e. HTTPS related ones.
You can override and extend statics and templates locally. This can be useful
if you have to change the logo for a specific instance for example. For that,
just put your files under the
Regarding the statics, do not forget to collect them after that. Note also that
local/ folder is ignored by git.
All the variable content - e.g. user-uploaded media, collected statics - are
stored inside the
var/ folder. It is also ignored by git as it’s specific
to each application installation.
So, you will have to configure your Web server to serve the
var/static/ folders, which should point to
Plate-forme du CDESS is developed by Cliss XXI and licensed under the AGPLv3+.