This guide documents the standard TorresVault workflow for bringing up any new Ubuntu VM or new self‑hosted app — including assigning a fixed IP in UniFi, adding DNS, and routing through NPM and Cloudflare.

Use this as your repeatable checklist every time you deploy something new.

—

Steps:

* Create an Ubuntu Server VM (use your preferred template) * Assign CPU/RAM/disk according to app needs * Boot and complete Ubuntu installation * Run updates:

sudo apt update && sudo apt upgrade -y && sudo apt autoremove -y

—

Why: Ensures stable networking for DNS + proxy routing.

Steps:

* Open UniFi Controller → Clients * Find your VM (usually shows up as DHCP) * Click Client → Settings → Network * Enable Use Fixed IP * Assign your desired IP (e.g., `192.168.1.x`) * Save → VM may need a reboot

Verify inside VM:

ip a 

—

Goal: Let LAN devices access the internal service using a hostname.

Steps:

* Pi-hole Admin → Local DNS → DNS Records * Add:

• Domain: `<app>.in.torresvault.com`
• IP: `<VM Fixed IP>`

* Save

Test:

ping <app>.in.torresvault.com 

—

Purpose: Public HTTPS access to the service.

Steps:

* NPM → Proxy Hosts → Add Proxy Host * Domain Names: `<app>.torresvault.com` * Forward Hostname/IP: `<VM Fixed IP>` * Forward Port: `APP_PORT` * Enable:

• Block Common Exploits
• Websockets Support (if needed)
• HTTP/2 Support

SSL Tab:

* Request a new certificate * Enable Force SSL * Use DNS Challenge (Cloudflare)

Save.

—

If using Cloudflare DNS challenge (recommended):

* Cloudflare → DNS * Add an A record:

• Name: `<app>`
• IP: Public IP of the UCG Max
• Proxy: Proxied (orange cloud)

If NPM is handling the service through Cloudflare's DNS challenge, NPM renews certs automatically.

—

Create app structure:

mkdir -p ~/apps/<app>/config
mkdir -p ~/apps/<app>/data
cd ~/apps/<app>

Create your `docker-compose.yml`:

version: "3.9"
services:
  app:
    image: <image>
    container_name: <app_name>
    restart: unless-stopped
    ports:
      - "PORT:PORT"
    volumes:
      - ./config:/config
      - ./data:/data
    environment:
      - TZ=America/New_York

Bring it up:

docker compose up -d 

—

Internal URL:

* http:<app>.in.torresvault.com External URL: * https:<app>.torresvault.com

Check container logs:

docker logs -f <app_name> 

Check NPM logs if needed:

* NPM → Logs → Proxy Host Logs

—

☐ VM updated & rebooted

☐ Fixed IP assigned in UniFi

☐ Internal DNS added in Pi-hole (`app.in.torresvault.com`)

☐ Reverse proxy entry added in NPM

☐ Cloudflare DNS record created

☐ SSL cert obtained via DNS challenge

☐ App deployed via Docker Compose

☐ Both internal & external URLs tested

—