You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,8 @@ Use it when your dev server is running on a remote machine and you want to open
20
20
- Runs any command you pass it, such as `pnpm dev`, `npm run dev`, `bun run dev`, or `python -m http.server`.
21
21
- Streams the child command's stdout/stderr normally.
22
22
- Detects common dev-server output formats, including `http://localhost:5173`, `http://127.0.0.1:3000`, `started server on 0.0.0.0:8080`, and `PORT=4321`.
23
+
- Ignores timing output like `ready in 500 ms` so it does not accidentally expose port `500`.
24
+
- Waits briefly after the first candidate port so multi-process commands, such as Laravel plus Vite, can print the better app-server URL.
23
25
- Waits for the detected port to accept local connections before exposing it.
- Prints the HTTPS MagicDNS URL for the current Tailscale device.
@@ -150,6 +152,22 @@ That prints a URL like:
150
152
https://my-host.tailabc.ts.net:8450
151
153
```
152
154
155
+
### Laravel / `composer run dev`
156
+
157
+
Laravel development commands often start both the PHP app server and the Vite asset server. `lizardtail` prefers output from the app server when it can see both ports:
158
+
159
+
```bash
160
+
lizardtail composer run dev
161
+
```
162
+
163
+
If your app server lands on a known port, you can force it:
164
+
165
+
```bash
166
+
lizardtail --port 8001 composer run dev
167
+
```
168
+
169
+
If browser assets fail to load, the Vite server may also need to be exposed or your Laravel/Vite config may need to allow the Tailscale hostname.
0 commit comments