Skip to content
ownpost.Get the kit
Documentation/Keep it running
KEEP IT RUNNING

Keep your workspace in good shape.

A considered update process, and backups that cover more than your drafts.

5 min read

Before you update

  1. Read the release notes and compare changes with your own customizations.
  2. Back up your database, media bucket, and deployment configuration.
  3. Keep a separate secure record of secrets and recovery codes.
  4. Preserve your resource IDs, environment settings, and application origin.

The older JSON metadata export and CSV export cannot be restored. Use Download content backup for a restorable package with stored media, and keep separate backups of deployment configuration and secrets. CSV exports use the selected account; content backups include all account profiles.

Back up content and restore into an empty workspace

  1. Open Settings → Account & data → Backup & restore and choose Download content backup. The version 1 package includes all account profiles, posts, thread parts, saved sources, stored images and videos, results, preferences, routines, replies, and inactive publication history.
  2. Keep the downloaded file privately outside the app. Login credentials, assistant keys, X connections, pending notifications, agent leases and browser-only data are excluded.
  3. To restore, sign in to an initialized empty destination workspace. In Backup & restore, choose the version 1 file and Preview restore. Review the counts and restore behavior before confirming; existing destination content blocks restore.
  4. Restore replaces preferences while keeping destination credentials. Routines are paused, notifications are muted, and X publishing, collection and replies are disabled. Older version 1 packages without profiles restore into Main account. Verify the restored content and media, reconnect integrations where needed, and deliberately enable the work you want to resume.

Content backups support up to 25 MB and 2,000 database records, including related rows such as thread parts and Metric Snapshots. Larger workspaces need an administrator-managed database and media backup. After an interrupted restore, retry the exact same file; a completed import is recognized without duplicating content.

Test the new version locally

Use the checked-in release migrations. You do not need to generate new migrations unless you are changing the schema yourself. Test with a separate development database and storage bucket. For Node hosts use pnpm dev:node; for Cloudflare use pnpm run preview. Check login, MCP and optional integrations.

Terminal
pnpm install
pnpm test
pnpm typecheck
# Node hosts:
pnpm build:node
# Cloudflare:
# pnpm run db:migrate:local
# pnpm run preview

Update production

Back up first, review migration SQL and confirm the intended database. The helper's --execute flow applies migrations before deployment on every target. The direct deploy:cloudflare command requires the separate D1 migration step shown above. Preserve existing private configuration and production environment values.

After deployment, confirm you can sign in, read an existing draft, and use your MCP connection. Check that scheduled jobs and media still work.

Terminal
# Node: choose the target you already use
pnpm db:migrate:node --status
pnpm run deploy --target vercel --execute
# Cloudflare alternative:
# pnpm exec wrangler d1 migrations list DB --remote
# pnpm run db:migrate:remote
# pnpm run deploy:cloudflare
Your workspace should feel like yours. Start small, then make it fit.