@marina-cloud/cli 0.0.0
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 +67 -0
- package/dist/marina.mjs +2216 -0
- package/package.json +41 -0
package/README.md
ADDED
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
# Marina Cloud CLI
|
|
2
|
+
|
|
3
|
+
Deploy small internal apps to Marina Cloud.
|
|
4
|
+
|
|
5
|
+
```sh
|
|
6
|
+
npm install -g @marina-cloud/cli
|
|
7
|
+
marina setup
|
|
8
|
+
marina deploy
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
`marina setup` opens Clerk in the browser and delivers the resulting API key
|
|
12
|
+
directly back to the CLI. For unattended environments, `MARINA_TOKEN` or
|
|
13
|
+
`marina setup --token mar_…` is the explicit fallback.
|
|
14
|
+
|
|
15
|
+
The saved credential lives in `~/.marina/profile` with user-only permissions.
|
|
16
|
+
Use `marina profile` to inspect the active profile and `marina logout` to remove
|
|
17
|
+
its credential.
|
|
18
|
+
|
|
19
|
+
Setup automatically installs Marina's deployment skill when Codex or Claude is
|
|
20
|
+
detected. Install or refresh it explicitly with:
|
|
21
|
+
|
|
22
|
+
```sh
|
|
23
|
+
marina skills install
|
|
24
|
+
marina skills install --agent codex
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
The CLI checks npm at most once per day and prints an advisory update command
|
|
28
|
+
when a newer release is available. It never updates itself.
|
|
29
|
+
|
|
30
|
+
## Agent-friendly output
|
|
31
|
+
|
|
32
|
+
Every command accepts `--json`. Standard output contains exactly one versioned
|
|
33
|
+
JSON result; progress stays on standard error.
|
|
34
|
+
|
|
35
|
+
```sh
|
|
36
|
+
marina list --json
|
|
37
|
+
marina status --app my-tool --json
|
|
38
|
+
marina deploy --json
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
Successful results have `schema_version: 1` and `ok: true`. Failures have
|
|
42
|
+
`ok: false` and a stable `error.code`; exit codes distinguish errors,
|
|
43
|
+
authentication failures, and deployment refusals.
|
|
44
|
+
|
|
45
|
+
## Deploy a first demo
|
|
46
|
+
|
|
47
|
+
`marina deploy demo --json` deploys the bundled, interactive Hello Marina
|
|
48
|
+
cut-paper collage as a new app. Pass `--name` to override its name.
|
|
49
|
+
|
|
50
|
+
To deploy a real directory literally named `demo`, pass `./demo`.
|
|
51
|
+
|
|
52
|
+
## App manifest
|
|
53
|
+
|
|
54
|
+
Add `marina.json` at the project root to give the app a portable name and icon:
|
|
55
|
+
|
|
56
|
+
```json
|
|
57
|
+
{
|
|
58
|
+
"schema": 1,
|
|
59
|
+
"name": "My App",
|
|
60
|
+
"icon": "⛵",
|
|
61
|
+
"type": "static"
|
|
62
|
+
}
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
For names, the CLI uses `--name`, then `marina.json`, then `package.json`, then
|
|
66
|
+
the directory name. `.marina/project.json` only links the directory to an app
|
|
67
|
+
after its first deploy; do not commit it.
|