Native handling of docker secrets

[EnsuingRequiem]

Is your feature request related to a problem? Please describe. The only "problem" is the plain-text storage of secrets.

Describe the solution you'd like A native implementation to pull sensitive information from Docker secrets. This can be done either in the existing docker-entrypoint.sh or some Ruby-specific method.

Describe alternatives you've considered Indirect parameter extension via a custom entrypoint.sh prior to the existing ENTRYPOINT and CMD entries in the Dockerfile. While this approach technically works, it created other unforeseen issues with flipper_gates table and/or validate_secret_key_base (as discovered and discussed in the Matrix chat)

Additional context Typically, Docker secrets are bind-mounted to a file on /run/secrets/<secret name> with the file being owned by the uid running the container. Approaches in other images typically involve allowing a user to set either the base environment variable (e.g., SECRET_KEY_BASE) or an environment variable pointing to the path to find the contents (e.g., SECRET_KEY_BASE_FILE)

[Floppy]

Thanks - I'll take a look into this!