Recipes

Self-contained guides for deploying a specific stack — each one takes you from a repo to a live URL.

Every recipe is complete on its own: the config, the one rule that matters (listen on 0.0.0.0:$PORT), and the deploy steps. New to Dockhold? Start with the Quickstart.

• Deploy a Vite + React app — A Vite single-page app, built and served on a live URL.
• Deploy a Next.js app — Full-stack Next.js — pages, API routes, and server rendering.
• Deploy a static site — Plain HTML, CSS, and JS — the 60-second “it works”.
• Deploy a Node / Express API — A JSON API on Express, listening on $PORT.
• Deploy a Python / FastAPI app — A FastAPI service with a minimal, reproducible Dockerfile.
• Deploy a Lovable export — Take the Vite + React app Lovable built and host it yourself.
• Deploy a Bolt.new export — Move a Bolt.new project out of the sandbox onto a real URL.
• Connect a Postgres database — Add a managed database; Dockhold injects DATABASE_URL. pgvector built in.
• Deploy a vector database (pgvector) — Store embeddings and run similarity search — pgvector is built into the managed database.
• Deploy a full-stack app (React + API + Postgres) — A React frontend and a separate Express + Postgres API — the production shape, split across your compute pool.
• Deploy connected services — Deploy several services that call each other in one step — Dockhold injects each service’s URL into the others automatically.
• Deploy an MCP server — A remote MCP server (Streamable HTTP) on a live URL — any client connects over the web.
• Deploy from your AI tool (MCP) — Connect Claude, Cursor, or any MCP client to Dockhold and let it deploy and manage your apps.
• Deploy n8n — Self-host your own n8n automation instance, backed by a managed database.
• Deploy a Telegram bot — An always-on Telegram bot — get a token, set it, and it’s live. Discord works the same way.