#12 The resources units should be modifiable as a (local_)settings

Fix #11

Excellent. Two details :

• formatting of the setting parenthesis is not very git-friendly https://code.ffdn.org/jocelyn/transparency/pulls/12/files#diff-0951e555c3efaad48ecd5e80df8144312bf364bR128 (yeah, nitpicking)
• could you document that setting in README.md

I'm really happy to see you around :-)

• formatting of the setting parenthesis is not very git-friendly https://code.ffdn.org/jocelyn/transparency/pulls/12/files#diff-0951e555c3efaad48ecd5e80df8144312bf364bR128 (yeah, nitpicking)

Ok, no problem.

I've a related newbie question: do we have to keep a tuple of tuples for the choices parameter or can it be an array of tuples? What is the difference, with the line 232 for example?

• could you document that setting in README.md

Yes. But as it isn't a required modification, I purpose to add a « Additionnal settings » section to the readme? In which we can move the Organization Name too, to keep only the required parameters for a working env (SECRET_KEY and DEBUG). What do you think?

I've a related newbie question: do we have to keep a tuple of tuples for the choices parameter or can it be an array of tuples? What is the difference, with the line 232 for example?

Does not realy matter, both works. IIRC there is an irrelevant pico-slight performance hit in using lists rather than tuples. IMHO, that is readability that matters most.

   could you document that setting in README.md

Yes. But as it isn't a required modification, I purpose to add a « Additionnal settings » section to the readme? In which we can move the Organization Name too, to keep only the required parameters for a working env (SECRET_KEY and DEBUG). What do you think?

:+1:

Let me know if you upgrade a PR. Gogs is stupid enough not to notice and notify.

PR updated and rebased against master

I've modified heavily the README file, you can see the resulting output there if you want. Hope you'll like it :)