ioLoop Docs

Appearance

Publish ​

Publish releases the saved development version of a Project as an application that its intended users can access.

The Publish area contains two actions:

ActionPurpose
Publish ProjectReplace the current published version with the Project's latest saved and publishable development state.
Launch ProjectOpen the published application at its configured address.

Publishing and launching are separate actions. Publishing performs the release. Launching only opens the result so it can be verified.

The Release Workflow ​

A typical release follows this sequence:

  1. Make and save changes in the Project Editor.
  2. Preview affected Pages and Forms.
  3. Test Database operations, Cloud Flow, Connections, AI Agents, and access rules as applicable.
  4. Review the Starting Page, Project URL, and custom domain configuration.
  5. Select Publish → Publish Project and complete the publish.
  6. Review the publish result and its access summary.
  7. Select Publish → Launch Project.
  8. Verify the released application with representative users and production conditions.

Each step has a different purpose:

  • Save records development changes.
  • Preview runs saved frontend changes in the development context.
  • Publish Project releases applicable saved changes.
  • Launch Project opens the published application for verification.

Preview does not publish, and Launch Project does not include changes that have not been successfully published.

Development and Published Versions ​

Development changes do not automatically update the published application. You can continue editing and testing a Project while its existing published version remains available.

When you start a publish, the published Project becomes temporarily inaccessible while ioLoop prepares and activates the new version. Plan the release for an appropriate time when an interruption would affect active users, Web Hook callers, or other dependent systems.

If publishing does not complete successfully, the Project may remain unavailable until the problem is corrected and a successful publish is completed.

What Publishing Can Affect ​

A publish can update several connected parts of the application, including:

  • Active Pages and Forms, their settings, Page Flow, and access configuration.
  • Included JavaScript and CSS Code assets.
  • Project-wide presentation and runtime settings.
  • Database table definitions, named queries, and access configuration.
  • Cloud Flow modules and their published entry points.
  • Connections and their access configuration.
  • AI Agents and their published dependencies.
  • The Project URL and supported custom-domain configuration.

The exact effect depends on which Project resources changed. Publishing should therefore be treated as an application release, not only as a visual Page update.

Production records follow a separate rule. Publishing does not merge development records into populated production tables. When a corresponding production table is empty, its development records are copied into that empty table during publishing. For the full data behavior, see Development and Production Data.

In This Section ​

GuideWhat You Will Learn
Publish ProjectPrepare a release, publish the Project, review the result, and respond to failures.
Launch ProjectOpen and verify the published application through its configured address.