Hosting with 20% off when you buy through the link

Publish the site

Put the site online on a real server with one request: what to prepare, what the AI asks the first time, what it does, and what to check once it's live.

Publishing puts the site you built on your computer onto a hosting server, content included, so it answers at its real address. With the Velk skill it's one request: the AI asks what it doesn't know the first time, inspects the server, sends everything and checks the result.

This page covers the first deploy. After it, the live site is the real one: later changes go out as theme publishes (Publish changes) and new Velk versions as updates (Update Velk).

Before you start

  1. SSH access

    SSH is the secure connection from your computer to the server, opened with a key instead of a password. Turn it on in the hosting panel, under SSH Access (Hostinger uses port 65002). Mid-range shared plans usually have it, basic ones often don't, a VPS (a virtual server of your own) always does.

  2. A database and its four details

    Create the database and its user in the hosting panel: Velk can't create them there. Note the host (usually localhost), name, user and password exactly as shown, prefix included, as in u12345678_lumen.

  3. The domain

    Point the domain at the server, or at least start: DNS, the internet's address book, takes minutes to hours to spread a change.

  4. The canonical address

    Choose one official address, with or without www, always with https. It becomes APP_URL in the server's .env (its settings file), and the sitemap, robots.txt and canonical tags are built from it. Launch on a temporary address and they keep pointing at it until someone notices.

Ask the AI

Create an SSH key for me and show me the public part, so I can paste it in the hosting panel.

The public part goes to the server; the private one never leaves your computer.

Ask the AI

Publish this site for the first time on my Hostinger hosting. It's the Lumen Clinic site, and the official address is https://www.lumenclinic.example, with www. SSH is on and I've created the database in the panel.

The first time, the AI asks for what it still doesn't know. It saves the answers, so later requests ask nothing.

What the AI asks the first time

QuestionWhat to answer
SSHAddress, port and user, from the hosting panel. The AI connects with the key, never with a password.
Folder on the serverThe full path where the site will live, such as /home/u123456789/domains/lumenclinic.example/public_html on Hostinger (the panel's document root). The AI never guesses it from the address.
AddressThe canonical address with https (the AI warns you about http), plus the subfolder if the site isn't at the domain's root.
Server databaseName, user and password exactly as the panel created them; the host only if it isn't localhost.
Local databaseNothing: the AI reads it from your project's .env.

What the AI does

It saves the answers in .deploy/ssh.json, readable only by you and kept out of Git, and tests them. Then it:

  • Looks at the server first, and stops if the folder already holds Velk.
  • Refuses to ship problems: an edited engine, or the original pages of a converted HTML site left in the theme.
  • Sends the files: engine, theme, storage/uploads/ and .htaccess, the web server's rules file. Never your local .env, .git or deploy settings.
  • Writes the server's .env from your answers, with APP_DEBUG=false, locked so other accounts on the server can't read it. Your local credentials never go up.
  • Copies your local database into the server's and runs migrate, the engine's database updates: pages, posts, media and admin users arrive as they were.
  • Finishes: writes robots.txt with the sitemap's real address and checks that the home page answers.
What the AI runs
# the skill's scripts, in the scripts/ folder of the Velk plugin # 1. look first $ scripts/preflight.sh --project . --local-db ✓ Preflight passed # 2. the first deploy $ scripts/deploy/init.sh --project . ✓ Target empty — proceeding ✓ Files synced ✓ DB imported ✓ Migrations OK ✓ HTTP 200 OK ✓ Init deploy complete.
You don't type any of this: the AI runs it and reports the live address and the admin's.

Check the live site

  1. The home page

    Opens, with the same content you had locally.

  2. An inner page

    Opens too, which tests the address rules in .htaccess. If the home works and inner pages give 404, that file is the first suspect.

  3. The images

    Show up, which tests that storage/uploads/ arrived.

  4. The admin

    Your address plus /admin accepts the user you had locally.

  5. A form

    Sends, and the submission shows in the admin.

  6. robots.txt

    Opens at /robots.txt and points to the sitemap at the right address. Since v3.8.1 it doesn't list the admin, which tells search engines by itself not to index it.

Ask the AI

Check the live site: open the home, the About page and one blog post, see whether the images load, and tell me what /robots.txt says.

HTTPS and production settings

Certificate. Turn it on in the hosting panel (Hostinger issues a free one). The address you gave the AI already starts with https, so the links built from it come out right.

Debug mode off. The first deploy writes APP_DEBUG=false on the server. Keep it: switched on, an error shows file paths, database queries and versions to any visitor.

E-mail. The e-mail sending settings (SMTP) in the server's .env start empty. If the forms send e-mail, ask the AI to fill them in with your provider's details; until then, sending depends on the server's own mail function.

A site in a subfolder

A site can live under a path, such as https://auroraschool.example/enrollment. Give the AI the subfolder when it asks: it goes into APP_BASE_PATH, while APP_URL keeps only https and the domain. The folder on the server is a separate answer; the AI never derives one from the other.

Links work there because a Velk theme builds every address through the engine's helpers, and since v3.9.0 the canonical and language tags no longer repeat the folder. One catch: search engines read robots.txt only at the domain's root, so declare the sitemap there or send it through Google Search Console.

Hosts without SSH

Without SSH the AI can't deploy for you, but Velk still runs: the files go up by FTP (plain file transfer) or the hosting's file manager, the server's .env gets the database details and a first admin user, and the first visit installs the site. After an engine update, the first visit applies the database changes by itself (AUTO_MIGRATE, on by default).

The content in your local database doesn't travel with the files, and none of the SSH flows on these pages work there. If you can, choose a plan with SSH.

Working straight on the live site

You can skip the local copy and ask for changes on the live site. The AI still never edits files on the server: it downloads a fresh copy of the live theme, changes it and publishes it with every check (see Client sites). The cost: you see the result only once it's live, and the checks catch a broken page, not an ugly one. Local to build, live for small adjustments, a backup before anything big.

Common questions

What if I ask to deploy again later?

The AI finds Velk on the server and asks what changed: the theme (a versioned publish) or the engine (an update). It never repeats the first deploy, and your local content never goes up again: the live database, storage/uploads/ and the server's .env are never overwritten.

Which hosts work?

Any with PHP 8.2 or newer, MySQL or MariaDB, and SSH with a key: Hostinger, cPanel hosts (Locaweb, HostGator, KingHost), DreamHost, a VPS or a cloud server; only the folder path changes. If PHP sits at an unusual path, the AI finds it and, with your OK, saves it. A server running nginx instead of Apache ignores .htaccess and needs the rules in Velk's nginx.conf.example.