-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config customization lost after upgrade #25
Comments
Strangely, I did not have any default frontend (Mangane) change after the upgrade 🤔 |
Solved by 71cd0b7 |
This still occurred for me. Moving from 3.7.1 to 3.9.3. I configure my instance from the config.exs file. So configs, emojis, statuses, and uploads persist. But all theming is lost after an upgrade. |
Are the time located in |
My custom theme was removed from
FWIW this has been an ongoing issue with pleroma_ynh for a while now too. I just keep backups of the important files handy and rebuild the theme after each update. |
Too bad, I was thinking we fixed this… |
Problem:
When we upgrade Akkoma the configuration is reset to default: in fact we loose all custom parameters defined directly in Admin FE. Included the choice of a custom frontend.
This is in fact a dirty side effect of running
migrate_to_db
at every upgrade.Solution:
Exec
migrate_to_db
only at install and not at upgrade.The text was updated successfully, but these errors were encountered: