<![CDATA[upgrade broke TRACKER_SCRIPT_NAME]]>I have used a custom environment variable to set a custom file name for my umami installation but about a month ago an automated upgrade apparently broke that. In fact, I can't even see in the settings now where it's possible to SET custom environment variables for the app. Was this a deprecation in cloudron? It doesn't appear to be related to changes in umami itself.

]]>https://forum.cloudron.io/topic/9728/upgrade-broke-tracker_script_nameRSS for NodeSun, 12 Apr 2026 17:19:27 GMTFri, 28 Jul 2023 16:00:55 GMT60<![CDATA[Reply to upgrade broke TRACKER_SCRIPT_NAME on Sat, 29 Jul 2023 02:49:02 GMT]]>@psifertex iirc, I think that changed happenned from 1.x to 2.x .

]]>https://forum.cloudron.io/post/71038https://forum.cloudron.io/post/71038Sat, 29 Jul 2023 02:49:02 GMT<![CDATA[Reply to upgrade broke TRACKER_SCRIPT_NAME on Fri, 28 Jul 2023 18:27:20 GMT]]>Found the bug. The variable previously appended .js but apparently an upgrade either truncated the config file, or the umami code itself changed such that the extension wasn't used.

]]>https://forum.cloudron.io/post/71028https://forum.cloudron.io/post/71028Fri, 28 Jul 2023 18:27:20 GMT<![CDATA[Reply to upgrade broke TRACKER_SCRIPT_NAME on Fri, 28 Jul 2023 16:30:56 GMT]]>I just double checked and env.sh hasn't been changed, so not sure why the environment var is being ignored. It contains:

root@ab8ccac7-d2dc-4371-9cb8-0c0907fa15a9:/app/data# cat env.sh 
# https://umami.is/docs/environment-variables
export HASH_SALT=<REMOVED>
export TRACKER_SCRIPT_NAME=yummi
]]>https://forum.cloudron.io/post/71016https://forum.cloudron.io/post/71016Fri, 28 Jul 2023 16:30:56 GMT