Artboard

Sending Deployments

Review connected clients, start or schedule a deployment, and watch its progress live before it runs on the destination server.

When you're ready to run a deployment, the Review & Deploy screen is where you take a final look before sending it to the destination server. It has two tabs: Deployment and Connected Clients.

Deployment Tab

The Deployment tab shows a summary of what will happen when you send this deployment, including the files and operations involved. This is your last chance to review everything before it runs.

Connected Clients Tab

Deploying closes the target files, so it's helpful to know who is using them before you send the deployment. The Connected Clients tab shows every user currently connected to the deployment's target files, and it refreshes automatically so the list stays up to date while you're reviewing.

For each connected client, you can see:

  • User name
  • The files they have open
  • Host/IP
  • Sign-in time
  • Their FileMaker client app and version
  • Operating system
  • Privilege set
  • Status

You can select one or more clients to send them a message, or disconnect them entirely. Disconnecting lets you include a custom message and set a grace period (90 seconds by default) before the client is actually disconnected, giving users time to finish what they're doing.

Start Now or Schedule for Later

Once you're ready, choose Start Now to run the deployment immediately, or Schedule for Later to run it at a specific date and time. The date/time picker defaults to about an hour ahead. Scheduled times are set in the destination server's timezone.

Both deployments and builds can be scheduled. Scheduling a build requires the destination server to be running OttoFMS 4.10.0 or later.

OttoDeploy doesn't list your scheduled runs anywhere in the app. To view or cancel a scheduled deployment or build, go to the OttoFMS console on the destination server.

Watching a Deployment

Once a deployment starts, you can watch its progress live right in the app. The logs are broken into sections — one per sub-deployment, shown in order — and each section has its own running timer and progress bar. As new log lines come in, the view auto-scrolls to keep them visible as long as you're already scrolled to the bottom.

If a deployment fails to start, the error is shown here as well.

When the deployment finishes, you'll see a status for each sub-deployment along with buttons to open the OttoFMS Dashboard or return to the deployment.

Was this page helpful?

On this page