allyhub site deploy
Build a website here and upload it to AllyHub as a new version of its site, sending only the files AllyHub lacks; private until --live
allyhub site deploy [item] [options]Arguments
Section titled “Arguments”| Argument | Type | What it is |
|---|---|---|
<item> |
string | The website: its id in allyhub.yaml or its file, when several are in the project. Left out, the project’s one website |
Options
Section titled “Options”| Option | Type | Default | What it does |
|---|---|---|---|
--slug |
string | The site’s address, <slug>.allyhub.site, the first time; default from the website’s folder | |
--note |
string | What this version changes | |
--live |
boolean | Make this version what the site’s address serves | |
--built |
boolean | Upload the output folder as it is, with no build | |
--new |
boolean | Make a site of this team’s for the folder, though website.json names another team’s (theirs stays as it is) |
Global options
Section titled “Global options”--dir <value>: the project’s folder; default the one around where it is run. --json: print the result as JSON.
Output
Section titled “Output”With --json, the command prints an object with these fields:
| Field | Type | What it is |
|---|---|---|
site |
object | |
version |
string | |
live |
boolean | |
confirm |
string | |
files |
number | |
sent |
number |
Examples
Section titled “Examples”allyhub site deployallyhub site deploy website --slug acme --liveallyhub site deploy --note "New pricing" --liveExit codes
Section titled “Exit codes”0 when it succeeds; the others are listed in Exit codes.
In the work
Section titled “In the work”websites: Making a website: any web project, with its website JSON listed in allyhub.yaml
check → render → frames web → frames compare → site deploy → site status → site live