devlinker 1.2.7__tar.gz → 1.3.0__tar.gz

{devlinker-1.2.7 → devlinker-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devlinker
-Version: 1.2.7
+Version: 1.3.0
 Summary: AI-powered linking and automation tool
 Author-email: Mani <mani1028@users.noreply.github.com>
 Requires-Python: >=3.7
@@ -259,6 +259,34 @@ The test spins up lightweight local frontend and backend apps, starts Dev Linker
 - `POST /api/login` is routed to backend
 - `ws://.../hmr` round-trip works through proxy
 
+## Troubleshooting Links
+
+If local or shared links show blank pages, connection refused errors, or 404s, check these common causes:
+
+1. Docker backend binding
+
+- Symptom: `http://localhost:<backend-port>` refuses connection.
+- Cause: backend process inside container is bound to `127.0.0.1` instead of `0.0.0.0`.
+- Fix: run backend with host `0.0.0.0` (example FastAPI/Uvicorn: `uvicorn app.main:app --host 0.0.0.0 --port 8000`).
+
+2. API prefix mismatch
+
+- Symptom: frontend loads through Dev Linker but API calls return 404.
+- Cause: frontend calls `/api/...`, but backend routes are mounted without `/api` prefix.
+- Fix: expose backend routes under `/api` (or adjust frontend paths to match backend routes).
+
+3. Vite host restrictions
+
+- Symptom: direct Vite URL works, Dev Linker proxy URL is blank or blocked.
+- Cause: Vite host protections reject proxied host/port.
+- Fix: set Vite `server.host` and `server.allowedHosts` to allow proxy use.
+
+Quick isolate sequence:
+
+1. Open `http://localhost:<backend-port>/docs` (or `/health`) directly.
+2. Open Dev Linker local proxy URL and verify UI loads.
+3. Use browser network tab to check API status codes for `/api/*` requests.
+
 ## Real-Time Development
 
 - Run `devlinker` to share one combined frontend/backend URL.

{devlinker-1.2.7 → devlinker-1.3.0}/README.md

@@ -243,6 +243,34 @@ The test spins up lightweight local frontend and backend apps, starts Dev Linker
 - `POST /api/login` is routed to backend
 - `ws://.../hmr` round-trip works through proxy
 
+## Troubleshooting Links
+
+If local or shared links show blank pages, connection refused errors, or 404s, check these common causes:
+
+1. Docker backend binding
+
+- Symptom: `http://localhost:<backend-port>` refuses connection.
+- Cause: backend process inside container is bound to `127.0.0.1` instead of `0.0.0.0`.
+- Fix: run backend with host `0.0.0.0` (example FastAPI/Uvicorn: `uvicorn app.main:app --host 0.0.0.0 --port 8000`).
+
+2. API prefix mismatch
+
+- Symptom: frontend loads through Dev Linker but API calls return 404.
+- Cause: frontend calls `/api/...`, but backend routes are mounted without `/api` prefix.
+- Fix: expose backend routes under `/api` (or adjust frontend paths to match backend routes).
+
+3. Vite host restrictions
+
+- Symptom: direct Vite URL works, Dev Linker proxy URL is blank or blocked.
+- Cause: Vite host protections reject proxied host/port.
+- Fix: set Vite `server.host` and `server.allowedHosts` to allow proxy use.
+
+Quick isolate sequence:
+
+1. Open `http://localhost:<backend-port>/docs` (or `/health`) directly.
+2. Open Dev Linker local proxy URL and verify UI loads.
+3. Use browser network tab to check API status codes for `/api/*` requests.
+
 ## Real-Time Development
 
 - Run `devlinker` to share one combined frontend/backend URL.

{devlinker-1.2.7 → devlinker-1.3.0}/devlinker/detector.py

@@ -6,15 +6,50 @@ from typing import Iterable, Optional, Tuple
 import requests
 
 
-def check_port(port: int, timeout: float = 1.0) -> bool:
-    """Return True when an HTTP service responds on localhost:port."""
+DEFAULT_BACKEND_PROBE_PATHS = (
+    "/health",
+    "/api/health",
+    "/",
+)
+
+
+def check_port(
+    port: int,
+    timeout: float = 1.0,
+    probe_paths: Iterable[str] = DEFAULT_BACKEND_PROBE_PATHS,
+) -> bool:
+    """Return True when an HTTP service is reachable on localhost:port.
+
+    Probe order is health-first (for API-style backends), then root fallback.
+    """
+    normalized_paths: list[str] = []
+    for path in probe_paths:
+        cleaned = path.strip()
+        if not cleaned:
+            continue
+        if not cleaned.startswith("/"):
+            cleaned = f"/{cleaned}"
+        normalized_paths.append(cleaned)
+
+    if not normalized_paths:
+        normalized_paths = ["/"]
+
     for host in ("localhost", "127.0.0.1"):
-        try:
-            response = requests.get(f"http://{host}:{port}", timeout=timeout)
-            if response.status_code < 500:
+        for path in normalized_paths:
+            try:
+                response = requests.get(f"http://{host}:{port}{path}", timeout=timeout)
+            except requests.RequestException:
+                continue
+
+            # Health endpoints must return 2xx/3xx to be considered ready.
+            if path in {"/health", "/api/health"}:
+                if 200 <= response.status_code < 400:
+                    return True
+                continue
+
+            # Root fallback accepts non-error responses.
+            if 200 <= response.status_code < 400:
                 return True
-        except requests.RequestException:
-            pass
     return False
 
 

{devlinker-1.2.7 → devlinker-1.3.0}/devlinker.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devlinker
-Version: 1.2.7
+Version: 1.3.0
 Summary: AI-powered linking and automation tool
 Author-email: Mani <mani1028@users.noreply.github.com>
 Requires-Python: >=3.7
@@ -259,6 +259,34 @@ The test spins up lightweight local frontend and backend apps, starts Dev Linker
 - `POST /api/login` is routed to backend
 - `ws://.../hmr` round-trip works through proxy
 
+## Troubleshooting Links
+
+If local or shared links show blank pages, connection refused errors, or 404s, check these common causes:
+
+1. Docker backend binding
+
+- Symptom: `http://localhost:<backend-port>` refuses connection.
+- Cause: backend process inside container is bound to `127.0.0.1` instead of `0.0.0.0`.
+- Fix: run backend with host `0.0.0.0` (example FastAPI/Uvicorn: `uvicorn app.main:app --host 0.0.0.0 --port 8000`).
+
+2. API prefix mismatch
+
+- Symptom: frontend loads through Dev Linker but API calls return 404.
+- Cause: frontend calls `/api/...`, but backend routes are mounted without `/api` prefix.
+- Fix: expose backend routes under `/api` (or adjust frontend paths to match backend routes).
+
+3. Vite host restrictions
+
+- Symptom: direct Vite URL works, Dev Linker proxy URL is blank or blocked.
+- Cause: Vite host protections reject proxied host/port.
+- Fix: set Vite `server.host` and `server.allowedHosts` to allow proxy use.
+
+Quick isolate sequence:
+
+1. Open `http://localhost:<backend-port>/docs` (or `/health`) directly.
+2. Open Dev Linker local proxy URL and verify UI loads.
+3. Use browser network tab to check API status codes for `/api/*` requests.
+
 ## Real-Time Development
 
 - Run `devlinker` to share one combined frontend/backend URL.

{devlinker-1.2.7 → devlinker-1.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "devlinker"
-version = "1.2.7"
+version = "1.3.0"
 description = "AI-powered linking and automation tool"
 authors = [
     { name = "Mani", email = "mani1028@users.noreply.github.com" }