<NME> 1 - Upgrading from version 2.0.x to version 2.1.x
<BEF> ADDFILE
<MSG> Add 2.0.x -> 2.1.x upgrade guide and reorder other guides located in the same folder.

<DFF> @@ -0,0 +1,65 @@
+h2. Upgrading from version 2.0.10 to version 2.1.x
+
+This guide will guide you through the upgrade process from version 2.0.10 to version 2.1.x.
+
+endprologue.
+
+WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend that you upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.
+
+WARNING. Before continuing make sure you have a backup copy of your application and database in case something goes wrong.
+
+h3. Updating gems
+
+Open up your application's Gemfile and change the version of the +refinerycms+ gem entry from +2.0.10+ to +2.1.0+.
+
+After you complete the steps above your Gemfile should look like this:
+
+<ruby>
+gem "refinerycms", "~> 2.1.0"
+</ruby>
+
+Now run +bundle update+ and let it install new gems.
+
+h3. Running Refinery's CMS generator
+
+WARNING: If the application you will be upgrading is using a SQLite database then you need to read +Refinery's CMS generator and SQLite database+.
+
+Go to the terminal and run following command:
+
+<shell>
+rails generate refinery:cms
+</shell>
+
+This command will do a couple of things:
+
+* Add two css requires in +application.css+.
+* Update +app/views/sitemap/index.xml.builder+ template.
+* Wrap  +config.action_mailer+ config entry in a conditional +if config.respond_to?(:action_mailer)+ clause for each environment file located in +app/config/environments+.
+* Copy new migrations.
+* Run +rake db:migrate+ and +rake db:seed+ commands.
+
+NOTE: If you don't want the generator to run +rake db:migrate+ and +rake db:seed+ commands pass the +--skip_db+ option when invoking the generator:
+
+<shell>
+rails generate refinery:cms --skip_db
+</shell>
+
+h3. Refinery's CMS generator with a SQLite database
+
+INFO. Because SQLite can only handle index names that are no longer than 64 characters you will have to edit one of the migrations that will be generated when you run the following command in the terminal:
+
+<shell>
+rails generate refinery:cms --skip_db
+</shell>
+
+Go inside of +db/migrate+ and find a migration called +<timestamp>_remove_meta_keywords_from_seo_meta.seo_meta.rb+. Open it in the editor of your choice and replace everything with the code from "Uģis' gist":https://gist.github.com/ugisozols/5998256.
+
+What this will do is check if the +seo_meta+ table has an index named +index_seo_meta_on_seo_meta_id_and_seo_meta_type+ and in case it does it will:
+
+* Remove the current index named +seo_meta_id_and_seo_meta_type+.
+* Remove the +meta_keywords+ column.
+* Add back the original index but with a shorter name.
+
+Now run +rake db:migrate+.
+
+h3. Profit!

