Deploy to your own server (Dokploy)
Connect a self-hosted Dokploy server, deploy a project, and read back its status and logs.
What Dokploy is for
Dokploy is an open-source platform-as-a-service you run on a server you control. It builds and runs your app from Git or a Docker image and manages its domains and HTTPS.
Lyre connects to your Dokploy instance as an external target. Lyre does not host, bundle or operate Dokploy; you own the server, its domains, its TLS and its data. Deploying through Lyre means Lyre tells your server what to run — it is different from a local preview and from publishing to an app store.
Connect a target
- Have a running Dokploy instance and an API key for it. The first key is created in Dokploy’s own profile page; Lyre can also help create one during onboarding on a fresh instance.
- On desktop, open the workspace menu and choose Deploy.
- Enter the server address and the API token, then connect. The token is stored on the host in an owner-only file and is never returned to the client.
Connecting a target requires the deploy.manage permission. An app-only
viewer cannot reach it.
Deploy a project
Create the application in Dokploy’s own dashboard, then use its application id in Lyre.
- Enter the application id, and optionally a git ref to build.
- Press Deploy. Lyre asks your server to build and release the app.
- Read back the resulting URL, status and bounded logs.
Deploy is offered only for a confirmed target with no pending connection change. If you edit the address or type a new token, the sheet asks you to Reconnect first instead of quietly using the older saved target. A refused connection leaves a previously saved target intact.
Reading the result
| What you see | What it means |
|---|---|
| Failed | The server reached the target and the deploy failed. Read the logs. |
| Uncertain | The response was lost. Check the target before retrying — do not assume success or failure. |
| Unreachable or misconfigured | The host could not reach the server, or the target is wrong. Check the address, token and server state. |
| Revoked credential or removed target | The stored token no longer works or the target was deleted. Reconnect with a current key. |
A returned URL is not proof the site is reachable for everyone. Open it yourself before treating the deploy as live.
Who can deploy
Deploying can expose a project publicly, so it has its own grant rather than riding along with preview or agent access.
- Developer (
deploy.manage) - Connect to an already-connected target and run ordinary deploy and operation actions.
- Host owner (
deploy.admin) - Manage the target connection, credentials and guided installation. Paired developer devices never receive it.
- App-only viewer
- Denied at the host boundary. Viewing a shared app is not permission to deploy.
What is available now
The current connector is deliberately narrow: connect a target, deploy an application that already exists in Dokploy, and read back its URL, status and bounded logs. A live Dokploy server is still being qualified against supported versions and failure modes, so source and fixtures alone are not proof of a deployment.
The wider goal — managing projects, databases, domains, certificates and the rest of Dokploy natively inside Lyre’s Deploy UI, without opening the Dokploy dashboard — is in progress and not yet generally available. Where a control you expect is missing, use Dokploy’s own dashboard for now and follow release status.