Deploy to hosting

Ship a project that already exists — on disk or in a Git repository — to a Hostinger website. Building a new site from a prompt (design, store, blog) is the hostinger-headless skill; this one takes code as it is.

Calling the operations

• Read the inputSchema that search returns before the first call of each operation. If a name below is rejected as unknown, search for what the step does (e.g. "deploy static").
• Batch reads with multi-execute; values pass between steps as $steps.<i>.<path>. Batches chain operations from one server only — the Hostinger Connector runs hosting, wordpress and agency-hosting as separate servers.
• Every deploy overwrites the website's current contents. Confirm the target domain with the user before the first deploy to a site that already has content.

0. If a shell and the Hostinger CLI are available

hostinger up does steps 1 to 3 in one call and is the shortest path when you can run commands and the hostinger CLI is installed (brew install hostinger/tap/hostinger), signed in and has hostinger up: it finds or creates the website, detects the type, packs the directory (honouring .gitignore; skipping node_modules, .git, .env files, credentials and private keys, and listing symlinks it does not follow), uploads, deploys or builds, waits for the build and links the directory in .hostinger/site.json, the same file this skill uses. Nothing is asked without a terminal.