Hosted edition

Config Deploy

Config Deploy lets you push ORDS configuration changes to your instances from the ORDSwatch dashboard, instead of editing files by hand on each server.

What it covers

ORDSwatch understands the standard ORDS configuration files:

File	Purpose
`settings.xml`	Global ORDS settings
`pool.xml`	Per-database-pool connection settings
`jetty-http.xml`	Jetty HTTP listener settings

The dashboard gives you a form-based editor for known settings, plus a "Custom Entries" section for anything not yet recognized, so you're never blocked by an unfamiliar key.

Templates

A deploy template is a saved, reusable set of configuration values. Instead of editing one instance at a time, create a template once (e.g. "standard production pool settings") and push it to any instance or group of instances that should share that configuration.

Templates support secrets (database passwords, wallet credentials) which are stored encrypted and never displayed back in plaintext in the UI once saved.

Pushing a deploy

Go to Config Deploy → Templates, pick or create a template
Choose the target instance(s)
Review the diff preview — ORDSwatch shows exactly what will change on the target file(s) before anything is applied
Confirm. The change is sent to the owning agent, which writes the file on the ORDS server and reports back success or failure

Deploy history

Every deploy is recorded — who triggered it, what template, which instance, and whether it succeeded — under Config Deploy → History. Use this to audit changes or see what was last pushed to an instance.

Who can deploy config

Operators and admins can create templates and push deploys. Viewers can see templates and history but can't trigger a deploy. See Users and Roles.