{'commit': 'diff --git a/doc/guides/6 - Updating Refinery/1 - Upgrading from version 2.0.x to version 2.1.x b/doc/guides/6 - Updating Refinery/1 - Upgrading from version 2.0.x to version 2.1.x\nnew file mode 100644\nindex 000000000..003a34fc4\n--- /dev/null\n+++ b/doc/guides/6 - Updating Refinery/1 - Upgrading from version 2.0.x to version 2.1.x\t\n@@ -0,0 +1,65 @@\n+h2. Upgrading from version 2.0.10 to version 2.1.x\n+\n+This guide will guide you through the upgrade process from version 2.0.10 to version 2.1.x.\n+\n+endprologue.\n+\n+WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend that you upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.\n+\n+WARNING. Before continuing make sure you have a backup copy of your application and database in case something goes wrong.\n+\n+h3. Updating gems\n+\n+Open up your application\'s Gemfile and change the version of the +refinerycms+ gem entry from +2.0.10+ to +2.1.0+.\n+\n+After you complete the steps above your Gemfile should look like this:\n+\n+<ruby>\n+gem "refinerycms", "~> 2.1.0"\n+</ruby>\n+\n+Now run +bundle update+ and let it install new gems.\n+\n+h3. Running Refinery\'s CMS generator\n+\n+WARNING: If the application you will be upgrading is using a SQLite database then you need to read +Refinery\'s CMS generator and SQLite database+.\n+\n+Go to the terminal and run following command:\n+\n+<shell>\n+rails generate refinery:cms\n+</shell>\n+\n+This command will do a couple of things:\n+\n+* Add two css requires in +application.css+.\n+* Update +app/views/sitemap/index.xml.builder+ template.\n+* Wrap  +config.action_mailer+ config entry in a conditional +if config.respond_to?(:action_mailer)+ clause for each environment file located in +app/config/environments+.\n+* Copy new migrations.\n+* Run +rake db:migrate+ and +rake db:seed+ commands.\n+\n+NOTE: If you don\'t want the generator to run +rake db:migrate+ and +rake db:seed+ commands pass the +--skip_db+ option when invoking the generator:\n+\n+<shell>\n+rails generate refinery:cms --skip_db\n+</shell>\n+\n+h3. Refinery\'s CMS generator with a SQLite database\n+\n+INFO. Because SQLite can only handle index names that are no longer than 64 characters you will have to edit one of the migrations that will be generated when you run the following command in the terminal:\n+\n+<shell>\n+rails generate refinery:cms --skip_db\n+</shell>\n+\n+Go inside of +db/migrate+ and find a migration called +<timestamp>_remove_meta_keywords_from_seo_meta.seo_meta.rb+. Open it in the editor of your choice and replace everything with the code from "Uģis\' gist":https://gist.github.com/ugisozols/5998256.\n+\n+What this will do is check if the +seo_meta+ table has an index named +index_seo_meta_on_seo_meta_id_and_seo_meta_type+ and in case it does it will:\n+\n+* Remove the current index named +seo_meta_id_and_seo_meta_type+.\n+* Remove the +meta_keywords+ column.\n+* Add back the original index but with a shorter name.\n+\n+Now run +rake db:migrate+.\n+\n+h3. Profit!\ndiff --git a/doc/guides/6 - Updating Refinery/1 - Upgrading to the Latest Stable Version.textile b/doc/guides/6 - Updating Refinery/2 - Upgrading to the Latest Stable Version.textile\nsimilarity index 100%\nrename from doc/guides/6 - Updating Refinery/1 - Upgrading to the Latest Stable Version.textile\nrename to doc/guides/6 - Updating Refinery/2 - Upgrading to the Latest Stable Version.textile\ndiff --git a/doc/guides/6 - Updating Refinery/2 - Upgrading to Edge.textile b/doc/guides/6 - Updating Refinery/3 - Upgrading to Edge.textile\nsimilarity index 100%\nrename from doc/guides/6 - Updating Refinery/2 - Upgrading to Edge.textile\nrename to doc/guides/6 - Updating Refinery/3 - Upgrading to Edge.textile\n', 'commit_subject': 'Add 2.0.x -> 2.1.x upgrade guide and reorder other guides located in the same folder.', 'repo_name': 'refinery/refinerycms', 'committer': {'name': 'Uģis Ozols', 'email': '2034ff49f86b31154f8bd08550f3de750ddb116b@gmail.com', 'time_sec': '1373877892', 'tz_offset': '180', 'date': {'seconds': '1373877892'}}, 'commit_tree': 'ec23214e571a1b269a828697ad8076b900586284', 'commit_message': 'Add 2.0.x -> 2.1.x upgrade guide and reorder other guides located in the same folder.\n', 'language_name': 'HTML', 'license': 'mit', 'hunks': '@@ -0,0 +1,65 @@\n+h2. Upgrading from version 2.0.10 to version 2.1.x\n+\n+This guide will guide you through the upgrade process from version 2.0.10 to version 2.1.x.\n+\n+endprologue.\n+\n+WARNING. This guide assumes that you will be upgrading from version 2.0.10 of Refinery CMS. If your application is not up-to-date we strongly recommend that you upgrade it to version 2.0.10 before trying to upgrade to version 2.1.0.\n+\n+WARNING. Before continuing make sure you have a backup copy of your application and database in case something goes wrong.\n+\n+h3. Updating gems\n+\n+Open up your application\'s Gemfile and change the version of the +refinerycms+ gem entry from +2.0.10+ to +2.1.0+.\n+\n+After you complete the steps above your Gemfile should look like this:\n+\n+<ruby>\n+gem "refinerycms", "~> 2.1.0"\n+</ruby>\n+\n+Now run +bundle update+ and let it install new gems.\n+\n+h3. Running Refinery\'s CMS generator\n+\n+WARNING: If the application you will be upgrading is using a SQLite database then you need to read +Refinery\'s CMS generator and SQLite database+.\n+\n+Go to the terminal and run following command:\n+\n+<shell>\n+rails generate refinery:cms\n+</shell>\n+\n+This command will do a couple of things:\n+\n+* Add two css requires in +application.css+.\n+* Update +app/views/sitemap/index.xml.builder+ template.\n+* Wrap  +config.action_mailer+ config entry in a conditional +if config.respond_to?(:action_mailer)+ clause for each environment file located in +app/config/environments+.\n+* Copy new migrations.\n+* Run +rake db:migrate+ and +rake db:seed+ commands.\n+\n+NOTE: If you don\'t want the generator to run +rake db:migrate+ and +rake db:seed+ commands pass the +--skip_db+ option when invoking the generator:\n+\n+<shell>\n+rails generate refinery:cms --skip_db\n+</shell>\n+\n+h3. Refinery\'s CMS generator with a SQLite database\n+\n+INFO. Because SQLite can only handle index names that are no longer than 64 characters you will have to edit one of the migrations that will be generated when you run the following command in the terminal:\n+\n+<shell>\n+rails generate refinery:cms --skip_db\n+</shell>\n+\n+Go inside of +db/migrate+ and find a migration called +<timestamp>_remove_meta_keywords_from_seo_meta.seo_meta.rb+. Open it in the editor of your choice and replace everything with the code from "Uģis\' gist":https://gist.github.com/ugisozols/5998256.\n+\n+What this will do is check if the +seo_meta+ table has an index named +index_seo_meta_on_seo_meta_id_and_seo_meta_type+ and in case it does it will:\n+\n+* Remove the current index named +seo_meta_id_and_seo_meta_type+.\n+* Remove the +meta_keywords+ column.\n+* Add back the original index but with a shorter name.\n+\n+Now run +rake db:migrate+.\n+\n+h3. Profit!\n', 'addition_count': 65, 'deletion_count': 0, 'src_file': '/dev/null', 'tgt_file': 'b/doc/guides/6 - Updating Refinery/1 - Upgrading from version 2.0.x to version 2.1.x', 'file_extension': '.x', 'before_file': 'ADDFILE', 'message': 'Add 2.0.x -> 2.1.x upgrade guide and reorder other guides located in the same folder.\n', 'author_name': 'Uģis Ozols', 'lang': '0'}