hostit.mifcom.dev

A project + a tarball + a name → a live URL. Designed so an AI agent can deploy on the user's behalf with no human in the loop.

For humans (one-line deploy)

cd path/to/project
tar czf - . | curl -fsS -X POST \
  "https://hostit.mifcom.dev/api/v1/deploy?name=my-app" \
  -H 'Content-Type: application/gzip' \
  --data-binary @-

The response gives you a url and a password. Save the password — it's the only thing that lets you re-deploy under the same name.

Updating later:

tar czf - . | curl -fsS -X POST \
  "https://hostit.mifcom.dev/api/v1/deploy?name=my-app" \
  -H 'Content-Type: application/gzip' \
  -H 'Authorization: Bearer your-saved-password' \
  --data-binary @-

For AI agents

Read /llms.txt (Markdown) or /.well-known/hostit.json (machine-readable). The recipe:

1. Ask the user for a project name.
2. GET /api/v1/projects/<name> — if it exists, ask the user for the password they saved earlier.
3. tar czf - . the project; POST /api/v1/deploy as multipart or raw application/gzip.
4. Show the user the returned url and remind them to save password if it's a first deploy.

Project types

• Static (default): plain HTML/CSS/JS, Vite/Next/Hugo build output, etc. Hostit wraps the files in a tiny nginx:alpine image and hands it to Coolify.
• Dockerfile: include a Dockerfile at the root. Hostit builds it and hands the image to Coolify, which runs the container behind its Traefik proxy. The container must listen on $PORT (default 3000) on 0.0.0.0.

Either way, your project becomes a real Coolify-managed app you can manage in the Coolify UI alongside everything else on the host.

Constraints

• Names: 3–40 lowercase alphanumerics + hyphens, e.g. my-cool-app.
• Upload limit: 100 MB compressed / 500 MB extracted / 20,000 entries.
• No symlinks or absolute paths in tarballs (rejected with 422).

v1   service status: live