Feature request: k8s friendly handling of config.json and localUser.json #150
Description
It would be really helpful if the injection of configuration variables can be fully migrated to environment variables. This would allow users to deploy these tools to a k8s environment without having to manually encrypt database, slack, and localUser hash variables. Instead, the tool will rely on injecting these configuration variables via ENV/Config maps. This would also allow users to select their password management solution - like AWS Secrets, K8s secrets or a KMS related solution. Messing around with a node encryption script isn't great