Miroir du site de l'AE UTBM https://ae.utbm.fr
Go to file
Skia d83bb20547 core: small update on footnotes style
Signed-off-by: Skia <skia@libskia.so>
2018-02-22 22:56:15 +01:00
accounting Add possibility to not link an operation 2017-10-22 22:29:36 +02:00
api Fix some bugs in mailings with new club tools 2017-10-06 11:09:31 +02:00
club Fix for mailing lists 2017-12-22 12:06:23 +01:00
com Fix datetime forms for posters 2017-12-22 12:53:43 +01:00
core core: small update on footnotes style 2018-02-22 22:56:15 +01:00
counter fix can_buy in customer 2017-12-01 01:44:38 +01:00
doc Update README and Markdown test assets 2017-11-09 14:37:29 +01:00
eboutic Add comment in product type 2017-10-25 23:02:46 +02:00
election It's better to delete an object in delete 2017-12-12 14:52:08 +01:00
forum forum: add favorite topics 2018-02-22 22:28:28 +01:00
launderette Format launderette 2017-06-13 10:04:13 +02:00
locale/fr/LC_MESSAGES forum: add favorite topics 2018-02-22 22:28:28 +01:00
matmat Translations fix 2017-08-15 18:57:50 +02:00
rootplace Move mailing list admin to com 2017-08-22 15:36:39 +02:00
sas sas: fix notification callback 2017-10-15 12:00:33 +02:00
sith Posters now working + notifications for com admin 2017-12-16 20:48:36 +01:00
stock Add header to stock files 2017-04-25 16:17:04 +02:00
subscription Search field in Subscription admin area 2017-11-17 11:48:16 +01:00
trombi trombi: update export page again 2017-10-06 17:29:23 +02:00
.coveragerc coverage: blacklist some files 2017-09-07 11:50:05 +02:00
.gitignore gitignore: ignore coverage artifacts 2017-08-29 16:45:18 +02:00
.gitlab-ci.yml CI: add coverage report 2017-08-29 16:01:01 +02:00
CONTRIBUTING.md Integrate external_res variable 2017-10-18 14:44:47 +02:00
Doxyfile Update Doxyfile 2016-06-22 14:52:53 +02:00
LICENSE Apply GPLv3 to Sith, and add header to every concerned file 2017-04-24 17:51:12 +02:00
LICENSE.old Apply GPLv3 to Sith, and add header to every concerned file 2017-04-24 17:51:12 +02:00
manage.py Apply GPLv3 to Sith, and add header to every concerned file 2017-04-24 17:51:12 +02:00
migrate.py Fix is_active migration 2017-10-06 11:09:30 +02:00
README.md Update README and Markdown test assets 2017-11-09 14:37:29 +01:00
requirements.txt Improve deletion and add ordering on roles 2017-12-02 19:05:48 +01:00
TODO.md Add basic refill support 2016-06-26 20:07:29 +02:00

pipeline status coverage report

Sith AE

Get started

To start working on the project, just run the following commands:

git clone https://ae-dev.utbm.fr/ae/Sith.git
cd Sith
virtualenv --clear --python=python3 env
source env/bin/activate
pip install -r requirements.txt
./manage.py setup

To start the simple development server, just run python3 manage.py runserver

Generating documentation

There is a Doxyfile at the root of the project, meaning that if you have Doxygen, you can run doxygen Doxyfile to generate a complete HTML documentation that will be available in the ./doc/html/ folder.

Dependencies:

See requirements.txt

You may need to install some dev libraries like libmysqlclient-dev, libssl-dev, libjpeg-dev, or zlib1g-dev to install all the requiered dependancies with pip. You may also need mysql-client. Don't also forget python3-dev if you don't have it already.

You can check all of them with:

sudo apt install libmysqlclient-dev libssl-dev libjpeg-dev zlib1g-dev python3-dev libffi-dev python3-dev libgraphviz-dev pkg-config

The development is done with sqlite, but it is advised to set a more robust DBMS for production (Postgresql for example)

Collecting statics for production:

We use scss in the project. In development environment (DEBUG=True), scss is compiled every time the file is needed. For production, it assumes you have already compiled every files and to do so, you need to use the following commands :

./manage.py collectstatic # To collect statics
./manage.py compilestatic # To compile scss in those statics

Misc about development

Controlling the rights

When you need to protect an object, there are three levels:

  • Editing the object properties
  • Editing the object various values
  • Viewing the object

Now you have many solutions in your model:

  • You can define a is_owned_by(self, user), a can_be_edited_by(self, user), and/or a can_be_viewed_by(self, user) method, each returning True is the user passed can edit/view the object, False otherwise.
    This allows you to make complex request when the group solution is not powerful enough.
    It's useful too when you want to define class-wide permissions, e.g. the club members, that are viewable only for Subscribers.
  • You can add an owner_group field, as a ForeignKey to Group. Second is an edit_groups field, as a ManyToMany to Group, and third is a view_groups, same as for edit.

Finally, when building a class based view, which is highly advised, you just have to inherit it from CanEditPropMixin, CanEditMixin, or CanViewMixin, which are located in core.views. Your view will then be protected using either the appropriate group fields, or the right method to check user permissions.

Counting the number of line of code

# apt install cloc
$ cloc --exclude-dir=doc,env .

Updating doc/SYNTAX.md

If you make an update in the Markdown syntax parser, it's good to document update the syntax reference page in doc/SYNTAX.md. But updating this file will break the tests if you don't update the corresponding doc/SYNTAX.html file at the same time.
To do that, simply run ./manage.py markdown > doc/SYNTAX.html, and the tests should pass again.