daymug
§ 01 — install

Pour it once. Drink for years.

Setting up takes about five minutes. After that, everyone on your team just opens a page in their browser — there's nothing else to install on the side.

one line  — for the person setting it up 
# pop this into the computer you'd like daymug to live on,
# then everyone on the team can open it in their browser

$ curl -fsSL https://daymug.com/install.sh | bash
What you need — a short checklist
  • A computer any Mac or Linux that stays on
  • A browser whichever one the team already uses
  • An AI plan your existing subscription works
  • Set-up time about five minutes
  • Updates one click, easy to undo
  • Your data stays on the computer you choose
after the installer finishes

Pick how the team reaches it.

DayMug listens on plain HTTP at 127.0.0.1. To let anyone outside this machine connect, pick one of the three paths below. The installer prints the same menu, so you can also decide later — nothing here is locked in.

Path A · recommended
Managed tunnel on nows.xyz
Free hostname under *-daymug.nows.xyz, TLS at Cloudflare's edge, no firewall changes.

Use this when you don't own a domain, can't open ports, or just want the fastest path to a public URL.

  1. Install cloudflared. 
    # Debian / Ubuntu
sudo apt install -y cloudflared

# RHEL / Fedora
sudo dnf install -y cloudflared

# macOS
brew install cloudflared
  2. Ask the admin for a hostname: 
    daymug website request \
  --alias your-team
  3. An operator approves in DayMug-Admin → Websites.
  4. Bring the tunnel up: 
    daymug website start
    Browse to https://your-team-daymug.nows.xyz.
Re-running either command is safe. Tunnel + DNS are reconciled in place.
Path B · advanced
Your domain + nginx + TLS cert
Terminate TLS yourself with nginx in front of DayMug. Works with any cert authority.

Use this when you already own a domain, you have a public IP (or your own reverse proxy), or your organisation requires a specific cert chain.

  1. Point an A / AAAA record at this machine.
  2. Issue a cert with Let's Encrypt: 
    sudo apt install -y certbot \
  python3-certbot-nginx
sudo certbot --nginx \
  -d chat.example.com
    Certbot installs a renewal timer automatically.
  3. Drop an nginx server block in /etc/nginx/conf.d/daymug.conf. WebSockets need the Upgrade headers and a long proxy_read_timeout: 
    server {
  listen 443 ssl http2;
  server_name chat.example.com;
  ssl_certificate     /etc/letsencrypt/live/…/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/…/privkey.pem;
  location / {
    proxy_pass http://127.0.0.1:8080;
    proxy_http_version 1.1;
    proxy_set_header Host              $host;
    proxy_set_header Upgrade           $http_upgrade;
    proxy_set_header Connection        "upgrade";
    proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_read_timeout 3600s;
  }
}
  4. sudo nginx -t && sudo systemctl reload nginx — done.
In this mode you don't need cloudflared or daymug website request. The installer prints the same nginx snippet so you can paste it from the terminal.
Path C · quickest
Localhost / LAN only
Skip the public-facing layer. DayMug is reachable on this machine and (optionally) on the same network.

Use this when you're evaluating it, you're the only user, or you're inside an office that already has its own VPN.

  1. Open the browser on this machine: 
    http://127.0.0.1:8080
  2. To share with the LAN, change server.addr in ~/.daymug/config.yaml from :8080 to 0.0.0.0:8080, then restart: 
    systemctl --user restart \
  daymug.service
No certs, no tunnels, no proxy. Anything outside your LAN still can't see it — that's the whole point.