Announcement! Version 0.10 is out now! Check out the release notes.

On this page
This is an older version of the docs. View the latest

Upgrading Portway

An upgrade replaces the application files and keeps configuration and databases.

Breaking changes

Before v1.0.0, releases can include breaking changes. Read the release notes before every upgrade.

Find your current version ​

Windows and Linux releases include .version.txt with the release version. Bug reports reference it.

Steps ​

1. Read the release notes ​

The GitHub release notes list breaking changes, migration steps and new configuration.

2. Back up the installation ​

  • appsettings.json and appsettings.overrides.json
  • auth.db, mcp.db and portway.key
  • environments/
  • endpoints/
  • .core/
  • The file storage directory (FileStorage:StorageDirectory, default storage/files)

3. Stop the application ​

bash
sudo systemctl stop portway
powershell
Stop-WebAppPool -Name "PortwayAppPool"
sh
docker compose down

Stopping resets the in-memory cache and rate limit state.

4. Replace the application files ​

Linux and IIS: extract the release over the existing directory without overwriting appsettings.json, environments/ and endpoints/.

Docker:

sh
docker compose pull && docker compose up -d

5. Apply configuration changes ​

Apply the configuration changes from the release notes to appsettings.json and the environment files.

6. Start and verify ​

  • GET /health/live returns Alive
  • Endpoints respond in a test environment
Last updated: 2026-10-29