Upgrading IXP Manager

These upgrade instructions relate to upgrading when you are already using IXP Manager v4.x.

We track releases on GitHub.

You will find standard instructions for upgrading IXP Manager below. Note that the release notes for each version may contain specific upgrade instructions including schema changes.

If you have missed some versions, the most sensible approach is to upgrade to each minor release in sequence (4.5.0 -> 4.6.0 -> 4.7.0 -> ...) and then to the latest patch version in the latest minor version.

In the below, we assume the following installation directory - alter this to suit your own situation:


The general process is:

  1. Enable maintenance mode:

    cd $IXPROOT
    ./artisan down
  2. Using Git, checkout the next minor / latest patch version up from yours. For IXP Manager v4.

    # move to the directory where you have installed IXP Manager
    cd $IXPROOT
    # pull the latest code
    git fetch
    # check out the version you are upgrading to
    git checkout v4.x.y
  3. Install latest required libraries from composer (see notes below):

    composer install
  4. Install latest frontend dependencies (see notes below):

    # if asked to chose a jquery version, chose the latest / highest version offered
    bower prune
    bower install
  5. Restart Memcached and clear the cache. Do not forget / skip this step!

    systemctl restart memcached.service
    ./artisan cache:clear
  6. Update the database schema:

    # review / sanity check first:
    ./artisan doctrine:schema:update --sql
    # If in doubt, take a mysqldump of your database first.
    # migrate:
    ./artisan doctrine:schema:update --force
  7. Restart Memcached (yes, again). Do not forget / skip this step!

    systemctl restart memcached.service
  8. Ensure there are no version specific changes required in the release notes.

  9. Ensure file permissions are correct.

    MY_WWW_USER=www-data  # fix as appropriate to your operating system
    chown -R $MY_WWW_USER: bootstrap/cache var storage
    chmod -R u+rwX bootstrap/cache var storage
  10. Disable maintenance mode:

    ./artisan up

Updating Bower Dependancies

It is not advisable to run bower are root but how you run it will depend on your own installation.

If you installed IXP Manager via the installation scripts, then it will have changed ownership on directories that the web server does not need to write to to root.

The following options would work on Ubuntu (as root):

# set this to your IXP Manager installation directory

# update bower
sudo -u www-data bash -c "HOME=${IXPHOME}/storage && cd ${IXPHOME} && bower --config.interactive=false -f update"

The above command is structured as it is because typically the www-data user has a nologin shell specified.

Your mileage may vary on this and we're happy to accept pull requests with other options.

Updating Composer Dependancies

This is similar to the bower section above so please read that if you have not already.

The following options would work on Ubuntu (as root):

# set this to your IXP Manager installation directory

# update bower
sudo -u www-data bash -c "HOME=${IXPHOME}/storage && cd ${IXPHOME} && composer install"

Correcting Database Issues / Verifying Your Schema

Because of the manual process of database updates, it is possible your database schema may fall out of sync.

If you are having issues, first and foremost, restart Memcached. Doctrine2 caches entities and schema information in Memcached so, after an upgrade, you must restart Memcached.

You can verify and update your schema using the artisan script. The first action should be validation - here is a working example with no database issues:

./artisan doctrine:schema:validate

Validating for default entity manager...
[Mapping]  OK - The mapping files are correct.
[Database] OK - The database schema is in sync with the mapping files.

If there are issues, you can use the following to show what SQL commands are required to bring your schema into line:

./artisan doctrine:schema:update --sql

And you can let Doctrine make the changes for you via:

./artisan doctrine:schema:update --force

Doctrine2 maintains the entities, proxies and repository classes. Ideally you should never need to do the following on a production installation - as we maintain these files with Git - but if you're developing / testing IXP Manager, you may need to.

The process for updating these files with schema changes / updates is:

/etc/init.d/memcached restart    # (or as appropriate for your system)
./artisan doctrine:generate:entities database
./artisan doctrine:generate:proxies

Some older scripts also rely on MySQL view tables that may be missing. You can safely run this to (re)create them:

mysql -u ixp -p ixp < $IXPROOT/tools/sql/views.sql