.. MediaGoblin Documentation Written in 2012 by MediaGoblin contributors To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty. You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see . ============= Release Notes ============= 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. 0.3.1 ===== **Do this to upgrade** 1. Make sure to run ``bin/gmg dbuptdate`` after upgrading. 2. If you set up your server config with an older version of mediagoblin and the mediagoblin docs, it's possible you don't have the "theme static files" alias, so double check to make sure that section is there if you are having problems. **New features** * **theming support** MediaGoblin now also includes theming support, which you can read about in the section :ref:`theming-chapter`. * **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 :ref:`core-plugin-section` for plugin documentation 0.3.0 ===== 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: 1. Make sure your MongoDB is still running and has your data, it's needed for the conversion. 2. Configure the ``sql_engine`` URI in the config to represent your target database (see: :ref:`deploying-chapter`) 3. You need an empty database. 4. Then run the following command:: bin/gmg [-cf mediagoblin_config.ini] convert_mongo_to_sql 5. Start your server and investigate. 6. That's it.