Press runs headlessly. It listens on loopback by default; remote clients should connect through a trusted HTTPS reverse proxy. The bootstrap management token must be at least 32 characters and should be stored in a protected file.
Linux Docker
The Press image runs as a non-root user. Mount persistent data at /var/lib/inksmith-press so the SQLite database and render artifacts survive container replacement. The root filesystem can be read-only when the data mount is writable and /tmp is a writable temporary filesystem.
A Compose deployment places Press behind an HTTPS gateway. Press stays on 127.0.0.1:8080 inside the shared network namespace; the gateway publishes HTTPS on port 443. Supply a certificate trusted by the Desktop clients and a protected management-token file outside the image.
After starting the stack, check the container health and request https://your-hostname/ready. Back up the persistent volume before an upgrade. Do not bake customer templates, credentials, database files, or licensed fonts into the image.
Windows Service
The Windows Service edition registers InkSmithPress, uses a machine-scoped data directory under C:\ProgramData\Logicos Software\InkSmith Press, and reports startup and failures in the Application Event Log. Its command line contains token-file and data-directory paths, not the secret token.
From an elevated PowerShell session, use the service installer included with the Press distribution. Provide an absolute path to the signed inksmith-press.exe and to a protected bootstrap-token file. The default service identity is LocalService; a dedicated account can be used when its required filesystem permissions are configured.
Check Get-Service InkSmithPress, the Event Log, and http://127.0.0.1:8080/ready. A reverse proxy with a trusted certificate is required for remote Desktop connections.
Operational limits
Press rejects a direct non-loopback HTTP listener. Certificate enrollment and Desktop trust overrides are still being developed. The Docker and live Windows Service paths need smoke testing in the target environment before a production rollout. Keep a backup of the database and artifact store before upgrading either deployment.
Continue with the Press API for authentication, scoped clients, and render jobs, or Press Control for the Desktop administration workflow.