As the dev-team I'd like to be able to have all of the ports, database config, etc all be centralised in one config file in root (S) #3
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
javascript
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: joshnie/KU-courses#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, all the various components of the project, refer to DATA_DIR separately, their ports are defined locally in the files, and other config options are all done within the code, can we use either .envrc or some other thing to put everything into environment variables and grab the information from there instead?
@KristianDamPedersen
Yes doable, however is it the most important for the MVP? I think this is generally on the high prio list after we are finished, but not quite not :)
Also, please refrain from pulling usecases from the backlog w/o consulting us <3 I am putting this back into scoping, as it is definetly worth discussing, however we should focus on the features required for the MVP first.
Sufficiently done, can be reopened if current solution isn't good enough.