Upgrading
Upvora upgrades are a normal image bump: pull the new image and recreate the container. Database migrations run automatically on boot.
From the admin panel
If you deployed with the updater sidecar, open Admin → System, check for the latest release, and click Update now. The app writes a trigger file the sidecar picks up; it pulls the new image and recreates the app container. The page polls through the restart and reloads when the new version is live.
From the command line
docker compose pull
docker compose up -d
Upgrading to 0.39.0.8.2
Moves the base to Fider v0.39.0: API keys of blocked users are rejected, OAuth redirects with several leading slashes are refused, and a new Disable Sign-ups setting is available under Admin, Privacy (off by default). One migration runs on boot (202611031200; Fider numbers it 202610131200, Upvora runs it after its own so every site gets it). It also includes 0.38.2.8.1's fixes for the MCP listen stream and slow Vora replies on local models. If the host is short on disk, run docker image prune -af first.
Upgrading to 0.38.2.8.0
Adds Require Vora for new ideas (Admin → AI) and PDF, text and Markdown attachments on ideas (Admin → General), both off by default; see the Admin guide. One migration runs on boot. Nothing changes until you turn them on.
Upgrading to 0.38.2.7.1
Adds MCP-only public addresses for boards on an internal network (MCP_ORIGINS and MCP_PORT, see MCP, Internal boards) and makes /mcp say clearly when MCP is off. One migration runs on boot. Nothing changes unless you set MCP_ORIGINS.
Upgrading to 0.38.2.7.0
This release moves the base to Fider v0.38.2 and adds member private ideas, the complete REST API and MCP. Five migrations run on boot (new settings columns and the OAuth tables). MCP stays off until an administrator turns it on, and member private ideas stay off until enabled under Admin, Privacy.
Migrating from Fider
Upvora keeps Fider's data model, so you can migrate in place: keep your existing Postgres database and environment values, swap your app image to ghcr.io/hodyhq/upvora, and bring it up. Upvora's migrations run on first boot and upgrade your schema. Your existing ideas, votes, comments and users are preserved.
Always take a database backup before a major upgrade or a migration from Fider.