Updating October CMS
Instructions for keeping your October CMS website up to date.
october:update command will request updates from the October gateway. It will update the core application and plugin files, then perform a database migration.
php artisan october:update
# Database Migration
october:migrate command will perform a database migration, creating database tables and executing seed scripts, provided by the system and plugin version history. The migration command can be run multiple times, it will only execute a migration or seed script once, which means only new changes are applied.
php artisan october:migrate
--rollback option will reverse all migrations, dropping database tables and deleting data. Care should be taken when using this command. The plugin refresh command is a useful alternative for debugging a single plugin.
php artisan october:migrate --rollback
--skip-errors option will ignore any exceptions that occur during the migration process. This can be useful in cases where tables already exist, but version information should still be applied.
php artisan october:migrate --skip-errors
# Bleeding Edge Updates
To receive bleeding edge updates of October CMS, change the minimum stability setting to
composer config minimum-stability dev
Then target the
develop branch in the composer.json file. For example:
develop branch includes updates that are not released in the stable channel yet. There can be the latest bug fixes and features, but at the same time, it can contain unfinished work. Enabling bleeding edge updates is not recommended for production environments.
dev-develop notation may also apply to some plugins and themes.
# Upgrade Guide from v1 and v2
If your starting point is October CMS 2.0, please observe the following guides when performing the upgrade.
- October CMS v3.0 Upgrade Guide (opens new window)
- October CMS v3.1 Stable Release (opens new window)
If your starting point is October CMS 1.0, please observe these guides before continuing with the above guides.