@light-cloud/cli 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Light Cloud Team
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,131 @@
+# Light Cloud CLI
+
+`lc` is the Light Cloud command line: deploy an app and watch the build stream
+by, tail runtime logs, set environment variables, roll back, manage databases.
+Everything the console does for an app, from the terminal, with `--json` for
+scripts.
+
+```
+$ lc deploy
+┌  ☁ Light Cloud deploy
+│
+│  my-app → production ★
+│  Source: github.com/acme/my-app @ main
+│
+◇  Deployment queued  my-app / production
+◇  Cloning repository  2.1s
+◇  Building image  58s
+◇  Deploying container  14s
+◇  Deployed in 1m 16s  https://my-app.acme.light-cloud.io
+│
+└  Live at https://my-app.acme.light-cloud.io
+```
+
+## Install
+
+```bash
+npm install -g @light-cloud/cli
+lc --version
+```
+
+Node 18.17 or newer. `lc` and `light-cloud` are the same binary.
+
+## First run
+
+```bash
+lc login          # opens the browser; tokens land in ~/.lightcloud/credentials.json
+cd my-project
+lc init           # link the folder to an existing app, or create one
+lc deploy         # deploy and follow the build
+lc logs -f        # tail runtime logs
+```
+
+`lc login` shares its credential file with the Light Cloud MCP server, so
+signing in once serves both.
+
+## Commands
+
+| Command | What it does |
+|---|---|
+| `lc login` / `logout` / `whoami` | Browser sign-in, or `lc login --api-key lc_…` for machines |
+| `lc orgs`, `lc org use <name>` | List workspaces; choose the default one |
+| `lc init` | Link this folder to an app (wizard) |
+| `lc create` | Create an app from a GitHub repository or an upload, flag-driven |
+| `lc apps [filter]` | Apps in the workspace with status and URL |
+| `lc status [app]` | One app: environments, URLs, domains, last deploy |
+| `lc deploy [app] [--env x] [--upload]` | Deploy and follow; `--no-watch` to just queue |
+| `lc open [app]` | Open the deployed URL (`--console` for the dashboard) |
+| `lc envs`, `lc env create/delete/scale/get` | Environments |
+| `lc env vars [set/unset/import/export]` | Environment variables; `--redeploy` to apply |
+| `lc logs [-f] [--since 2h] [--min-severity WARNING] [--search text]` | Runtime logs |
+| `lc deployments`, `lc deployment <id>` | History and the build log of one deployment |
+| `lc rollback [id]` | Roll back to an earlier deployment, no rebuild |
+| `lc domains add/check/retry/remove` | Custom domains with the DNS records to create |
+| `lc dbs`, `lc db create/get/url/rotate-password/dump/delete` | Databases |
+| `lc billing`, `lc billing plans`, `lc billing plan use <id>`, `lc billing card add/remove` | Plan, usage pool and payment card (card via a Stripe-hosted link) |
+| `lc login --device [--email <address>]` | Sign in — or sign up — with a code from any device; no browser needed here |
+| `lc config`, `lc unlink` | Endpoint settings; remove the link file |
+
+Every command takes `--json`, `--org <workspace>`, `--yes` and `--api-url`.
+
+## How a folder is linked
+
+`lc init` writes a `.lightcloud` file:
+
+```json
+{
+  "organisationId": "…",
+  "applicationId": "…",
+  "environmentId": "…",
+  "applicationName": "my-app",
+  "framework": "nextjs",
+  "deploymentType": "container"
+}
+```
+
+Commands run from that folder (or any subfolder) act on that app. The same
+file is read by the MCP server and the VS Code extension. Commit it if the
+whole team deploys the same app; ignore it if not.
+
+## CI and scripts
+
+Create an API key in the console (Organisation settings → API keys; paid
+plans), then:
+
+```bash
+export LIGHT_CLOUD_API_KEY=lc_…
+lc deploy --yes            # in a folder with .lightcloud
+lc apps --json | jq '.[].name'
+```
+
+An API key is bound to one workspace, so `--org` is not needed. Without a
+terminal, prompts are never shown: anything that would have asked fails with
+the flag to pass instead.
+
+Exit codes: `0` ok · `1` error · `2` usage · `3` not signed in · `4` not found ·
+`5` the deployment or provisioning failed · `130` cancelled.
+
+## Staging or a local API
+
+```bash
+lc config set api-url https://api.staging-light-cloud.com
+# or per command
+LIGHT_CLOUD_API_URL=http://localhost:5001 lc apps
+```
+
+The console URL is inferred from the API URL (`api.` → `console.`); override it
+with `lc config set console-url …` or `LIGHT_CLOUD_CONSOLE_URL`.
+
+## Development
+
+```bash
+npm install
+npm run dev -- apps            # run from source
+npm run typecheck
+npm test
+npm run build                  # dist/index.js, single file
+node dist/index.js --help
+```
+
+Framework detection rules live in `src/lib/detection/catalogue.ts`, a snapshot
+of the backend catalogue; the header of that file says how to regenerate it.