[Feature]: Configuration via environment variables

[ajsokolik]

What do you imagine 💭

Allow full configuration via environment variables (with full documentation) so an installation could be fully deployed via Docker Compose or Kubernetes configMaps and skip the setup process.

This would allow me to version control the settings as well as setup things like external database (I know in the future), authentication settings, etc. without having maintain a config file or have to something like an initContainer to copy a config file I maintain as a configMap.

Great project! It looks fantastic and all the hard work is greatly appreciated.

I have checked the other issues and pull-requests for similar issues.

• [x] I've checked existing issues
• [x] I've checked existing pull-requests

[KSJaay]

Thanks for the feedback, this was something we used to have but moved away from because I thought that the UI screen was a lot cleaner and easier for most users to manage.

I think having a system that allows users to configure using ENV might actually be a good idea for some of the future stuff I'm currently developing.

[ajsokolik]

Yeah, I'm not opposed to a mechanism to have if configured in a UI, but maybe something where the ENV vars take precedent over a config file? Then it's a "best of both worlds" kind of situation?

Again, awesome work on the project and it really is great!

[KSJaay]

Yeah, it'll be something that I'll add in the future. Currently a little bit low on the list, there's a few extra things that we need to focus on right now.

Thank you!!

[ajsokolik]

Absolutely. There is always a ton to do and I would always expect the basic functionality stuff would get addresses first. This is more of a "wish list" kind of item that can live in the back log for a while.