SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-05-14 12:12:11 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Ghost LXC: Migrate from unsupported MariaDB to MySQL 8 #1102

New Issue
Closed
opened 2025-11-20 05:04:28 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:04:28 -05:00
Owner
Copy Link

Originally created by @benjaminkjh on GitHub (May 15, 2025).

🌟 Briefly describe the feature

Update the Ghost LXC installation script to use MySQL 8 instead of MariaDB

📝 Detailed description

Ghost CMS officially supports MySQL 8 as the sole database backend for production environments. The current Ghost LXC script in this repository utilizes MariaDB, which is not officially supported and may lead to compatibility issues. To ensure alignment with Ghost’s supported configurations and to prevent potential issues with future releases, the script should be updated to install and configure MySQL 8.

Ghost documentation - What databases are supported in production?

💡 Why is this useful?

Utilizing MySQL 8, as officially recommended by the Ghost team, ensures full compatibility with current and future versions of Ghost. This change helps prevent potential issues related to unsupported database behavior and aligns the LXC setup with Ghost’s documented requirements.

Originally created by @benjaminkjh on GitHub (May 15, 2025). ### 🌟 Briefly describe the feature Update the Ghost LXC installation script to use MySQL 8 instead of MariaDB ### 📝 Detailed description Ghost CMS officially supports MySQL 8 as the sole database backend for production environments. The current Ghost LXC script in this repository utilizes MariaDB, which is not officially supported and may lead to compatibility issues. To ensure alignment with Ghost’s supported configurations and to prevent potential issues with future releases, the script should be updated to install and configure MySQL 8. [Ghost documentation - What databases are supported in production?](https://ghost.org/docs/faq/supported-databases) ### 💡 Why is this useful? Utilizing MySQL 8, as officially recommended by the Ghost team, ensures full compatibility with current and future versions of Ghost. This change helps prevent potential issues related to unsupported database behavior and aligns the LXC setup with Ghost’s documented requirements.
saavagebueno added the enhancement label 2025-11-20 05:04:28 -05:00
saavagebueno commented 2025-11-20 05:04:29 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (May 16, 2025):

Reading their docs suggest doing a full database dump and loading it in fresh mysql db

this would mean that you will have to spin up a new LXC with MySQL running, transfer the db and load it up into the database...

https://forum.ghost.org/t/how-to-migrate-from-mariadb-10-to-mysql-8/29575

Also its a 3 year old "breaking change", obviously its not breaking anything. If breakage happens, we will update the script

@tremor021 commented on GitHub (May 16, 2025): Reading their docs suggest doing a full database dump and loading it in fresh mysql db this would mean that you will have to spin up a new LXC with MySQL running, transfer the db and load it up into the database... https://forum.ghost.org/t/how-to-migrate-from-mariadb-10-to-mysql-8/29575 Also its a 3 year old "breaking change", obviously its not breaking anything. If breakage happens, we will update the script
saavagebueno commented 2025-11-20 05:04:29 -05:00
Author
Owner
Copy Link

@benjaminkjh commented on GitHub (May 16, 2025):

This would be the approach for existing installations, but for new users of the script, it would be better if the script just used MySQL in the first place.

@benjaminkjh commented on GitHub (May 16, 2025): This would be the approach for existing installations, but for new users of the script, it would be better if the script just used MySQL in the first place.
saavagebueno commented 2025-11-20 05:04:29 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (May 16, 2025):

Correct. This implies that users on old version of the script are left to dry and need to be able to manually do the migration

@tremor021 commented on GitHub (May 16, 2025): Correct. This implies that users on old version of the script are left to dry and need to be able to manually do the migration
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1102
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?