search

CLARIAH / clariah-plus

This is the project planning repository for the CLARIAH-PLUS project. It groups all technical documents and discussions pertaining to CLARIAH-PLUS in a central place and should facilitate findability, transparency and project planning, for the project as a whole.
9 stars 6 forks source link

software requirements: change for configuration via environment variables #103

Closed proycon closed 2 years ago

proycon commented 2 years ago

This removes "all configuration MUST be in environment variables" from point 5 (which was not too strict and not the best place) in favour of a more strongly formulated point 15.3 (discussion in #102)

jblom commented 2 years ago

@proycon much clearer now. It would perhaps help out to illustrate a full "configuration chain" (from local dev/code, to running containers) in a separate README or wiki page (amongst other more advanced topics emerging from the requirements). We could then refer to these elaborate examples from the reqs.

jblom commented 2 years ago

@proycon much clearer now. It would perhaps help out to illustrate a full "configuration chain" (from local dev/code, to running containers) in a separate README or wiki page (amongst other more advanced topics emerging from the requirements). We could then refer to these elaborate examples from the reqs.

4tikhonov commented 2 years ago

A set of Common Software Quality Assurance Baseline Criteria for Research Projects https://digital.csic.es/bitstream/10261/160086/10/sqa-baseline-v4.0.pdf

proycon commented 2 years ago

Agreed, it's good to have some examples of 'full configuration chains' to refer to. I'm hoping we get more and more of those as we go on.