Slow Startup due to chown'ing all data

[nomadgeek]

Cloudron seems to chown all files every Mastodon starts up. This is terrible for a Mastodon server with all of the media uploads. Please add a way to skip this step. A simple memory adjustment leads to a 30 minute downtime while it loops recursively though all of the files.

[nebulon]

The latest package removes those cache files more eagerly, so this should already help quite a bit.

[subven]

Going through the startup script is a necessary evil to ensure that all apps work accordingly. If you depend on your service having a high uptime, you need to do (and announce) planned maintenances. Altering the configuration or startup process would be a source of user error and Cloudron is built for simplicity and ease of use. So yeah it's not ideal in the case of Mastodon but bearable.

[nomadgeek]

@nebulon noted. I haven't updated to your latest package yet but I'll probably do that later tonight.

I still vote for a "I know what I'm doing, don't chown the files" check mark.

[nomadgeek]

@nomadgeek I'm going to probably move the Mastodon instance into Kubernetes in the long run anyway. I used Cloudron to get started quickly and see if people were interested in even having the service before I put a lot of cash and work into setting up a more robust and complicated configuration.

[nebulon]

Is this still an issue with the latest cache purging?

[nomadgeek]

@nebulon It was still a problem until the most recent update. Server reboot was super quick! Thanks!