@lukoweb/apitogo 0.1.76 → 0.1.78

package/docs/configuration/make-config.mdx

@@ -7,7 +7,7 @@ description:
   authentication settings.
 ---
 
-The **`apitogo make-config`** command writes **`apitogo.config.json`**. It can scaffold a portal
+The **`apitogo config`** (alias: `make-config`) command writes **`apitogo.config.json`**. It can scaffold a portal
 project (package.json, tsconfig, landing and user-panel stubs, thin `apitogo.config.tsx`) when those
 files are missing, merge **site / theme / authentication** from flags or an interactive wizard, scan
 `pages/` for navigation, and wire OpenAPI plus an **API Reference** link.
@@ -26,8 +26,10 @@ Landing and user panel are **always enabled** on new configs. The command does *
 3. **Patches site, theme, and auth** from `--site`, `--theme`, `--authentication`, `--title`, or
    `--interactive`.
 4. **Merges `navigation`** from `.md` / `.mdx` / `.tsx` files under your pages directory into a
-   Documentation category. Other nav items are kept. Use **`--force`** to rebuild Documentation items
-   from disk (API Reference is still kept when OpenAPI is wired).
+   Documentation category when those files exist. **Missing or empty `pages/` is fine** (common for
+   portal-only sites) — existing navigation is left alone. Other nav items are kept. Use
+   **`--force`** to rebuild Documentation items from disk when pages are present (API Reference is
+   still kept when OpenAPI is wired).
 5. **Wires OpenAPI** when a spec is found (or confirmed in interactive mode):
    `apis: [{ type: "file", input, path: "api" }]` and a top-level **API Reference** link to `/api` if
    that link is missing.
@@ -37,7 +39,7 @@ Landing and user panel are **always enabled** on new configs. The command does *
 Run from your project root (where `apitogo.config.json` and `package.json` live):
 
 ```bash
-apitogo make-config
+apitogo config
 ```
 
 ### Options
@@ -56,9 +58,9 @@ apitogo make-config
 Examples:
 
 ```bash
-apitogo make-config --title "Books API"
-apitogo make-config --theme '{"light":{"primary":"#111111"}}'
-apitogo make-config --interactive
+apitogo config --title "Books API"
+apitogo config --theme '{"light":{"primary":"#111111"}}'
+apitogo config --interactive
 ```
 
 There is **no `--modules` flag**. Edit `modules` in `apitogo.config.json` if you need to change

package/docs/deploy/apitogo.md

@@ -1,145 +1,51 @@
----
-title: Deploy with APIToGo CLI
----
+# Deploy with APIToGo CLI
 
