|Jérôme Lebleu ed8b33e447 [fix] Corrige la classe d'un champ requis||1 month ago|
|assets||1 month ago|
|boiteaasso||1 month ago|
|requirements||2 months ago|
|styleguide||5 months ago|
|.babelrc||5 months ago|
|.browserslistrc||5 months ago|
|.eslintrc||7 months ago|
|.gitignore||5 months ago|
|.jshintrc||9 months ago|
|.sass-lint.yml||9 months ago|
|CHANGELOG.md||11 months ago|
|LICENSE||1 year ago|
|Makefile||2 months ago|
|README.md||11 months ago|
|config.env.example||11 months ago|
|gulpfile.js||2 months ago|
|manage.py||11 months ago|
|package-lock.json||2 months ago|
|package.json||2 months ago|
|pytest.ini||2 months ago|
|requirements.txt||1 year ago|
|setup.cfg||11 months ago|
La plateforme numérique de l’Association d’Action Éducative du Pas-de-Calais.
On a Debian-based host - running at least Debian Jessie, you will need the following packages:
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 Plateforme de l’AAE62, 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
boiteaasso/. 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