Docs

Deploying

git push over SSH. That's the entire deploy story.

The command

git remote add rentfree git@rentfree.site:/var/lib/rentfree/repos/yourname.git
git push rentfree main

The exact path is printed when your Site is created — use that one verbatim.

Your Admin Key authenticates the push, and the key alone determines which Site it targets. There's no separate login step and nothing else to configure.

What a push does

A push atomically replaces your Site's entire content with whatever was in the pushed tree — only static files (HTML/CSS/JS/WASM) are served; nothing on the server executes. The previous content is gone the instant the push succeeds, not merged with it. The server keeps the full git history of what you've pushed, so git log and git revert work against the server-side repo too, not just your own clone.

Only static files

Whatever you push is served byte-for-byte. There's no build step, no server-side rendering, and no way to run code on the box — if your site needs a build, run it locally and push the output.

Fetching what's live

git clone and git fetch work the same way, scoped to your own Site. They return the latest tree, which is enough to check what's live or to seed a second machine.

One key, one Site

Your Admin Key can only push to, fetch from, or delete the Site it's bound to — never another one, even if you know its name. Want a second Site? Generate a second keypair and ask for a second invite (or, if you're the operator, create it directly).