Skip to content
LarVPS Docs

Create a Site

Before you click create

Section titled “Before you click create”

Make sure the server is already connected in Servers.

Then open Sites and click Add Site.

What the Add Site sidebar asks for

Section titled “What the Add Site sidebar asks for”

Simple Setup

Section titled “Simple Setup”

This is the fastest path for most users:

  • Server: where the site will live
  • Domain: the public hostname
  • Runtime: WordPress, Laravel, PHP App, Static HTML, Next.js, Node.js App, Python App, Docker, and other supported stacks
  • DNS mode: manual or auto via Cloudflare

Advanced

Section titled “Advanced”

Use this when your runtime needs more control:

  • PHP version
  • database choice
  • runtime preset
  • public directory
  • internal port
  • start command override
Section titled “Recommended flow”

  1. Choose the target server.

  2. Enter the domain exactly as the site should open in a browser. LarVPS validates obvious mistakes early and checks DNS readiness in the form.

  3. Pick the runtime that matches the app you are actually deploying.

  4. Choose how DNS should be handled.

    • Manual DNS means you will create or edit the records yourself.
    • Auto via Cloudflare means LarVPS can help create or update the record only inside zones the team has granted.

  5. Review the DNS message in the form before creating the site. LarVPS will tell you whether:

    • the domain is ready
    • the domain is not live yet
    • the record points somewhere else
    • Cloudflare can create the record automatically
    • Cloudflare needs your confirmation before overwriting an existing record

  6. Click Create Site.

What LarVPS creates for you

Section titled “What LarVPS creates for you”

When the site is provisioned, LarVPS prepares the app environment on the server:

  • isolated site user
  • web root and home directory
  • Nginx vhost
  • runtime services needed for the chosen stack
  • optional database wiring, depending on the runtime

What to expect after creation

Section titled “What to expect after creation”

The site row becomes the main control point.

  • Deploying means LarVPS is still finishing setup
  • Active means the app is live on the server
  • SSL may still wait on DNS even when the site itself is already ready

Operator responsibility

Section titled “Operator responsibility”

LarVPS assists with setup, but you still decide:

  • whether the domain should point to this server
  • whether an existing DNS record is safe to replace
  • whether the selected runtime matches the real application