@nearform/fling 0.2.0 → 0.4.0

package/CHANGELOG.md

@@ -0,0 +1,49 @@
+# Changelog
+
+## Unreleased
+
+## 0.4.0
+
+- **Several Flings.** The CLI remembers every Fling you sign in to, each with its own API key, and
+  uses the current one. `fling login <url>` and `fling setup <url>` add a Fling (or refresh its
+  login) and make it current without signing you out of the others. `fling use` lists them, with
+  each one's name and your email; `fling use <url>` switches (a full address, its host or the start
+  of it). `fling logout <url>` signs out of another Fling and forgets it; a bare `fling logout`
+  still removes the current Fling's key and keeps the Fling. `fling whoami` shows which Fling is
+  current.
+- `--server` and `FLING_URL` pick a remembered Fling for one command and use its stored key (an
+  address you haven't signed in to has no key; `FLING_API_KEY` still overrides). The local MCP
+  server uses the current Fling unless `FLING_URL` (the Claude Desktop extension's **Fling server**)
+  names one, and signing in from it makes that Fling current only when no other is.
+- Upgrading: `~/.fling/config.json` from 0.3 is read as-is, as one remembered Fling that is
+  current. It is rewritten in the new shape (`current` plus `servers`, keyed by address) the next
+  time the CLI saves it, so an older CLI can no longer read it after that.
+
+## 0.3.0
+
+**Breaking: no default server.** The CLI works with any Fling deployment, so it no longer has one
+built in.
+
+- `fling login <url>` (or `fling setup <url>`) signs in to the Fling at that address. The CLI
+  reads the server's `/.well-known/fling` (its name, sites domain, sign-in method) and remembers
+  both in `~/.fling/config.json`; later commands, and `fling login` without a URL, use them.
+  `FLING_URL` and `--server` still override it.
+- Upgrading from 0.2: if you logged in with 0.2, nothing changes; the server you logged in to is
+  kept, and its metadata is fetched the first time it is needed. A config without a server (a new
+  machine, or a key set by hand) fails with `No Fling server set — run fling login <url> …`
+  instead of assuming a server.
+- Site URLs shown before a deploy come from the server's metadata instead of being guessed from
+  the server URL.
+- The local MCP server (`fling mcp`, the Claude Desktop extension) names your Fling and its sites
+  domain in its tool descriptions. The extension's **Fling server** setting has no built-in
+  default; the copy a Fling serves at `/downloads/fling.mcpb` has its address filled in.
+- Comments: `fling comments`, `fling comment` (and `--reply`), `fling resolve`, `fling uncomment`;
+  the local MCP server gains `fling_comments_list`, `fling_comment_add`, `fling_comment_resolve`
+  and `fling_comment_delete` on an instance with the `comments` capability.
+- On an instance with comments, a deploy (`fling deploy`, and the MCP server's `fling_deploy` and
+  `fling_publish`) also gives the review page, the link to share for feedback: in the output box,
+  as `reviewUrl` in `--json` and in the MCP result, where it leads.
+
+## 0.2.0
+
+`fling setup`, a new look, and help by default.

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Nearform
+Copyright (c) 2026 Clifton Cunningham
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -1,14 +1,18 @@
 # @nearform/fling
 
-Fling a folder of static files at [fling.labs.nearform.com](https://fling.labs.nearform.com) and
-get a stable link back:
+Fling a folder of static files at your Fling server and get a stable link back:
 
 ```
-https://<name>.fling.labs.nearform.com
+https://<name>.<your sites domain>
 ```
 
-Site names are one global namespace, first come first served. Sites are private to signed-in Nearformers by default. Share links make them viewable by anyone
-who has the link.
+Site names are one global namespace per server, first come first served. Sites are private to
+people signed in to that Fling by default. Share links make them viewable by anyone who has the
+link.
+
+> **Upgrading from 0.2?** The CLI no longer has a built-in server. If you were logged in with 0.2
+> it carries on with the server you logged in to. Otherwise (or on a new machine) run
+> `fling login <url>` once with your Fling's address. See [CHANGELOG.md](CHANGELOG.md).
 
 ## Install
 
@@ -23,13 +27,15 @@ npx @nearform/fling …
 ## Set up
 
 ```sh
-fling setup
+fling setup https://fling.example.com   # your Fling's address; later runs can leave it out
 ```
 
 This does everything a new machine needs:
 
-1. **Signs you in.** Your browser opens for Nearform Google sign-in and an API key is stored in
-   `~/.fling/config.json` (mode 0600). This is skipped if you're already signed in.
+1. **Signs you in.** The CLI reads the server's `/.well-known/fling` (its name, where its sites
+   live, how people sign in) and remembers it. Your browser opens for sign-in and an API key is
+   stored in `~/.fling/config.json` (mode 0600). This is skipped if you're already signed in.
+   The server becomes your current one; logins to other Flings are kept.
 2. **Adds Fling to Claude Code.** If `claude` is on your PATH, setup installs the Fling plugin
    (skill + MCP server) from the `nearform/fling` marketplace, or updates it if it's already
    installed. `--scope project|local` installs it for this project only (default `user`).
@@ -38,15 +44,34 @@ This does everything a new machine needs:
 
 On a terminal it asks before steps 2 and 3. With `--yes` it does them without asking.
 
-To sign in only, use `fling login`. `fling whoami` shows who you are, and `fling logout` removes the
-key. For CI, set `FLING_API_KEY` instead.
+To sign in only, use `fling login <url>` (the URL is remembered: later `fling login` needs none).
+There is no default server: until you log in, commands say to run `fling login <url>`.
+`fling whoami` shows who you are and which server is current. For CI, set `FLING_URL` and
+`FLING_API_KEY` instead.
+
+### Several Flings
+
+The CLI remembers every Fling you sign in to, each with its own key, and uses the current one.
+`fling login <url>` or `fling setup <url>` adds a Fling (or signs in to it again) and makes it
+current; the others stay signed in.
+
+```sh
+fling use                              # list them: * marks the current one, with its name and your email
+fling use other.example.com            # switch: a full address, its host, or the start of it
+fling --server other.example.com ls    # one command against another Fling, with its own key
+```
+
+`FLING_URL` picks a Fling the same way for every command run with it, and `FLING_API_KEY`
+overrides the stored key. `fling logout` removes the current Fling's key and keeps it current (a
+bare `fling login` signs in again); `fling logout <url>` signs out of another Fling and forgets
+it.
 
 ## Deploy
 
 ```sh
 npm run build
 fling deploy ./dist                        # name generated from the project, e.g. rocketpod-docs; you confirm it
-fling deploy ./dist --name my-app          # → https://my-app.fling.labs.nearform.com
+fling deploy ./dist --name my-app          # → https://my-app.<your sites domain>
 fling deploy ./dist --name my-app --spa    # client-side routing: unknown paths serve index.html
 fling deploy ./dist --public               # no sign-in needed to view
 fling deploy ./dist --yes                  # never prompt (CI): use the generated name as is
@@ -126,7 +151,7 @@ Without `--name`, the name is generated from the folder, never from your user na
 In a terminal, Fling checks the generated name and asks before deploying:
 
 ```
-fling Site name: rocketpod-docs → https://rocketpod-docs.fling.labs.nearform.com/  (new)
+fling Site name: rocketpod-docs → https://rocketpod-docs.sites.example.com/  (new)
 Use "rocketpod-docs"? [Y/n or type another name]
 ```
 
@@ -162,8 +187,24 @@ and a taken name fails (exit 1) with suggestions rather than picking another nam
 | `fling archive <name>` / `fling unarchive <name>` | take offline and keep the files, or bring back |
 | `fling rm <name> [--yes]` | delete permanently |
 
-Global options: `--json` prints machine-readable output, and `--server <url>` points at another
-server. Exit codes are `0` ok, `1` error, `2` not logged in and `3` forbidden.
+## Comments
+
+People review a site on its review page (`<your Fling>/review/<name>`, the **Review** button on the
+sites page): the site beside its comments. Anyone signed in who can open the site can comment; the
+CLI reads and writes the same threads. On a Fling with comments, `fling deploy` (and the MCP
+server's `fling_deploy` / `fling_publish`) also prints the review page as the link to share for
+feedback (`reviewUrl` in `--json`); reviewers sign in to use it.
+
+| Command | |
+|---|---|
+| `fling comments <name> [--path <page>] [--all]` | open threads (with replies) by page; `--all` adds resolved ones |
+| `fling comment <name> "text" [--path <page>]` | comment on a page (default `/`) |
+| `fling comment <name> "text" --reply <id>` | reply to a thread |
+| `fling resolve <name> <id> [--reopen]` | resolve a thread, or reopen it |
+| `fling uncomment <name> <id> [--yes]` | delete a comment (a thread with its replies): your own, or any on your site |
+
+Global options: `--json` prints machine-readable output, and `--server <url>` points one command at
+another server (a remembered one brings its key; see [Several Flings](#several-flings)). Exit codes are `0` ok, `1` error, `2` not logged in and `3` forbidden.
 
 Environment: `FLING_API_KEY`, `FLING_URL`, `FLING_CONFIG_DIR`, `FLING_DEBUG`, `FLING_DOWNLOADS_DIR`
 (where the MCP server looks for files given by name first), `FLING_NO_WAIT=1` (after a deploy or a new share
@@ -185,7 +226,10 @@ Or install it by hand in Claude Code:
 /plugin install fling@fling
 ```
 
-Log in once with `fling login` (or `npx @nearform/fling login` if it is not installed). The MCP server reuses that login.
+Log in once with `fling login <url>` (or `npx @nearform/fling login <url>` if it is not installed).
+The MCP server reuses that login, and its tool descriptions name your Fling and where its sites
+live. It re-reads the config on every call, so after `fling use <url>` it talks to the new current
+Fling without a restart.
 
 The MCP tools:
 
@@ -215,20 +259,23 @@ For Claude Desktop (including Cowork), install the one-click extension. It runs
 on your computer, so Claude can fling files you downloaded or that Claude Desktop saved, by name,
 without uploading anything from Claude's sandbox.
 
-1. Download [fling.mcpb](https://fling.labs.nearform.com/downloads/fling.mcpb).
+1. Download `fling.mcpb` from your Fling (Get started → Download, or `https://<your Fling>/downloads/fling.mcpb`).
 2. Double-click it, or drag it into Claude Desktop, or go to **Settings → Extensions → Advanced
    settings → Install Extension…** and pick the file.
-3. Optional settings: **Fling server** (default `https://fling.labs.nearform.com`) and **Downloads
-   folder** (default `~/Downloads`).
+3. Optional settings: **Fling server** (filled in with the Fling you downloaded it from; empty means
+   the one the CLI is logged in to) and **Downloads folder** (default `~/Downloads`).
 4. Ask Claude to "fling Pitch Deck.html from my Downloads". If you're not signed in, Claude calls
-   `fling_login` and your browser opens. The extension and the CLI share the login in
-   `~/.fling/config.json`.
+   `fling_login` and your browser opens. The extension and the CLI share the logins in
+   `~/.fling/config.json`. With **Fling server** set, the extension always uses that Fling (and its
+   stored key), whichever one the CLI is using; signing in from the extension doesn't change the
+   CLI's current Fling.
 
 It needs Node.js 20 or later, which Claude Desktop provides, on macOS or Windows.
 
-Build it with `pnpm --filter @nearform/fling build:mcpb`. That bundles `src/mcp-entry.ts` and every
-dependency into one file, then validates and packs `mcpb/manifest.json` into `dist/fling.mcpb`.
-CI publishes it at `/downloads/fling.mcpb`.
+Build it with `pnpm --filter ./apps/cli build:mcpb`. That bundles `src/mcp-entry.ts` and every
+dependency into one file, then validates and packs `mcpb/manifest.json` into `dist/fling.mcpb`
+(`FLING_MCPB_SERVER_URL` sets the **Fling server** default). A deploy publishes it at
+`/downloads/fling.mcpb`.
 
 To use the MCP server in another client, run it over stdio:
 
@@ -241,7 +288,7 @@ To use the MCP server in another client, run it over stdio:
 From the repo root:
 
 ```sh
-pnpm cli --server http://localhost:3001 login   # against `pnpm dev`
-pnpm --filter @nearform/fling test
-pnpm --filter @nearform/fling build             # → dist/cli.js
+pnpm cli login http://localhost:47101   # against `pnpm dev`
+pnpm --filter ./apps/cli test
+pnpm --filter ./apps/cli build         # → dist/cli.js
 ```