DocsWorking with Rahti
Deploying with Dilnaka Cloud
Deploy a Rahti application as a Docker service from GitHub or directly from your terminal, with managed domains, TLS, logs and rollback workflows in one project.
Dilnaka Cloud runs applications as isolated Docker services. Rahti is one of the frameworks it
recognises for Auto Dockerfile deployment, and a Rahti project with its own Dockerfile is deployed from that file instead. Your Dockerfile always takes precedence.
The standard Rahti Dockerfile is already production-shaped: it builds a release
binary, carries the compiled public/ assets into the runtime image, binds on 0.0.0.0, and accepts the platform's PORT environment variable. There is no separate frontend artifact to deploy.
Deploy from GitHub
- Sign in to Dilnaka Cloud with GitHub and create a project for the application.
- Connect the repository that contains the Rahti project. Keep its
Dockerfileat the repository root, or choose the Rahti project's root directory when it lives in a monorepo. - Choose the branch to deploy. Dilnaka builds the container and publishes the application through its managed proxy.
- Push to the tracked branch to build and deploy again. You can also deploy manually, inspect build and runtime logs, and roll back to a prior commit.
Configure the running service
Add application secrets and connection strings as service environment variables in
Dilnaka Cloud. Values supplied by the platform take precedence over values in the
local .env file, which should remain uncommitted. Rahti reads PORT and HOST at startup; the supplied Dockerfile defaults to a container-safe HOST=0.0.0.0.
For an authenticated application, configure AUTH_SECRET and AUTH_COOKIE_NAME. A database-enabled application can start without DATABASE_URL; set it when the deployment should serve database-dependent features. The generated application leaves those features disconnected until then, rather than failing the container at startup. Dilnaka can provision managed PostgreSQL, MySQL, MariaDB, Redis and MongoDB services inside the same project.
Deploy from the command line
The Dilnaka CLI deploys the source directory you link. It needs Node.js 18.17 or newer. Sign-in opens a browser approval flow; no password or token is pasted into the terminal.
npm install -g dilnaka-cli
dilnaka login
dilnaka link --create
dilnaka updilnaka link --create creates a project named after the current directory. To deploy into an existing
project instead, run dilnaka link <project>; use --service <name-or-id> to bind the directory to one service. After linking, dilnaka up packages the source using Git ignore rules and leaves local .env files out of the deploy. dilnaka up --new creates another application in the linked project.
Domains, health and growth
Each app receives a managed subdomain. Add a custom domain by creating the DNS record Dilnaka shows; it issues TLS automatically when the domain first receives a request. Use the service's build logs, runtime output and request logs to diagnose a release, and watch CPU and memory before adjusting capacity.
Start on shared capacity for smaller services, then move an application and its databases to a dedicated instance when it needs reserved resources or stronger isolation.
For current platform setup, deployment controls, databases and CLI reference, see the Dilnaka Cloud documentation. Rahti's own Configuration guide covers every environment variable the application reads.
For durable uploads, use Dilnaka Storage with its Rust SDK. The external storage guide covers the application-side configuration and trust boundary.