Tracking actions (aka logging) #2
Assignees
Comments
hexylena
added a commit
that referenced
this issue
Sep 4, 2018
hexylena
pushed a commit
that referenced
this issue
Oct 11, 2018
Just wanted to share the changes I've made while getting ready to run this in freiburg. - many python style changes - I've made everything flake8 compliant (minus line length since) - `python/denbi/` was moved up to just be `denbi/` which is more to my experience - Scripts are moved into `denbi/scripts` - `setup.py` is modified to be aware of the scripts, when `pip install`ing this module, those will now be placed on the user's path for their convenience. - more complete .gitignore from [gitignore.io](https://www.gitignore.io/) - fixes #2 adds logging whenever a modifying or destruction keystone call is made - fixes #16 adds a --read-only flag (could be renamed, meh.) to the `perun_propagation` file-based script. - documentation fixes, how to run with gunicorn if flasks's warning gives you concern. - Makefile which has `lint` and `test` targets and serves as documentation of how to do both of those things (running tests was not otherwise documented.) - Adds a Dockerfile - Adds a docker-compose.yml in case you want to run a pKA/keystone locally. - Adds sphinx based documentation - fixes #18
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should add Python logging facilities to provide a simple tracking of actions like user/project create/list/delete.
The text was updated successfully, but these errors were encountered: