You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found the following issue in the main repo that added support for using Docker secrets for any config variable: plausible/analytics#1105
This functionality doesn't appear to be documented anywhere, and also takes a different approach to using Docker secrets than I have seen commonly used in other popular Docker images (i.e. adding separate _FILE environment variables to specify a path to load the secret from).
From what I can tell, Plausible will load any config variable from the config directory (defaults to /run/secrets) when there is a file with a name matching the variable. This should be added as a note somewhere in the docs, and should probably also encouraged to be used for sensitive variables (DATABASE_URL, GOOGLE_CLIENT_SECRET, etc)
The text was updated successfully, but these errors were encountered:
I found the following issue in the main repo that added support for using Docker secrets for any config variable: plausible/analytics#1105
This functionality doesn't appear to be documented anywhere, and also takes a different approach to using Docker secrets than I have seen commonly used in other popular Docker images (i.e. adding separate
_FILE
environment variables to specify a path to load the secret from).From what I can tell, Plausible will load any config variable from the config directory (defaults to /run/secrets) when there is a file with a name matching the variable. This should be added as a note somewhere in the docs, and should probably also encouraged to be used for sensitive variables (DATABASE_URL, GOOGLE_CLIENT_SECRET, etc)
The text was updated successfully, but these errors were encountered: