Networks

Create, inspect, and manage Docker networks across connected VPS servers.

Networks in tug.sh map directly to Docker networks on each connected VPS.

Why networks matter

Use networks to:

  • isolate traffic between services,
  • connect app and database containers privately,
  • keep only selected ports exposed publicly.

Create a network

  1. Open Networks in the dashboard.
  2. Click New network.
  3. Select the target VPS.
  4. Enter a network name (for example app-network).
  5. Confirm creation.

tug.sh sends the request to the Agent, and the Agent creates the network on that VPS.

Inspect network usage

The Networks table shows:

  • network name,
  • VPS where the network exists,
  • containers currently attached to that network.

This makes it easy to verify which services share the same internal layer.

Delete a network safely

You can remove a network only when no active containers depend on it.

Recommended sequence:

  1. Stop or reconfigure attached containers.
  2. Detach them from the network.
  3. Delete the network from Networks.

Best practices

  • Use one dedicated app network per project.
  • Keep database containers on private networks.
  • Expose only ingress containers (for example TugRouter or reverse proxies).