When you can publish
Publish, at the top right of the app, is available when:
- the app’s screens have been connected to a backend with Apply. A version that still runs on sample data cannot be published, and Atomic says “Apply the screens first”;
- the latest version is Verified;
- no build is running; and
- you are the app’s owner or an admin.
Before publishing something people will rely on, work through before your app goes live.
Publish
Select Publish. Atomic builds a release of the latest verified version, starts it on the app’s own runtime and moves the app’s address over to it. The button shows Publishing until it finishes; you can close the page meanwhile.
When it is done, the app’s Dashboard shows its address under Published app, and a link in the app’s top bar opens the published app in a new tab. Open it and check it there, signed in as a real app user rather than a sample account.
Publishing changes
Later changes stay in the preview until you publish again; the button then reads Republish. Each publication is kept in the app’s deployment history, so you can serve an earlier one again if something goes wrong.
If a change alters how the app stores data, publishing applies that change to the published app’s data. Rolling back serves earlier code but does not undo it, so test such changes carefully in the preview first.
What publishing does not do
- It does not copy anything you created in the preview. The published app’s data belongs to its users.
- It does not create the sample accounts. Invite your first admin after publishing.
- It does not change who can edit the app.
After publishing
- Invite app users and set the access mode.
- Connect your own domain.
- Keep refining in the preview, using logs to track down problems before you republish.