Is it normal for the Masa 7.5+ update process on L...
# masacms
a
Is it normal for the Masa 7.5+ update process on Linux / Lucee to change ownership of many /admin/ code files from our original server user to root? Our site admin requests all turn to 403 Forbidden on the assets - apparently after an upgrade. Coincidence? Known issue?
g
When running an update, Masa is pulling a zip file from GitHub and extracts the code. That code is placed on your server. So if the permissions change, that might be due to the configuration of your server and the user that is used to run Lucee.
a
Yes, the prior bug was that: The Masa updater would apply a different user (than the one running Apache) during an update. After this, all of the asset files would become forbidden.
Masa was running as root
I suppose I need to look for the knowledge file that explains which user(s) should be running what on this stack.
After they applied all their changes and restarted everything, this zip file error when I attempted the test update (to see if all the assets would not change ownership any more).