@solcreek/dew 0.7.52 → 0.7.53
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 +20 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -101,6 +101,25 @@ It resolves to the VM's NAT gateway in both the guest and its containers,
|
|
|
101
101
|
so you never hardcode the `192.168.64.x` gateway IP. The host service must
|
|
102
102
|
bind `0.0.0.0` (not `127.0.0.1`) to be reachable from the VM.
|
|
103
103
|
|
|
104
|
+
If the host service is bound to **`127.0.0.1`** (the dev default) — or you
|
|
105
|
+
want to sidestep the macOS 26 VZ NAT regression — expose it explicitly and
|
|
106
|
+
reach it at `host.lo.internal` instead. dew tunnels the declared ports over
|
|
107
|
+
vsock straight to the host's loopback, no `0.0.0.0` bind and no NAT:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
dew up --expose-host 50051
|
|
111
|
+
# in the VM: host.lo.internal:50051 → the host's 127.0.0.1:50051
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
```toml
|
|
115
|
+
# or, in dew.toml:
|
|
116
|
+
[host]
|
|
117
|
+
expose = [50051]
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
dew only ever dials its own loopback on a port you declared, so the VM can't
|
|
121
|
+
reach anything else on the host.
|
|
122
|
+
|
|
104
123
|
### Run any container
|
|
105
124
|
|
|
106
125
|
Run a single OCI image in a microVM — no Docker daemon, sub-second boot,
|
|
@@ -240,6 +259,7 @@ Dev:
|
|
|
240
259
|
dew up --with postgres,redis Dev with built-in services
|
|
241
260
|
dew up --init Write a starter dew.toml
|
|
242
261
|
dew up --services-only Boot services without a dev server
|
|
262
|
+
dew up --expose-host PORT Reach a host 127.0.0.1 service in the VM
|
|
243
263
|
dew down Stop dev environment
|
|
244
264
|
|
|
245
265
|
Share:
|