Updating to beta from latest stable

caution

Updating to the beta version is only available from the latest stable release! Select "1.2.x (Latest)" from the dropdown in the top-right corner and follow the update instructions first.

danger

We don't recommend testing beta on production installs, as this version may contain unknown critical bugs. Ideally, clone your database from the current version and set up a second test instance of CtrlPanel alongside your production install on a separate domain. Rolling back after an update is NOT possible.

danger

Always backup your database and any code changes before updating! It's better to not need them, than to lose everything when you do. We've explained how to do that here.

Without a backup, you won't be able to roll back without losing all your data.

Enable Maintenance Mode

cd /var/www/ctrlpanel
php artisan down

Pulling the New Files

git stash
git checkout development
git pull

Update Dependencies

COMPOSER_ALLOW_SUPERUSER=1 composer install --no-dev --optimize-autoloader

Updating the Database

php artisan migrate --seed --force
php artisan permissions:sync

Clear Compiled Template Cache

php artisan cache:clear
php artisan route:clear
php artisan view:clear
php artisan config:clear
php artisan settings:clear-cache

Set Permissions

# If using NGINX or Apache (not on CentOS):
chown -R www-data:www-data /var/www/ctrlpanel/
chmod -R 755 /var/www/ctrlpanel

# If using NGINX on CentOS:
chown -R nginx:nginx /var/www/ctrlpanel/
chmod -R 755 /var/www/ctrlpanel

# If using Apache on CentOS
chown -R apache:apache /var/www/ctrlpanel/
chmod -R 755 /var/www/ctrlpanel

Restarting Queue Workers

After every update, you should restart the queue worker to ensure that the new code is loaded in and used.

php artisan queue:restart

Disable Maintenance Mode

php artisan up

Disclaimer

If you notice any bugs 🐛, would like something to be improved , added or just need help with beta version, let us know by creating a forum post in #🧪┃beta-feedback channel on our Discord server.
For any major security risk, create GitHub vulnerability report and DM 1day2die in Discord. Avoid discussing vulnerabilities in public chats, and also do not create reports on public trackers!