Put your project online
VibeCode.surf builds your project on your computer. It does not host it. You choose where it lives, and an agent prepares the project for that place. This guide explains the two cases and what to ask for.
First, know what you built
| Kind | What it is | Where it can live |
|---|---|---|
| A static page | Only files: HTML, CSS, JavaScript, images. Nothing runs on a server. | Any static host. |
| An app with a server | Code that runs all the time: an API, a database, sign-in, payments. | A server you rent (a VPS) or an app platform. |
Not sure? Ask the agent: “Is this a static site or does it need a server?”
Ask the agent to prepare it
Example requestPrepare this project for production and tell me how to deploy it.
The ready-made task Get it ready to deploy, in the Tasks menu under the message box, sends a fuller version of this request.
The agent runs the production build, fixes what breaks, lists the environment variables the app needs, and writes the steps into a document in your project. Tell it which host you use and it writes the files that host expects.
A static page
- Build the project. A site with no build step is ready as it is; otherwise the build makes one folder, usually called
distorbuild. - Upload that folder to a static host, or connect the host to your GitHub repository so it publishes on every push.
- Add your domain in the host's settings.
Examples of static hosts: Cloudflare Pages, Netlify, Vercel, GitHub Pages. Any of them works; so does a plain web server.
An app with a server
On a server you rent, the steps are roughly these. The commands depend on your project; ask the agent for the exact ones.
git clone https://github.com/you/your-app.git
cd your-app
npm ci && npm run build
cp .env.example .env # then fill in the real values
npm start- Clone the repository on the server and install what it needs.
- Create the environment file with the real keys and passwords.
- Start the app with a process manager, so it restarts after a crash or a reboot.
- Put a web server such as nginx in front of it, and add an HTTPS certificate.
- Point your domain at the server.
An app platform does most of this for you: you connect the repository and set the environment variables.
Two rules
- Never put API keys or passwords in the repository. They belong in the environment file on the server, and that file stays out of Git.
- Test the production build on your computer first. Ask the agent to run it and open it in the browser before you publish.
Ship an update
Push the change to GitHub (see that guide). On a static host that is connected to the repository, the site updates by itself. On your own server, pull, build and restart. An agent can write that as one script.
The steps on this page are general guidance. Hosts differ, and they change their screens often: follow your host's own documentation for the details.