umami
umami copied to clipboard
Setting the admin password from ENV variables
In order to fully support Infrastructure-as-Code settings, changing the admin password without manual intervention would also introduce additional security.
In case someone is actively searching for a new umami instance on a URL, that person could be faster than the administrator of said instance and gain unprivileged access.
Having the option to set the admin password via an environment variable would solve this issue. (And allows to reset the admin password with a simple restart of the instance.)
To further support infrastructure-as-code settings, it would be great if one could start umami with a simple configuration file stating which websites should exist. Something like this:
websites.conf
some-website-name,predetermined-website-id
other-website-name,other-website-id
This way, I don't have to manually register my website and then manually configure my frontend to use the given identifier.
In case it's helpful to others, here's a way to accomplish both when deploying umami on kubernetes: https://stianlagstad.no/2022/08/deploy-umami-analytics-with-kubernetes/.
This issue is stale because it has been open for 60 days with no activity.
@mikecao seeing this issue going stale, are there any plans for improving the umami-initial setup without touching the database directly as @stianlagstad described?
If there are no plans, should we close this?
This issue is stale because it has been open for 60 days with no activity.
Any updates on this issue?
I'm currently facing a situation where I need to reset the admin
password, and so far haven't been able to find how to do that. Having something like this would certainly make that easier.
This issue is stale because it has been open for 60 days with no activity.
This issue was closed because it has been inactive for 7 days since being marked as stale.
I would still like to see this feature added :(