Updating

Update Pepper from Settings > Update. You need an owner or admin account and the new release ZIP from your purchase or support channel.

For a container installation, follow the Docker update and runtime steps. The whole installation must stay on its persistent volume.

Before you update

Create a backup in Settings > Backups and verify it on a separate installation. Test the update on a staging copy before you update your live installation.

Check the server requirements. Keep the original installation and its data until you have verified the update or restored replacement.

Portable backups need no database command-line tools. If your installation uses SQL safety backups, ask your host to confirm that its tools match the database: MySQL tools for MySQL, or MariaDB tools for MariaDB. If they do not match, use a portable export and restore it into a separate, empty installation. If portable export is unavailable, arrange matching tools before creating a backup or updating.

Desks and AI client changes

An update that introduces Desks keeps existing people on Everything. Their records stay in place. Owners and admins can then arrange and assign desks.

For AI client integrations, lists use limit, cursor, sort and dir, with rows in data and continuation in next_cursor. The older page, per_page and after inputs remain accepted. Update clients that read data.rows to read data. Read the list contract.

An AI client that qualifies a lead must link an existing customer. Prepare and approve a customer creation first when needed. Read Sales tools.

Existing role-change approvals without a bound role must be prepared again. Restoring a backup also makes waiting approvals stale. Review the approval rules before retrying a request.

Regional settings and optional work tools

Updates preserve saved formatting choices, tax rates and issued originals. Review regional defaults before changing existing overrides. Configure tax classes and rules before selecting them on sales lines. Pepper does not infer tax jurisdiction.

Docs, Calendar and Automations follow current permissions and desk assignments. Owners and admins can review access after updating. Automation rules start inactive and need review before activation.

Assistant starts off. An owner must choose a provider and review data disclosure before enabling it. Provider charges are separate. Ordinary work and MCP need no generation provider.

1. Add the ZIP

Keep the ZIP intact. Choose either method below.

Upload from the dashboard

1. Open Settings > Update.
2. Click Choose a ZIP file, or drop the ZIP on the upload area.
3. Click Upload package.

Upload with SFTP

Use this method if the ZIP exceeds the dashboard's upload limit.

1. Open Settings > Update to create the update folder.
2. Connect to your hosting account with SFTP or its file manager.
3. Upload the ZIP to storage/app/private/updates inside your Pepper installation.
4. Return to Settings > Update.
5. Click Refresh list.

Upload the ZIP file itself. Do not extract it over the application files.

2. Check the package

Click Check package beside the ZIP under Uploaded packages. Pepper checks the files, supported starting version and server requirements.

These checks change nothing. If a check fails, fix the stated cause and check again. Ask your host or support if you need help.

3. Install the update

1. Click Install update.
2. Read the confirmation.
3. Click Install update to confirm.
4. Keep the page open until it shows the result.

Pepper enters maintenance mode, creates a backup and installs the update. The site returns online when the update succeeds. If a step fails, it restores the previous files and database.

Your records, uploaded files, issued originals and settings stay in place. The update replaces application code, so keep custom code separately.

Move an older backup to a newer installation

Use fresh browser setup when you need another installation. Choose Import a backup. Use a newer package that supports the backup’s starting version. Import applies the updates and verifies the result before activation. The destination must be empty.

Follow the older backup import steps. Keep the source stopped during a move.

If something goes wrong

If the connection drops, reload the Update page. If an update fails and recovery cannot finish, the site stays in maintenance mode.

Migration rollback commands cannot undo an update. Recover from a verified backup with matching code.

Read update checks and recovery messages, or contact support. Server operators can use replacement recovery when the dashboard is unavailable.