Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Umami
  3. upgrade broke TRACKER_SCRIPT_NAME

upgrade broke TRACKER_SCRIPT_NAME

Scheduled Pinned Locked Moved Umami
4 Posts 2 Posters 522 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      P Offline
      psifertex
      wrote on last edited by
      #1

      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.

      1 Reply Last reply
      0
      • P Offline
        P Offline
        psifertex
        wrote on last edited by psifertex
        #2

        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
        
        1 Reply Last reply
        0
        • P Offline
          P Offline
          psifertex
          wrote on last edited by
          #3

          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.

          girishG 1 Reply Last reply
          1
          • P psifertex

            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.

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            @psifertex iirc, I think that changed happenned from 1.x to 2.x .

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search