YuraNetworkDocumentation libraryPreserved resource
YuraNetwork
Guide

Step‑by‑step Yura Network setup

Pick a path below. Each path is short, clear, and complete.

Path A — Browser App (Recommended)

One small app that handles the tunnel and opens Yura sites.

Step 1 — Download setup

Windows Setup Script Linux/macOS Setup Script

Step 2 — Run setup

Windows:

cd $env:USERPROFILE\Downloads Set-ExecutionPolicy -Scope Process Bypass -Force .\YuraBrowserApp-Setup.ps1

Linux/macOS:

cd ~/Downloads chmod +x ./YuraBrowserApp-Setup.sh ./YuraBrowserApp-Setup.sh

Step 3 — Expected result

  • App opens with URL bar + back/forward.
  • Tunnel starts if needed.
  • Torch search opens at https://torch.yura.

Path B — Manual Tunnel Connect

Use this if you want script‑level control.

Step 1 — Download scripts

Step 2 — Connect

Windows (run PowerShell as Administrator):

cd $env:USERPROFILE\Downloads Set-ExecutionPolicy -Scope Process Bypass -Force .\YuraConnect.ps1

Linux/macOS:

cd ~/Downloads chmod +x ./YuraConnect.sh ./YuraConnect.sh

Step 3 — Save your Publisher ID + Key

  • Printed on screen after connect.
  • Saved locally:
    • Windows: %TEMP%\yura-connect\yura-publisher.json
    • Linux/macOS: /tmp/yura-connect/yura-publisher.json

Step 4 — Disconnect later

Windows:

cd $env:USERPROFILE\Downloads Set-ExecutionPolicy -Scope Process Bypass -Force .\YuraDisconnect.ps1

Linux/macOS:

cd ~/Downloads chmod +x ./YuraDisconnect.sh ./YuraDisconnect.sh

Path C — Static Website

Best for HTML/CSS/JS sites. Fastest and simplest.

Important IDs (short version)

  • Tunnel ID changes every connect. Ignore it.
  • Publisher ID + Key are permanent. Save them.
  • Domain is the URL people visit.

Step 1 — Download site kit (one‑time)

$publisherId = 'pub_xxx' $publisherKey = 'your_key_here' $desiredDomain = '' # empty = random domain $body = @{ publisherId=$publisherId; publisherKey=$publisherKey; desiredDomain=$desiredDomain } | ConvertTo-Json Invoke-WebRequest -Method Post -Uri 'https://yuranetwork.com/api/sitekit/create' -ContentType 'application/json' -Body $body -OutFile .\yura-site-kit.zip

Step 2 — Extract once

Expand-Archive -Force .\yura-site-kit.zip .\yura-site-kit

Step 3 — Run the kit (Windows)

cd .\yura-site-kit\yura-site-kit .\yura-site-up.ps1

First run will ask: Random or Custom domain. Your choice is saved to this folder.

Step 4 — Run the kit (Linux/macOS)

cd yura-site-kit/yura-site-kit chmod +x ./yura-site-up.sh ./yura-site-up.sh

Step 5 — Open your site

The script prints your URL, e.g. https://abc123xyz.yura.

Reopen the same site later (same domain)

  1. Reconnect to Yura if needed.
  2. Go back to the same kit folder.
  3. Run yura-site-up again — it reuses the saved domain.
.\yura-site-up.ps1

Turn your site off

.\yura-site-stop.ps1 ./yura-site-stop.sh

Stopping only shuts down your local server. The domain stays reserved to your Publisher ID.

Multiple websites

Copy the entire yura-site-kit folder for each site. Each folder keeps its own domain.

Path D — Full‑Stack Website (login, database, APIs)

Yura can publish any app you can run locally (Node, Django, Rails, Go, Next.js, Laravel, etc.). It just forwards traffic to your app’s port.

Step 1 — Start your app locally

Example: your app runs on http://127.0.0.1:3000.

Step 2 — Make sure it listens on your machine (not just localhost)

Your app must listen on 0.0.0.0 (or the 10.77.x.x tunnel IP), so the gateway can reach it.

Step 3 — Connect to Yura (Path A or B)

You need an active tunnel.

Step 4 — Use the site kit and set the app port

  1. Download the site kit (same as Path C).
  2. Open yura-site-config.json and set localPort to your app port (e.g. 3000).
  3. Run yura-site-up.
# Example: set port to 3000 # Open: yura-site-config.json # Change: "localPort": 3000 .\yura-site-up.ps1

Step 5 — Open your .yura domain

Your full‑stack app is now reachable at https://your-domain.yura (tunnel users only).

Quick example (Node/Express)

# start app on port 3000 node server.js # in your app, listen on 0.0.0.0 app.listen(3000, '0.0.0.0')

Notes

  • Login + database work normally — they’re inside your app.
  • If your app stops, the domain goes offline.
  • You can run multiple apps by copying the kit folder and changing ports/domains.