This chapter has important information for releases in it. If you’re upgrading from a previous release, please read it carefully, or at least skim over it.
This will be the last release that is capable of converting from an earlier MongoDB-based MediaGoblin instance to the newer SQL-based system.
New features
TO BE FILLED IN BEFORE RELEASE :-)
trim_whitespace
We bundle the optional plugin trim_whitespace which reduces the size of the delivered html output by reducing redundant whitespace.
See Part 2: Core plugin documentation for plugin documentation
Do this to upgrade
New features
theming support
MediaGoblin now also includes theming support, which you can read about in the section Theming MediaGoblin.
flatpages
MediaGoblin has a flatpages plugin allowing you to add pages that are aren’t media-related like “About this site...”, “Terms of service...”, etc.
See Part 2: Core plugin documentation for plugin documentation
This release has one important change. You need to act when upgrading from a previous version!
This release changes the database system from MongoDB to SQL(alchemy). If you want to setup a fresh instance, just follow the instructions in the deployment chapter. If on the other hand you want to continue to use one instance, read on.
To convert your data from MongoDB to SQL(alchemy), you need to follow these steps:
Make sure your MongoDB is still running and has your data, it’s needed for the conversion.
Configure the sql_engine URI in the config to represent your target database (see: Deploying MediaGoblin)
You need an empty database.
Then run the following command:
bin/gmg [-cf mediagoblin_config.ini] convert_mongo_to_sql
Start your server and investigate.
That’s it.