@grove-sh/cli 0.3.0-beta.2 → 0.4.0-beta.1

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.
Files changed (2) hide show
  1. package/README.md +24 -3
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -1,20 +1,41 @@
1
1
  # grove
2
2
 
3
- Local HTTPS hostnames, ports, and env vars, scoped per git worktree.
3
+ Two branches of the same app cannot both be running, not without juggling ports by hand and editing `.env` for each one. So mostly you stop the first to look at the second.
4
4
 
5
- Every worktree of a repository gets its own hostname, its own ports, and its own environment, so several checkouts run at the same time without colliding:
5
+ Grove makes a git worktree the unit. Each one gets its own hostname, its own ports, and its own environment, so several checkouts serve at the same time:
6
6
 
7
7
  ```
8
8
  ~/work/app https://app.grov.site postgres on 20402
9
9
  ~/worktrees/app/feat https://app-feat.grov.site postgres on 20533
10
10
  ```
11
11
 
12
+ No port in the URL, a real certificate your browser trusts, and one command to run anything inside that context:
13
+
14
+ ```sh
15
+ grove exec -- pnpm dev
16
+ ```
17
+
18
+ ## Installing
19
+
12
20
  ```sh
13
21
  npm install -g @grove-sh/cli
14
22
  grove install
15
23
  ```
16
24
 
17
- This package is a wrapper: it installs the binary for your platform and runs it. `grove install` is a separate step on purpose, because it generates a certificate authority and adds it to your trust stores, which is not something to do quietly during an `npm install`.
25
+ This package is a wrapper. It installs the binary for your platform and runs it.
26
+
27
+ `grove install` is a separate step on purpose. It generates a certificate authority and adds it to your trust stores, and it prints the one privileged step your platform needs instead of running it. Neither belongs in an `npm install` that nobody is watching.
28
+
29
+ ## It runs beside your other tools
30
+
31
+ Grove serves `127.0.0.4`, so it never competes for port 443:
32
+
33
+ ```
34
+ 127.0.0.1:443 docker-proxy <- lando
35
+ 127.0.0.4:443 grove
36
+ ```
37
+
38
+ Nothing to stop before you can use something else. And grove does not run your services, it addresses the ones you already start. If you want containers built and a stack managed, that is lando or ddev, and grove is happy to sit next to either.
18
39
 
19
40
  Full documentation: https://github.com/grove-sh/cli
20
41
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@grove-sh/cli",
3
- "version": "0.3.0-beta.2",
3
+ "version": "0.4.0-beta.1",
4
4
  "description": "Local HTTPS hostnames, ports, and env vars, scoped per git worktree",
5
5
  "keywords": [
6
6
  "git-worktree",
@@ -26,15 +26,15 @@
26
26
  "bin/"
27
27
  ],
28
28
  "engines": {
29
- "node": ">=18"
29
+ "node": ">=22"
30
30
  },
31
31
  "publishConfig": {
32
32
  "access": "public"
33
33
  },
34
34
  "optionalDependencies": {
35
- "@grove-sh/cli-darwin-arm64": "0.3.0-beta.2",
36
- "@grove-sh/cli-darwin-x64": "0.3.0-beta.2",
37
- "@grove-sh/cli-linux-arm64": "0.3.0-beta.2",
38
- "@grove-sh/cli-linux-x64": "0.3.0-beta.2"
35
+ "@grove-sh/cli-darwin-arm64": "0.4.0-beta.1",
36
+ "@grove-sh/cli-darwin-x64": "0.4.0-beta.1",
37
+ "@grove-sh/cli-linux-arm64": "0.4.0-beta.1",
38
+ "@grove-sh/cli-linux-x64": "0.4.0-beta.1"
39
39
  }
40
40
  }