project
Link a directory to a project and application, create and manage projects and their environments, and read their usage, traffic and deployment reports.
The project group ties a directory to a project and application, so later commands know what they act on without a name. It also creates and changes projects and their environments, and reads the reports for them: usage and cost, traffic, metrics and deployment statistics. Use link once per directory, then the other commands work from there.
| Command | What it does |
|---|---|
link | Resolve a project and application by name, and remember their ids for this directory |
unlink | Forget this directory’s link |
ls | List the projects you can see |
inspect | Show one project, the linked one when none is named |
apps | List a project’s applications and what each is doing |
create | Create a project |
update | Rename a project, or change its description or default server |
rm | Remove a project that has no applications |
environment:add | Add an environment to a project |
environment:rename | Change an environment’s label; its key stays the same |
environment:rm | Remove an environment that nothing is in |
usage | Show what the project used in a month, at this panel’s rates |
estimate | Show the project’s usage priced at another vendor’s rates |
analytics | Show the project’s traffic, from the proxy’s own log |
metrics | Show CPU, memory and restarts across the project over days |
stats | Show how the project’s deployments went |
Every command also takes --json, --quiet and --help. The shortcuts stechbd link and stechbd unlink run project link and project unlink.
stechbd project link
Resolves a project and, optionally, one of its applications by their names, then stores their ids for the current directory. Later commands that take an optional project or application use these ids. Run it in each project directory you work in.
stechbd project link <project> [<app>]| Option | Description |
|---|---|
<project> | The project slug. Required, unless --project is given. |
<app> | The application slug within the project. Optional. |
--project <project> | The project slug, as an alternative to the first positional argument. |
--app <app> | The application slug, as an alternative to the second positional argument. |
stechbd project link blog
stechbd project link blog webstechbd project unlink
Forgets the project and application link stored for the current directory. It does not change anything on the panel. Use it when a directory should no longer act on a project.
stechbd project unlinkstechbd project ls
Lists the projects that your login can see. Run it to find a slug to pass to link, or to check that a project exists.
stechbd project lsstechbd project inspect
Shows one project. When no project is named, it shows the project linked to the current directory.
stechbd project inspect [<project>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
stechbd project inspect
stechbd project inspect blogstechbd project apps
Lists the applications in a project and what each one is doing. Run it to see the application slugs to use with link.
stechbd project apps [<project>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
stechbd project apps blogstechbd project create
Creates a project with the name you give. Use --slug to set its slug, --server for its default server, and --account to pick the account it is created in.
stechbd project create <name> [--slug <slug>] [--server <id>] [--description <text>] [--account <account>]| Option | Description |
|---|---|
<name> | The display name of the project. Required. Quote it if it contains spaces. |
--slug <slug> | The URL slug to use for the project, instead of one derived from the name. |
--server <id> | The default server for the project. |
--description <text> | A description for the project. |
--account <account> | The account to create the project in, by slug or id. |
stechbd project create "Marketing site" --description "Public pages"stechbd project update
Changes a project’s name, description or default server. At least one of --name, --description or --server is required.
stechbd project update [<project>] [--name <name>] [--description <text>] [--server <id>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
--name <name> | The new display name. |
--description <text> | The new description. |
--server <id> | The new default server. |
stechbd project update blog --name "Company blog"stechbd project rm
Removes a project along with its environments. The command refuses when the project still has applications, and names how many, so remove those first. The command asks for confirmation first, unless --yes is passed.
stechbd project rm <project> [--yes]| Option | Description |
|---|---|
<project> | The project slug. Required. |
--yes | Skip the confirmation prompt. |
stechbd project rm old-blog --yesstechbd project environment:add
Adds an environment to a project. The key is the identifier other commands use, and --name is the label shown for it. To change the label later, use environment:rename.
stechbd project environment:add <key> --name <name> [--project <project>]| Option | Description |
|---|---|
<key> | The environment key, for example staging. Required. |
--name <name> | The label for the environment. Required. |
--project <project> | The project slug. Optional; defaults to the linked project. |
stechbd project environment:add staging --name Stagingstechbd project environment:rename
Changes the label of an environment. Its key stays the same, so anything that refers to the key keeps working.
stechbd project environment:rename <key> --name <name> [--project <project>]| Option | Description |
|---|---|
<key> | The environment key to relabel. Required. |
--name <name> | The new label. Required. |
--project <project> | The project slug. Optional; defaults to the linked project. |
stechbd project environment:rename staging --name QAstechbd project environment:rm
Removes an environment. The panel refuses while an application is still in it, so move those applications out first. The production environment cannot be removed. The command asks for confirmation first, unless --yes is passed.
stechbd project environment:rm <key> [--project <project>] [--yes]| Option | Description |
|---|---|
<key> | The environment key to remove. Required. |
--project <project> | The project slug. Optional; defaults to the linked project. |
--yes | Skip the confirmation prompt. |
stechbd project environment:rm staging --yesstechbd project usage
Shows what the project used in a calendar month, priced at this panel’s own rates. Pass --period to choose the month.
stechbd project usage [<project>] [--period <yyyy-mm>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
--period <yyyy-mm> | The calendar month to report, for example 2026-10. |
stechbd project usage blog --period 2026-10stechbd project estimate
Shows the same usage as usage, priced at another vendor’s rates. Use it to compare what the project would cost elsewhere.
stechbd project estimate [<project>] [--period <yyyy-mm>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
--period <yyyy-mm> | The calendar month to estimate, for example 2026-10. |
stechbd project estimate blog --period 2026-10stechbd project analytics
Shows the project’s traffic, taken from the proxy’s own log. Use --days for the window, --resolution for how finely it is split, and --compare to set it against an earlier period. The values are passed to the panel as typed.
stechbd project analytics [<project>] [--days <n>] [--resolution <resolution>] [--compare <compare>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
--days <n> | How many days to report. A whole number of at least 1. |
--resolution <resolution> | How finely to split the window, as the panel accepts it. |
--compare <compare> | The earlier period to compare against, as the panel accepts it. |
stechbd project analytics blog --days 30stechbd project metrics
Shows CPU, memory and restarts across the project over a number of days. Use it to check whether an application is under pressure or restarting.
stechbd project metrics [<project>] [--days <n>] [--resolution <resolution>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
--days <n> | How many days to report. A whole number of at least 1. |
--resolution <resolution> | How finely to split the window, as the panel accepts it. |
stechbd project metrics blog --days 7stechbd project stats
Shows how the project’s deployments went over a number of days. Use --compare to set the period against an earlier one.
stechbd project stats [<project>] [--days <n>] [--resolution <resolution>] [--compare <compare>]| Option | Description |
|---|---|
<project> | The project slug. Optional; defaults to the linked project. |
--days <n> | How many days to report. A whole number of at least 1. |
--resolution <resolution> | How finely to split the window, as the panel accepts it. |
--compare <compare> | The earlier period to compare against, as the panel accepts it. |
stechbd project stats blog --days 14 --json