h_HIRAX.

HIRAX / FIELD GUIDE

Your app works. Now put it on the internet.

A clear route from an AI-built project on localhost to a server, a domain and a working HTTPS application.

STEP 01Find out what you actually built

Look for package.json, requirements.txt, a Dockerfile or a folder of plain HTML files. Ask your AI to explain the production start command and whether the app needs a database or persistent files. A static website may be simpler on a static host; a VPS becomes useful for an API, workers, databases or several projects.

EXAMPLE / ADAPT TO YOUR PROJECT
I have a working local project. Identify its runtime, build command, production start command, required environment variables, persistent data and external services. Do not include secret values. Explain whether I need a server.

STEP 02Separate code from the things that must stay private

Commit the source code and a lockfile to a private or public Git repository. Keep credentials, .env files, database files and uploads out of Git. An environment variable name is documentation; its actual password is a secret. If you already committed a secret, rotate it before deployment.

STEP 03Choose a server and a deployment recipe

A VPS is a Linux computer in a datacenter that you administer remotely. Select an Ubuntu LTS version supported by your tools, connect with SSH keys and install your runtime. For several services, Docker Compose makes their relationship explicit. A single Node process can also run under systemd.

STEP 04Make the app survive a closed laptop

Use a production build and a process supervisor or a container restart policy. Put a reverse proxy in front of the app. A development server and an open SSH terminal are not a production runtime. Keep the database on a private interface or container network.

STEP 05Give it a name, then verify the whole path

Point a domain A record at the server IPv4. Add AAAA only if IPv6 actually works. Configure Caddy or another reverse proxy for the exact hostname. Test HTTPS from a different connection, log in, upload a file if relevant, restart the app and verify that the data remains.

A public URL is the start of operations: schedule updates, monitor the app and test a backup restore.

COPY → YOUR AI

Take the next step to your AI.

A safe starting prompt for this guide. No secrets. Works with ChatGPT, Claude and other assistants.

Sources and technical documentation

Docker documentationCaddy automatic HTTPS

This recipe is a pattern for the stated prerequisites. Verify project compatibility and your actual server configuration before applying it to a live service.

Ready for your own server?

Find a starting point for your project and compare real configurations at WVG.

Find my next step