Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Add migration and docs.

  • Loading branch information...
commit b057bd980747cb817dfae98bf11a6a6cb36f67e4 1 parent 76c2de6
@onyxfish onyxfish authored
View
2  docs/amazon.rst
@@ -67,7 +67,7 @@ This is the official PANDA AMI. It may take a moment to return a result. When it
.. _notes above regarding instance types:
-On the next page you'll need to select an **Instance Type**. You are welcome to use (and pay for) a more powerful server, but PANDA has been optimized with the expectation that most organizations will run it on an ``m1.small`` instance. (See the `FAQ <faq>` for information about costs.) This should provide adequate capacity for small to medium-sized groups. We don't recommend trying to run it on a ``t1.micro`` unless you will only be using it for testing.
+On the next page you'll need to select an **Instance Type**. You are welcome to use (and pay for) a more powerful server, but PANDA has been optimized with the expectation that most organizations will run it on an ``m1.small`` instance. (See the :doc:`FAQ <faq>` for information about costs.) This should provide adequate capacity for small to medium-sized groups. We don't recommend trying to run it on a ``t1.micro`` unless you will only be using it for testing.
Click "Next" and keep clicking "Next" until you get to "Configure Security Group" then select "Select an existing security group" and select the one you created in Step 2. Click "Review and Launch. Click "Launch".
View
18 docs/upgrades.rst
@@ -11,7 +11,23 @@ Although we strive to make upgrades as simple as possible, upgrading your PANDA
Your PANDA will be unavailable while upgrading. Typically this will not last more than five minutes, but it will vary by release. You should plan to perform PANDA upgrades during off hours.
-The following release are in **reverse** version order. They **must** be performed in sequence (from lowest version number to highest version number--reverse order on this page).
+The following release are in **reverse** version order. They **must** be performed in sequence (from lowest version number to highest version number--bottom to top order on this page).
+
+1.1.0 to 1.1.1
+==============
+
+To upgrade your PANDA from the 1.1.0 release to the 1.1.1 release, :doc:`SSH <ssh>` into your server and execute the following commands::
+
+ wget https://raw.github.com/pandaproject/panda/1.1.1/scripts/migrations/1.1.0-to-1.1.1.s
+ sudo bash 1.1.0-to-1.1.1.sh
+
+Your PANDA will be stopped, the upgrade will be applied and it will then be restarted. A log of this process will be put in ``/var/log/panda-upgrade-1.1.1.log``.
+
+Check out the :ref:`changelog` to see all the new features and bug fixes in this release!
+
+.. note::
+
+ This release adds German, Italian and Spanish translations. If you would like to modify your existing PANDA installation to run in one of these languages, see :doc:`Selecting the language of your PANDA <i18n>`.
1.0.2 to 1.1.0
==============
View
41 scripts/migrations/1.1.0-to-1.1.1.sh
@@ -0,0 +1,41 @@
+#!/bin/bash
+
+# PANDA Project migration script to ugprade version 1.1.0 to version 1.1.1.
+# Must be executed with sudo!
+
+set -x
+exec 1> >(tee /var/log/panda-upgrade-1.1.1.log) 2>&1
+
+echo "PANDA upgrade beginning."
+
+# Setup environment variables
+export DEPLOYMENT_TARGET="deployed"
+
+# Shutdown services
+service celeryd stop
+service nginx stop
+service uwsgi stop
+service solr stop
+
+# Fetch updated source code
+cd /opt/panda
+git pull
+git checkout 1.1.1
+
+# Update Python requirements (always do this)
+pip install -U -r requirements.txt
+
+# Migrate database (always do this)
+sudo -u panda -E python manage.py migrate panda --noinput
+
+# Regenerate assets (always do this)
+sudo -u panda -E python manage.py collectstatic --noinput
+
+# Restart services
+service solr start
+service uwsgi start
+service nginx start
+service celeryd start
+
+echo "PANDA upgrade complete."
+
Please sign in to comment.
Something went wrong with that request. Please try again.