dbrij

Deploy to Dbrij Hosting from your terminal. No GitHub connection, no webhook — the directory as it stands is what ships.

npm i -g dbrij

dbrij login      # confirm the code in your browser
dbrij link       # point this directory at a service
dbrij deploy     # ship it

How signing in works

dbrij login prints a short code and opens your browser. You confirm the code there, signed in as yourself, and the terminal receives a token. Your password never touches the terminal, and a machine with no browser (a server, a container) can be authorised from your phone — it is the same OAuth device flow gh auth login uses.

The token is stored in ~/.dbrij/auth.json with mode 600. It has no expiry, so the only thing that ends it is revoking it: Settings → Security → Terminals, or dbrij logout on the machine itself.

What gets uploaded

Everything in the directory, minus:

1. an always-ignored list — node_modules, .git, build output, and .env files, *.pem, *.key, id_rsa;
2. your .gitignore;
3. your .dbrijignore, if you have one.

Later rules win, so .dbrijignore can re-include something git ignores — including, deliberately, something on the always-ignored list. Nothing secret goes up by accident; overriding that is a decision you have to type.

The archive goes straight to object storage with a presigned URL. It never passes through the API, and it is deleted after seven days — the built image is the artefact worth keeping, and holding everyone's working directory indefinitely is a liability.

Commands

| | | |---|---| | dbrij login | Sign in. --force to switch accounts. | | dbrij logout | Revoke this machine's token. | | dbrij whoami | Who you are signed in as. | | dbrij link | Point this directory at a service (creates one if needed). | | dbrij deploy | Pack, upload, build, roll out. -m "message", --no-wait. | | dbrij status | Service state and the last five deployments. | | dbrij logs | Runtime logs. --build for the build log. | | dbrij env | List keys. add KEY=value, rm KEY, pull. | | dbrij open | Open the deployed site. | | dbrij ls | Projects and services. | | dbrij rollback | Put the previous build back. |

CI

Set DBRIJ_TOKEN and skip the login entirely:

- run: npx dbrij deploy --no-wait
  env:
    DBRIJ_TOKEN: ${{ secrets.DBRIJ_TOKEN }}

Mint that token by running dbrij login once on any machine and copying ~/.dbrij/auth.json, or from Settings → Security → Terminals.

DBRIJ_API_URL points the CLI at a self-hosted control plane. DBRIJ_DEBUG=1 prints stack traces.