RUN IT WELL
Upgrade Tallylamp while keeping browser profiles
A Tallylamp upgrade replaces the running service image. Your database and persistent Chrome profiles live on the data volume, which must stay attached to the replacement.
Your deployment stays on its chosen image
The Railway template uses a public GHCR release pinned to a digest. A digest identifies exact image contents. With automatic updates disabled, your service stays on that image when the source code changes or a new release comes out.
Tallylamp publishes versioned release images and has no floating latest tag. Keep the image reference you are running in your deployment notes, along with the backup taken before each change.
Before changing the image
Read the target release notes
Check the changes and any database migration or configuration requirements. Choose the published image reference for that release.
Finish active browser work
Tell agents that the service will restart. A redeploy interrupts all Chrome processes; persistent profiles do not make active tasks continuous.
Back up /data
Take a consistent backup of the database and profiles using your host's supported process. Stop active work first, and keep the backup protected as credential-bearing data.
Record the current version
Save the current image reference and the matching backup before replacing either. You may need both if the new release changes the database format.
Change the image, keep the volume
On Railway, replace the service's image reference with the new release digest. Keep the existing /data volume and variables, with one replica and automatic image updates disabled. Redeploy the service.
With Docker, stop the old container and start the chosen release with the same named volume and required settings. Do not delete the data volume when removing the old container.
Check the service and one saved profile
| Check | Expected result |
|---|---|
| Health | /healthz returns a successful status. |
| Dashboard | You can sign in and see the existing browser inventory. |
| MCP | The agent can reconnect and list its browsers. |
| Saved state | An existing persistent browser opens with its saved profile. Check the site's current login separately. |
| Handoff | Watch, Take control, and Return to agent work on that browser. |
Chrome starts again on the next use. Ask the agent to inspect the page before it resumes an interrupted task. Check whether a form was already sent so the agent does not submit it twice.
Before going back to an older image
If the new release changed the database format, starting the older image against the new data may fail. Read the migration notes and restore a compatible backup if required. Keep the interrupted deployment's data until you understand the failure and have verified the recovery.
Docs behind this guide
Based on Tallylamp's documented behaviour. See the source for API details and release-specific settings.