Chronos est un système permettant d'organiser le planning d'équipes et d'en faire des statistiques.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Vincent Adolphe a03b1d0388 doc(tableau de bord): explication mode de calcul 1 year ago
assets feat(webui): habillage de la page d'accueil + theme bt4 pour f-cal 1 year ago
chronos doc(sphinx): squelette + import d'image/logo 1 year ago
db_scripts build(Makefile/database): ajout d'un reset psql 1 year ago
docs doc(tableau de bord): explication mode de calcul 1 year ago
requirements doc(webui): integration dans l'interface de chronos 1 year ago
screenshots test(selenium/webui): ajout de screenshots 1 year ago
styleguide initial commit 1 year ago
var/log feat(chronos): ajout config log 1 year ago
.babelrc initial commit 1 year ago
.browserslistrc initial commit 1 year ago
.editorconfig build(editorconfig): ajout d'un .editorconfig 1 year ago
.eslintrc initial commit 1 year ago
.gitignore doc(sphinx): doc initiale 1 year ago
.gitmessage build(Makefile): ajout "reset-migrations" 1 year ago
.stylelintrc initial commit 1 year ago
CHANGELOG.md initial commit 1 year ago
CONTRIBUTORS.txt initial commit 1 year ago
LICENSE initial commit 1 year ago
Makefile build(doc): make doc d'autorite dans le venv 1 year ago
README.md fix(doc): corrige un `from .base import *` manquant 1 year ago
config.env.example initial commit 1 year ago
gulpfile.js feat(webui/js): import handler js pour la modale depuis sisyphe 1 year ago
manage.py initial commit 1 year ago
notes.txt doc(chronos): notes diverses 1 year ago
package-lock.json build(Makefile): permet peupler la base en prod. 1 year ago
package.json build(Makefile): permet peupler la base en prod. 1 year ago
pyproject.toml build(chronos/Makefile): ajout cible black et pre-commit 1 year ago
pytest.ini build(Makefile/pytest): ajout d'un tag wip 1 year ago
requirements.txt initial commit 1 year ago
setup.cfg ref(evenement): ajout evenement dans conf projet 1 year ago

README.md

Chronos - README

gestion et organisation du temps

Early build for development

In early stage of development, database and assets are not yet fixed so building the project involve a little more steps:

  1. assume git clone is done and npm is installed

  2. make build (may crash due to incomplete migrations - ignore error)

  3. make reset-migrations (remove database, local migration, redo it, install some fixtures)

  4. npm install (install all the assets dependancies)

  5. npm run build (create assets)

  6. Use it! make serve / make test ...

keep it up to date

  1. git pull (or git fetch + git merge)

  2. make update (install new python dependancies if needed, may crash due to incompletes migrations - ignore error)

  3. make reset-migrations (re-create database from scratch)

  4. npm install / npm run build update assets if needed

  5. Use it! make serve / make test ...

Installation

Requirements

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

  • python3
  • virtualenv
  • 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.

Deployment

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 (from 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;
}

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

Manual installation

If you don't want to use the Makefile facilities, here is what is done behind the scene.

It assumes that you have downloaded the last release of Chronos, extracted it and that you moved to that folder.

  1. Start by creating a new virtual environment under ./venv and activate it:

    $ virtualenv --system-site-packages ./venv
    $ source ./venv/bin/activate
    
  2. Install the required Python packages depending on your environment:

    $ pip install -r requirements/production.txt
    ... or ...
    $ pip install -r requirements/development.txt
    
  3. Configure the application by setting the proper environment variables depending on your environment. You can use the config.env.example which give you the main variables with example values.

    $ cp config.env.example config.env
    $ nano config.env
    $ chmod go-rwx 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 the READ_CONFIG_FILE environment variable to 0.

  4. 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

Structure

Overview

All the application files - e.g. Django code including settings, templates and statics - are located into the chronos/. 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 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.

Development

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

License

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