boosted-cli 0.2.1 → 0.2.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +25 -2
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Boosted
|
|
2
2
|
|
|
3
|
-
Boosted is a local-first, multi-user coding workspace with a task board, task-specific Codex planning conversations, and separate general Codex chats. It ships one Vite + React frontend
|
|
3
|
+
Boosted is a local-first, multi-user coding workspace with a task board, task-specific Codex planning conversations, and separate general Codex chats. It ships one Vite + React frontend as an installable Progressive Web App (PWA) and a Tauri desktop shell.
|
|
4
4
|
|
|
5
5
|
## Development
|
|
6
6
|
|
|
@@ -12,12 +12,35 @@ pnpm dev
|
|
|
12
12
|
cargo run -p boosted-server
|
|
13
13
|
```
|
|
14
14
|
|
|
15
|
-
The
|
|
15
|
+
The browser client uses its current origin; during Vite development, `/api` and WebSocket requests are proxied to `http://127.0.0.1:4782`. Set `VITE_BOOSTED_API_URL` when the service runs elsewhere. The server stores local state under the platform application-data directory, or under `BOOSTED_DATA_DIR` when set.
|
|
16
16
|
|
|
17
17
|
The first browser visit creates the administrator. The admin then creates member accounts. All authenticated users share projects, tasks, history, terminals, and host-level execution access; only the first user can manage accounts and the shared Codex connection.
|
|
18
18
|
|
|
19
19
|
> Boosted currently starts Codex with full host access, matching the selected product policy. Only expose the server to trusted users, and put remote access behind your own authenticated TLS proxy or tunnel.
|
|
20
20
|
|
|
21
|
+
## Machine connections
|
|
22
|
+
|
|
23
|
+
The web/PWA and desktop frontends can save multiple Boosted servers and switch between them from the machine selector or **Settings → Connections**. A connection has its own session and workspace state; switching replaces the whole active workspace, and Boosted never polls or combines data from saved machines.
|
|
24
|
+
|
|
25
|
+
When adding a machine, enter its local alias, URL, and account credentials. A scheme-less host such as `office-pc.local` becomes `http://office-pc.local:4782`; explicit HTTP/HTTPS schemes and ports are preserved. The server must already have its first administrator. Only the automatically generated local browser or desktop connection can perform first-run setup.
|
|
26
|
+
|
|
27
|
+
Boosted connects directly to the URL you provide. It does not provide TLS, server discovery, QR pairing, a relay, VPN/tunnel setup, port forwarding, DNS, or other remote-access configuration. Configure trusted routing and exposure yourself. Browsers block a plain-HTTP server when the frontend itself was loaded over HTTPS; use an HTTPS reverse proxy or load Boosted over HTTP in that case.
|
|
28
|
+
|
|
29
|
+
Existing installations migrate automatically. Browser clients retain the current origin, desktop clients retain `http://127.0.0.1:4782`, and development builds continue to honor `VITE_BOOSTED_API_URL`. The existing session and selected workspace move into that generated connection.
|
|
30
|
+
|
|
31
|
+
## Progressive Web App
|
|
32
|
+
|
|
33
|
+
Production builds include a web app manifest, install icons, and a service worker. Open Boosted over HTTPS (or on localhost), then use the browser’s install action. Chromium browsers also show an in-app installation prompt when installation is available.
|
|
34
|
+
|
|
35
|
+
```bash
|
|
36
|
+
pnpm build
|
|
37
|
+
pnpm preview
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
The PWA precaches the application shell and prompts before activating a newly downloaded version, so an open workspace is never silently replaced. The shell can launch without a network connection, but project data, authentication, terminals, and Codex features still require access to a running Boosted server and are deliberately not cached.
|
|
41
|
+
|
|
42
|
+
System notifications can be enabled under **Settings → Notifications**. Preferences are stored separately for each saved Boosted machine and browser. Users can choose background-only or always-on delivery and independently configure task, Codex chat, and integration sync events. Notification clicks focus Boosted and open the related task or Codex chat when available. Because notifications are driven by the authenticated live connection, the PWA must still be open or running in the background; a fully closed browser does not receive push notifications.
|
|
43
|
+
|
|
21
44
|
## Headless server
|
|
22
45
|
|
|
23
46
|
The quickest way to start the headless server is through npm (Node.js 18+):
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "boosted-cli",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.2",
|
|
4
4
|
"description": "Run the Boosted local-first coding workspace from the command line",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -28,6 +28,7 @@
|
|
|
28
28
|
"scripts": {
|
|
29
29
|
"dev": "pnpm --filter @boosted/web dev",
|
|
30
30
|
"build": "pnpm --filter @boosted/web build",
|
|
31
|
+
"preview": "pnpm --filter @boosted/web preview",
|
|
31
32
|
"test": "pnpm --filter @boosted/web test",
|
|
32
33
|
"typecheck": "pnpm --filter @boosted/web typecheck",
|
|
33
34
|
"desktop": "pnpm --filter @boosted/desktop tauri dev",
|