-[APIToGo](https://apitogo.com) hosts your documentation site. This page covers the **CLI** path
-(`apitogo deploy` with a deployment token).
+Publish your local portal (and optional API hub) to the APItoGo platform with
+`apitogo apply`. This is the same engine as MCP `publish_dev_portal`.
 
-For a full API product (plans, `dev-portal` auth, gateway, platform Free / Starter / Professional),
-use MCP **`publish_dev_portal`** / `apply_product_intent` mode `goLive` — see
-[MCP go-live](../mcp/go-live.md).
+## Prerequisites
 
-| Path                     | When                                              |
-| ------------------------ | ------------------------------------------------- |
-| MCP `publish_dev_portal` | Connected portal + plans + hosting go-live        |
-| CLI `apitogo deploy`     | Build and upload a site with a deployment token   |
+- `APITOGO_API_KEY_ID` and `APITOGO_API_SECRET` in the environment
+- A site directory with `apitogo.config.json` (use `apitogo init` / `apitogo config`)
+- Secrets such as OIDC (and Stripe when you have paid plans) in `.env` as
+  `APITOGO_CONFIG_AUTHENTICATION__*`
 
-## Before you deploy
+## Apply everything
 
 ```bash
-npm run dev
+apitogo apply
 ```
 
-## Deploy with the CLI
+Creates or links the platform project, provisions modules, syncs gateway plans,
+deploys the API hub (when configured), updates the portal backend, and builds +
+deploys the portal frontend.
 
-To publish a site with a deployment token:
-
-1. Sign in to [apitogo.com](https://apitogo.com)
-2. Create a new project or open an existing one
-3. Navigate to Project settings and copy the deployment token
-4. Run the following command:
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --env=<environment-name>
-```
-
-The `--env` value is the **environment name** your deploy server uses. It must match what is
-configured for your project (see the APIToGo dashboard / deploy API).
-
-Common patterns:
-
-- **`production`** — main live site (default when `--env` is omitted)
-- **Named non-production environments** — any label your backend accepts, for example `staging`,
-  `dev`, or `preview`
-- **Multiple preview slots** — separate previews such as `preview-a` and `preview-b` when your
-  `/deploy` endpoint supports them:
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --env=preview-a
-apitogo deploy --deployment-token=<TOKEN> --env=preview-b
-```
-
-If you do not provide `--env`, APIToGo deploys to `production` by default:
+## Target specific resources
 
 ```bash
-apitogo deploy --deployment-token=<TOKEN>
+apitogo apply --only apihub
+apitogo apply --only portal-backend
+apitogo apply --only portal-frontend
+apitogo apply --only apihub,portal-frontend
+apitogo apply --only portal-frontend --force
 ```
 
-### JSON-only mode (`--json-only`)
+| Resource | What it updates |
+| --- | --- |
+| `apihub` | Gateway plans/baseline, API hub package + deploy, public routes |
+| `portal-backend` | Dev-portal module settings and plan catalog |
+| `portal-frontend` | Site build + Static Web App deploy |
 
-Use `--json-only` when you want **machine-readable output** from the whole command (for example
-piping to `jq` in CI).
+Omit `--only` to apply all three. Use `--force` to redeploy even when hashes match.
 
-- **Standard output** is a **single JSON value**: on success, the parsed deploy API response (the
-  same payload the server returns with `?jsonOnly=true`). On failure (including build errors),
-  stdout is `{"error":"..."}` and the process exits with a non-zero code.
-- The CLI **suppresses** normal build and progress logs so they do not mix with that JSON.
-- The deploy request still includes `?jsonOnly=true` on the endpoint.
+## Other useful commands
 
 ```bash
-apitogo deploy --deployment-token=<TOKEN> --json-only
+apitogo status          # account + project + live checks
+apitogo teardown --yes  # delete the platform project
+apitogo build           # local production build
+apitogo build --preview # preview the production build locally
 ```
 
-Combine with `--env` as usual (including named previews such as `preview-a`):
-
-```bash
-apitogo deploy --deployment-token=<TOKEN> --env=preview --json-only
-apitogo deploy --deployment-token=<TOKEN> --env=preview-a --json-only
-```
-
-## Deploy with GitHub Actions
-
-You can automate deploys from GitHub so every merge to `main` updates production and every pull
-request gets a **preview** URL.
-
-### 1. Generate the workflow
-
-From your documentation project root (the folder that contains `apitogo.config.json` and `package.json`),
-run:
-
-```bash
-apitogo configure-github-workflow
-```
-
-This creates `.github/workflows/apitogo-deploy.yml` with two jobs:
-
-- **Preview** — runs on pull requests targeting `main`. It deploys to an environment named like
-  `preview-pr-<number>` and exposes the preview URL on the GitHub Actions run.
-- **Production** — runs on pushes to `main`. It deploys with the default production environment.
-
-If the file already exists, pass `--force` to overwrite it.
-
-### 2. Add your deployment token as a GitHub secret
-
-1. In [APIToGo](https://apitogo.com), open your project and copy the **deployment token** from
-   project settings (the same token you use with `apitogo deploy`).
-2. On GitHub, open your repository → **Settings** → **Secrets and variables** → **Actions**.
-3. Create a new repository secret named **`APITOGO_TOKEN`** and paste the token.
-
-The generated workflow reads that secret as `${{ secrets.APITOGO_TOKEN }}`.
-
-### 3. Optional: GitHub environments
-
-The workflow references **`preview`** and **`production`**
-[environments](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment).
-If you use environment protection rules, create matching environments in the repo settings and
-attach reviewers or branch filters as needed. If you do not use environments, the jobs still run;
-you can simplify the workflow later to drop `environment:` blocks.
-
-### 4. Commit and ship
-
-Add the new workflow to version control, commit, and push:
-
-```bash
-git add .github/workflows/apitogo-deploy.yml
-git commit -m "Add APIToGo GitHub Actions deploy workflow"
-git push
-```
-
-After that, pushes and pull requests against `main` trigger deploys automatically. You can also run
-the workflow manually from the **Actions** tab (**workflow_dispatch**).
-
-## What to verify after deployment
-
-After your site is live, check the following:
-
-- Navigation load correctly
-- Static assets such as images and logos resolve correctly
-- OpenAPI references and API playground features load as expected
-- Any custom domain or redirects are working properly
-
-## Open APIToGo
-
-To get started, sign in here:
-
-- [APIToGo Dashboard](https://apitogo.com)
+Multi-environment SWA deploy (`apitogo deploy --env …`) and
+`apitogo configure-github-workflow` are removed. Use `apitogo apply` instead.

package/docs/deployment.md

@@ -1,22 +1,8 @@
----
-title: Deploying APIToGo
----
+# Deployment
 
-Choose how you publish:
+| Path | Docs |
+| --- | --- |
+| **CLI** (`apitogo apply`) | [Deploy with APIToGo CLI](./deploy/apitogo.md) |
+| **MCP / agents** | [Go live](./mcp/go-live.md) |
 
-| Path | Guide |
-| ---- | ----- |
-| **MCP go-live** (portal + plans + hosting) | [MCP go-live](./mcp/go-live.md) |
-| **CLI** (`apitogo deploy` + token) | [Deploy with APIToGo CLI](./deploy/apitogo.md) |
-| **Static host** (GitHub Pages, upload `dist`) | Below and sibling deploy guides |
-
-## Build locally
-
-Produce static HTML, JavaScript, and CSS for any host:
-
-```bash
-npm run build
-```
-
-Output is in `dist/`. Upload that folder, or use [direct upload](./deploy/direct-upload.md) /
-[GitHub Pages](./deploy/github-pages.md).
+Local-only builds: `apitogo build` (optional `--preview`). Platform publish is always `apitogo apply`.

package/docs/mcp/go-live.md

@@ -88,7 +88,7 @@ shape → deploy_backend → publish_dev_portal(skipBackendRedeploy: true)
 | Path                         | Use when                                              |
 | ---------------------------- | ----------------------------------------------------- |
 | MCP `publish_dev_portal`     | Full product go-live (plans, auth, hosting, verify)   |
-| CLI `apitogo deploy`         | Build + deploy a site with a deployment token only    |
+| CLI `apitogo apply`          | Publish config to platform (apihub + portal)          |
 
 See [Deploy with APIToGo CLI](../deploy/apitogo.md).
 

package/docs/quickstart.md

@@ -76,6 +76,6 @@ cd your-project-name
 npm run dev
 ```
 
-For an existing `pages/` + OpenAPI folder: `apitogo make-config` (see
+For an existing `pages/` + OpenAPI folder: `apitogo config` (see
 [Make config](./configuration/make-config.mdx)). That command writes `apitogo.config.json`. Site-only
 deploy with a token: [Deploy with APIToGo CLI](./deploy/apitogo.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lukoweb/apitogo",
-  "version": "0.1.76",
+  "version": "0.1.78",
   "type": "module",
   "sideEffects": [
     "**/*.css",