Skip to content

Label studio setup

Original OneNote page: Label studio setup

Route: product/technical note to route

Categories: product_technical_or_learning

Source

  • Word export: C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\inbox\onenoteexport\01_PROJECTS\Gauss Compute\Label studio setup.docx
  • MHT export: C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\inbox\onenoteexport\01_PROJECTS\Gauss Compute\Label studio setup.mht

Extracted Notes

These notes are extracted from the Word export so the source is visible in the wiki without moving or deleting the original file.

  • Label studio setup
  • Good, now you’re thinking like a system designer. Let’s compare this properly so you can make a clean, confident decision.
  • You’ve already locked one important thing:
  • 👉 Docker = core platform (correct)
  • Now we only compare the access layer + routing layer:
  • Cloudflare Tunnel (access)
  • NGINX (internal routing)
  • These are not competing tools — they solve different parts of the problem.
  • But you can choose how much complexity you want.
  • 🧭 The Two Real Options You’re Considering
  • 🟢 OPTION 1 — Cloudflare ONLY (No NGINX)
  • 👉 Simplest possible system
  • 🟢 OPTION 2 — Cloudflare + NGINX
  • 👉 Structured / scalable system
  • ⚖️ Comparison — Effort vs Value
  • 🟢 OPTION 1 — Cloudflare ONLY
  • Mini PC ├── Docker │ ├── Label Studio (port 8080) │ ├── Wiki (port 3000 later) │ └── Cloudflare Tunnel ↓ Public HTTPS URLs
  • ⚙️ Effort Required
  • Install cloudflared → easy
  • Authenticate domain → medium (one-time)
  • Create tunnel → easy
  • 👉 Total: ~30–60 min
  • Each service exposed separately
  • 🌐 Access Experience
  • label.yourdomain.com → Label Studiowiki.yourdomain.com → Wiki
  • No central routing logic
  • No unified authentication layer
  • Harder to scale to many apps
  • Each app exposed individually
  • 🧠 When this is perfect
  • 👉 Solo builder / small team
  • 🟢 OPTION 2 — Cloudflare + NGINX
  • Docker: ├── Label Studio ├── Wiki ├── NGINX (gateway)
  • Cloudflare Tunnel ↓yourdomain.com ├── /label → Label Studio ├── /wiki → Wiki
  • ⚙️ Effort Required

URLs Found

  • https://yourdomain.com/labelhttps://yourdomain.com/wiki
  • https://chatgpt.com/g/g-p-69bd1b93a4988191a6bfb2a43c12f101/c/69b48d78-da30-8392-84f1-ab80cc74f989
  • http://labelstudio:8080/
  • http://wiki:3000/
  • http://localhost/labelhttp://localhost/wiki
  • http://localhost:80
  • https://your-domain/labelhttps://your-domain/wiki
  • http://localhost:8080

Next Curation Action

Review for Product Wiki migration. Keep only relationship, GTM, or CRM implications in the Network Wiki.

Sources

  • C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\inbox\onenoteexport\01_PROJECTS\Gauss Compute\Label studio setup.docx
  • C:\Users\adeel\OneDrive\100_Knowledge\203_TextCAD\01_Product_Project_Management\TextCAD_Wiki\inbox\onenoteexport\01_PROJECTS\Gauss Compute\Label studio setup.mht