Setting COLLECT_API_ENDPOINT in Umami
-
I noticed that the COLLECT_API_ENDPOINT endpoint supposedly needs to be set at build time... how does one go about doing this though when hosting in Cloudron? I've tried setting it and am not having any success. I've tried adding
export
before it too and restarting after saving the changes, no differences in behaviour though.I'm thinking this isn't working. Is there a different way this needs to be set? Has anyone configured this property yet by any chance?
-
https://github.com/umami-software/umami/issues/1318 confirms that this is a build time variable. In the package, we source user environment variables after the build. I am trying to see if it changes anything if we source it before the build.
-
I noticed that the COLLECT_API_ENDPOINT endpoint supposedly needs to be set at build time... how does one go about doing this though when hosting in Cloudron? I've tried setting it and am not having any success. I've tried adding
export
before it too and restarting after saving the changes, no differences in behaviour though.I'm thinking this isn't working. Is there a different way this needs to be set? Has anyone configured this property yet by any chance?
-
@d19dotca Try the latest package, I was able to set to TRACKER_SCRIPT_NAME and COLLECT_API_ENDPOINT to get analytics past ublock origin. Something like:
export TRACKER_SCRIPT_NAME=tellme export COLLECT_API_ENDPOINT=/api/teller
-
N nebulon marked this topic as a question on
-
G girish has marked this topic as solved on
-
G girish referenced this topic on