Upgrading MediaCore CE is relatively straightforward:
NOTE 1: yourconf.ini below should be replaced to refer to development.ini or deployment.ini, depending on which one you have set up for your current MediaCore CE installation.
NOTE 2: /path/to/venv and /path/to/mediacore-old below should be replaced with the paths to your MediaCore CE Virtual Environment directory and Installation directory, respectively.
NOTE 3: mediacore-old and mediacore-new below should be replaced with the correct versions for your installation. For example, with MediaCore-0.9.4 and MediaCore-0.10.0, respectively.
NOTE 4: If you’re a developer type, and you’re tracking the latest changes using git, you’ll want to run paster setup-app development.ini after fetching any new changes. This will ensure that your custom appearance css and your Players table are up to date.
If you perform only a minor upgrade (e.g. MediaCore CE 0.10.0 to 0.10.1) you can skip this step.
# Erase the old virtual environment:
cd /path/to/venv
cd ..
mv venv venv.old
# Create a new virtual environment:
virtualenv --no-site-packages venv
# Now, activate that virtual environment
source venv/bin/activate
NOTE 1: Before MediaCore 0.10 the virtualenv folder was named ‘mediacore_env’ in the documentation.
NOTE 2: If you kept your virtualenv inside the MediaCore CE source code directory (as recommended in the docs before version 0.10) please create the new virtualenv next to (not inside) the source code folder (run cd .. before creating the new virtualenv).
Download the latest official release of MediaCore CE from our site, then unpack it beside your current MediaCore CE installation.
# Download the latest distribution beside the current installation
cd /path/to/mediacore-old/..
wget http://mediacorecommunity.org/releases/mediacore-new.tar.gz
# Unpack the downloaded distribution
tar xzvf mediacore-new.tar.gz
# You should now have a mediacore-old directory and mediacore-new directory
# inside your current directory. Check that this is the case:
ls
# Install MediaCore and its dependencies into the new virtual environment
cd mediacore-new
python setup.py develop
Depending on the version you are upgrading from, this step is a little different:
If you your data directory is not inside your MediaCore CE source folder (recommended since MediaCore 0.10) you can skip this step.
If are upgrading from MediaCore CE 0.9.0 or newer, you’ll need to your data directory to a new place. It is recommended that you move the directory and your config file (yourconfig.ini) right next (but not inside) to your mediacore-new directory.
# Navigate to the parent directory, where mediacore-old and mediacore-new
# both reside.
cd /path/to/mediacore-old
cd ..
# Move over the old files (please note that there is no '/' after 'data')
mv ./mediacore-old/data .
mv ./mediacore-old/production.ini .
If you are upgrading from MediaCore CE 0.8.2 or older, you’ll need to move all of the relevant files in ./data/ and ./mediacore/public/images/podcasts/ and ./mediacore/public/images/media/ from your old installation directory. The new data folder should be in the same directory as (but not inside of) mediacore-new.
# Navigate to the parent directory, where mediacore-old and mediacore-new
# both reside.
cd /path/to/mediacore-old
cd ..
# Move over the old media files.
mkdir ./data
mv ./mediacore-old/data/deleted ./data/
mv ./mediacore-old/data/media ./data/
# Move over the old thumbnails.
mv ./mediacore-old/mediacore/public/images/podcasts/[0-9]* ./data/images/podcasts/
mv ./mediacore-old/mediacore/public/images/media/[0-9]* ./data/images/media/
If you perform only a minor upgrade (e.g. MediaCore CE 0.10.0 to 0.10.1) you can skip this step.
For major upgrades it is a good idea to create a new deployment.ini to check for new configuration settings. If you upgrade from MediaCore CE 0.8.1 (or older) this is actually required.
cp yourconf.ini yourconf-old.ini
paster make-config MediaCore deployment.ini
Copying over any modifications you made to the old one. At the very least, this means you should be copying over the database configuration (a line that looks something like):
sqlalchemy.url = mysql://mediacore_user:mysecretpassword@localhost/mediacore?charset=utf8&use_unicode=0
This step is slightly different depending on which version you are upgrading from. See the individual commands below:
# Run the setup/upgrade script to upgrade your database. cd /path/to/mediacore-new paster setup-app yourconf.ini
# Run the upgrade script to upgrade your database. cd /path/to/mediacore-new python batch-scripts/upgrade/upgrade-from-v080.py yourconf.ini
# Run the upgrade script to upgrade your database. cd /path/to/mediacore-new python batch-scripts/upgrade/upgrade-from-v072.py yourconf.ini
If you already had MediaCore CE deployed using mod_wsgi (Apache & mod_wsgi Deployment) or mod_fastcgi (Apache & mod_fcgid Deployment), you’ll want to re-deploy using the new installation. In particular, take note of changes to the deployment configurations (e.g. Apache configuration), changed deployment scripts (e.g. mediacore.wsgi, mediacore.fcgi) and required file permissions.
If you didn’t separate source code and data in your previous version of MediaCore CE, you will need to adapt also the paths in your mediacore.wsgi script (if you are using mod_wsgi).
If you recreated a new virtualenv in step 1 you also have to re-install any plugins you have installed earlier.
When everything works fine your can also remove all the old directories mediacore-old and venv-old).
If you’re upgrading from MediaCore 0.9.x or smaller and you use Facebook comments you have to run a special script to keep your existing Facebook comments. Please read the release notes for more details.
cd /path/to/mediacore-new
python batch-scripts/upgrade/upgrade_from_v09_preserve_facebook_xid_comments.py \
--app-secret=<your-app-secret> yourconfig.ini
Your migration to the latest MediaCore CE is now complete.