Go to file
Vincent Adolphe 3c49f4a058 Merge branch 'devel' 2023-09-26 16:46:26 +02:00
bin build(Makefile,bin): make check_env verifie les dependances root 2023-01-30 18:10:50 +01:00
center_pilote Merge branch 'devel' 2023-09-26 15:11:32 +02:00
requirements build: pinning manuel des requirements pour fixer un pb avec setuptools_scm 2023-09-26 15:54:35 +02:00
.editorconfig init 2021-08-03 16:07:40 +02:00
.gitattributes init 2021-08-03 16:07:40 +02:00
.gitignore build: ajout versionnement sur scm 2023-06-30 16:13:46 +02:00
CHANGELOG.md init 2021-08-03 16:07:40 +02:00
CONTRIBUTORS.txt init 2021-08-03 16:07:40 +02:00
LICENSE init 2021-08-03 16:07:40 +02:00
MANIFEST.in init 2021-08-03 16:07:40 +02:00
Makefile build(Makefile): relance cremecrm-job-manager sur un update 2023-09-26 16:27:34 +02:00
README.md fix(build): c'est le nom du depot qui n'etait pas bon 2022-01-17 09:32:36 +01:00
config.env.example build(settings): LOG_LEVEL configurable via config.env 2023-01-31 15:41:47 +01:00
manage.py init 2021-08-03 16:07:40 +02:00
pyproject.toml build(setuptools_scm): post_release est deprecié remplacé par no-guess-dev 2023-09-26 16:45:22 +02:00
requirements.txt init 2021-08-03 16:07:40 +02:00
setup.cfg build(behave): ajout de couverture de code sur les tests behave 2023-06-02 11:01:48 +02:00
setup.py fix(setup.py): corrige une typo 2022-08-23 11:40:06 +02:00



CremeCRM pour Fibois

Table of content

Give a try

On a Debian-based host - running at least Debian Stretch:

$ sudo apt install python3 virtualenv git make
$ git clone https://forge.cliss21.org/cliss21/creme_center_fibois
$ cd creme_center_fibois/

$ make init
# A configuration file will be created interactively; you can uncomment:
#  ENV=development

$ make serve

Then visit in your web browser.



On a Debian-based host - running at least Debian Stretch, you will need the following packages:

  • python3
  • virtualenv
  • make
  • git (recommended for getting the source)
  • python3-mysqldb (optional, in case of a MySQL / MariaDB database)
  • python3-psycopg2 (optional, in case of a PostgreSQL database)

Quick start

It assumes that you already have the application source code locally - the best way is by cloning this repository - and that you are in this folder.

  1. Define your local configuration in a file named config.env, which can be copied from config.env.example and edited to suits your needs.

    Depending on your environment, you will have to create your database and the user at first.

  2. Run make init.

    Note that if there is no config.env file, it will be created interactively.

That's it! Your environment is now initialized with the application installed. To update it, once the source code is checked out, simply run make update.

You can also check that your application is well configured by running make check.


Web application

Here is an example deployment using NGINX - as the Web server - and uWSGI - as the application server.


The uWSGI configuration doesn't require a special configuration, except that we are using Python 3 and a virtual environment. Note that if you serve the application on a sub-location, you will have to add route-run = fixpathinfo: to your uWSGI configuration (available since v2.0.11).


In the server block of your NGINX configuration, add the following blocks and set the path to your application instance and to the uWSGI socket:

location / {
    include uwsgi_params;
    uwsgi_pass unix:<uwsgi_socket_path>;
location /media {
    alias <app_instance_path>/var/media;
location /static {
    alias <app_instance_path>/var/static;
    # Optional: don't log access to assets
    access_log off;
location = /favicon.ico {
    alias <app_instance_path>/var/static/favicon/favicon.ico;
    # Optional: don't log access to the favicon
    access_log off;



All the application files - e.g. Django code including settings, templates and statics - are located into creme_center_fibois/.

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 django-debug-toolbar.
  • production: for production. It checks that configuration is set and correct, try to optimize performances and enforce some settings - i.e. HTTPS related ones.

Local changes

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 local/static/ and local/templates/ folders.

Regarding the statics, do not forget to collect them after that. Note also that the local/ folder is ignored by git.

Variable content

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/media/ and var/static/ folders, which should point to /media/ and /static/, respectively.


The easiest way to deploy a development environment is by using the Makefile.

Before running make init, ensure that you have either set ENV=development in the config.env file or have this environment variable. Note that you can still change this variable later and run make init again.

There is some additional rules when developing, which are mainly wrappers for manage.py. You can list all of them by running make help. Here are the main ones:

  • make serve: run a development server
  • make test: test the whole application
  • make lint: check the Python code syntax


creme_center_fibois is developed by Cliss XXI and licensed under the AGPLv3+.