Managing your apps

Update an app in place

Ship a new build to an app you've already published while keeping the same URL, status, and visibility. Upload a new zip or pull the latest from GitHub.

When you’ve changed your app and rebuilt it, you don’t delete and re-create it — you update it in place. The URL, the draft-or-published status, and the visibility all stay exactly as they were. Only the files change.

Update from a new zip

  1. Go to App To Page » Apps and click Manage on the app you want to update.
  2. On the app’s page, click Update.
  3. Drop your new .zip on the dropzone.

An app's Manage page with the Update button highlighted, alongside Unpublish, Settings, and Delete.

App To Page replaces the app’s files and re-runs its base-path processing on the new build. Everything else is preserved:

  • the same URL (your-site.com/your-app)
  • whether it’s a draft or published
  • its visibility (public or logged-in only)

You’ll get a confirmation when it’s done.

Update from GitHub

If the app is connected to a GitHub repository, you don’t upload anything. Open the app’s Manage page and pull the latest build from its GitHub section — App To Page fetches the newest Release asset (or branch files) and updates the app in place. See Deploy from a GitHub repository.

Tips

  • Test risky changes as a draft first. If a release is uncertain, click Unpublish to drop the app back to a private draft, update it, preview, and then publish again.
  • Caching is handled for you. Because hashed asset filenames change between builds, visitors pick up the new version automatically — the entry HTML is revalidated on each load, so no one has to hard-refresh.

Frequently asked questions

How do I update a WordPress app without changing its URL?

Open the app’s Manage page and click Update, then drop your new .zip. The URL, status, and visibility stay the same — only the files are replaced.

Will visitors need to clear their cache to see the update?

No. Asset filenames are content-hashed, so browsers fetch the new files automatically and the entry page is revalidated on each load.

Can I roll back to a previous version?

Not from within the plugin yet — version history and rollback are on the roadmap. For now, keep your previous build’s .zip (or a tagged GitHub Release) so you can re-upload it if you need to.

What if my update has a problem?

Unpublish the app to take it private while you sort it out, or update again with a fixed build. The app stays at the same URL throughout.