@dura-run/cli 0.1.5 → 0.2.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 CHANGED
@@ -1,20 +1,50 @@
1
1
  # @dura-run/cli
2
2
 
3
- CLI for the [dura.run](https://dura.run) managed automation platform.
3
+ Command-line tool for [dura.run](https://dura.run) deploy TypeScript and JavaScript automations with one command.
4
4
 
5
5
  ## Install
6
6
 
7
- ```
8
- npm i -g @dura-run/cli
7
+ ```bash
8
+ npm install -g @dura-run/cli
9
9
  ```
10
10
 
11
- ## Get started
11
+ ## Quickstart
12
12
 
13
- ```
13
+ ```bash
14
+ # 1. Authenticate
14
15
  dura login
16
+
17
+ # 2. Create a new project with a POST endpoint
18
+ dura new my-api --trigger post
19
+ cd my-api
20
+
21
+ # 3. Run it locally
22
+ dura dev
23
+ # → http://localhost:3000/hello
24
+
25
+ # 4. Deploy
15
26
  dura deploy
16
27
  ```
17
28
 
29
+ ## Common commands
30
+
31
+ | Command | Purpose |
32
+ |---|---|
33
+ | `dura new <name>` | Scaffold a new project (`--trigger get\|post\|cron`) |
34
+ | `dura init` | Add dura.json to an existing directory |
35
+ | `dura dev` | Local dev server with hot reload |
36
+ | `dura deploy` | Deploy to the dura cloud |
37
+ | `dura logs --follow` | Tail execution logs |
38
+ | `dura secrets set KEY value` | Store a secret for an automation |
39
+ | `dura endpoint-keys create <name>` | Issue an API key for private HTTP triggers |
40
+ | `dura diagnose <exec-id>` | AI-powered analysis of a failed execution |
41
+
42
+ All project-scoped commands pick up `projectId` from `dura.json` — you only need `--project <id>` when running outside a project directory.
43
+
18
44
  ## Documentation
19
45
 
20
- https://dura.run/docs
46
+ Full docs and recipes at [dura.run/docs](https://dura.run/docs).
47
+
48
+ ## License
49
+
50
+ MIT