Open graphiostudio opened 1 week ago
Yes, it is because Coolify detects that if the service is a database or not by the image name. mysql-server
is not in the list. I will update the image list.
(If you know a better way to do this, let me know)
Hey @andrasbacsai, thanks for the reply. That 'mysql-server' was a default by Mixpost template.
I guess, I need to double-check the template compose before deploying. However, the backups disappearing issue still persists. On 355, most databases now have a backups link but setting one doesn't really do anything, they will disappear like the example above. Also, keep getting these discord messages like in this issue: https://github.com/coollabsio/coolify/issues/3395
Error Message and Logs
This issue has been asked numerous times on Discord channel but none of them got proper replies and fixes. There are similar open issues as well. -Some container databases doesn't come with a backup option when you go into their settings. -The ones that have a backup option in their settings do not keep the schedules saved. It DOES work when you set and hit backup now, but a quick refresh or server restart deletes them (not the backup files but the scheduling).
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.349
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 22
Additional Information
Schedule set, backup working and uploaded to S3:
A quick refresh, or server restart, and that schedule is gone. This applies to all container backups, postgres, DB, and MySQL on multiple servers.
And some templates like Mixpost for instance, don't even have the backup option on the container, this also applies to the most recent template on Directus, when I use an old version of the Directus template, backup appears but still, doesn't schedule.