rick/rosterchirp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v0.12.0 codes for FCM and rebranded jama to RosterChirp

Browse Source
This commit is contained in:
Ricky Stretch
2026-03-22 20:15:57 -04:00
parent 21dc788cd3
commit 819d60d693
40 changed files with 426 additions and 363 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
Caddyfile.example
View File

@@ -1,4 +1,4 @@
# Caddyfile.example — JAMA-HOST reverse proxy
# Caddyfile.example — RosterChirp-Host reverse proxy
#
# Caddy handles SSL automatically via Let's Encrypt.
# Wildcard certs require a DNS challenge provider.
@@ -12,23 +12,23 @@
# CF_API_TOKEN=your_cloudflare_token (or equivalent)
#
# 3. Add a wildcard DNS record in your DNS provider:
# *.jamachat.com → your server IP
# jamachat.com → your server IP
# *.rosterchirp.com → your server IP
# rosterchirp.com → your server IP
#
# Usage:
# Copy this file to /etc/caddy/Caddyfile (or wherever Caddy reads it)
# Reload: caddy reload
# ── Wildcard subdomain ────────────────────────────────────────────────────────
# Handles team1.jamachat.com, teamB.jamachat.com, etc.
# Replace jamachat.com with your actual HOST_DOMAIN.
# Handles team1.rosterchirp.com, teamB.rosterchirp.com, etc.
# Replace rosterchirp.com with your actual HOST_DOMAIN.
*.jamachat.com {
*.rosterchirp.com {
tls {
dns cloudflare {env.CF_API_TOKEN}
}
# Forward all requests to the jama app container
# Forward all requests to the rosterchirp app container
reverse_proxy localhost:3000
# Security headers
@@ -42,13 +42,13 @@
# Logs (optional)
log {
output file /var/log/caddy/jama-access.log
output file /var/log/caddy/rosterchirp-access.log
format json
}
}
# ── Base domain (host admin panel) ───────────────────────────────────────────
jamachat.com {
rosterchirp.com {
reverse_proxy localhost:3000
header {
Strict-Transport-Security "max-age=31536000; includeSubDomains"
@@ -60,7 +60,7 @@ jamachat.com {
# ── Custom tenant domains ─────────────────────────────────────────────────────
# When a tenant sets up a custom domain (e.g. chat.theircompany.com):
#
# 1. They add a DNS CNAME: chat.theircompany.com → jamachat.com
# 1. They add a DNS CNAME: chat.theircompany.com → rosterchirp.com
#
# 2. You add a block here and reload Caddy.
# Caddy will automatically obtain and renew the SSL cert.
@@ -80,7 +80,7 @@ jamachat.com {
# }
# }
#
# *.jamachat.com, jamachat.com {
# *.rosterchirp.com, rosterchirp.com {
# tls { on_demand }
# reverse_proxy localhost:3000
# }