Hi @james-callahan this should be possible using https://plugins.matomo.org/EnvironmentVariables Let me know if that doesn't work.

Let me know if that doesn't work.

It didn't work: when using MATOMO_GENERAL_SALT it generated a new salt.

@james-callahan I suppose the server is restarted and everything? How did you check the value was not used? Cause the config file itself might still show the old value but the value is actually applied

@james-callahan I suppose the server is restarted and everything? How did you check the value was not used? Cause the config file itself might still show the old value but the value is actually applied

Yes I'm running inside of docker: I killed the container and recreated it (allowing matomo to generate a new config.php.ini)
Once it started I cat'd the file and saw the salt was not equal to the one in my env var.

@tsteur how can I check what matomo is using as the current salt?

That's a great question @james-callahan . Because the salt is anonymised in our diagnostics config screen in our Admin section for security reasons it's actually not that easy. Created for now matomo-org/plugin-EnvironmentVariables#8

The only thing I could think of right now would be to trigger an action that would force the update of the config file in which case the salt from the environment variable would be written to disc.

• You could log in as a super user
• Go to admin section (cog icon in top right)
• Go to "General settings"
• In the section "Trusted Matomo Hostname" temporarily add a new hostname
• Click save
• Check if the salt was updated.

I haven't tested this but thinking this procedure should work. Let me know.

• In the section "Trusted Matomo Hostname" temporarily add a new hostname

• Click save

• Check if the salt was updated.

Yep that seems to have worked; thanks!
Should there be an easier way to check this?

Yes definitely. there should be an easier way. That's why I created matomo-org/plugin-EnvironmentVariables#8 so it hopefully will help with this in the future.