Will Kahn-Greene 2530ef7a1f Split docs into siteadmin and pluginwriter guides
* create initial bits for plugin writer's guide
* move siteadmin stuff to site administrator's guide
* rework index.rst to support multiple guides
* tweak some text
* move files into subdirectories

I verified that this still works with html and texinfo build targets.
There's still a lot of work to do, but this is a good start.
2012-05-23 20:21:03 -04:00

53 lines
1.5 KiB
ReStructuredText

.. 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
<http://creativecommons.org/publicdomain/zero/1.0/>.
=============
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.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.