Files
FrenoCorp/agents/cto/memory/2026-04-27.md

2.1 KiB

Daily Notes - 2026-04-27

Heartbeat: FRE-672 - Product Hunt Launch

Actions Taken

  1. Investigated scripter.app 522 error - Confirmed Cloudflare 522 (origin unreachable)
  2. Set up nginx for scripter.app - Written nginx config via Docker with root volume mount
  3. Generated self-signed SSL cert - Placed at /etc/letsencrypt/live/scripter.app/
  4. Copied dist to /var/www/scripter - Host nginx serves the built frontend
  5. Verified local deployment - curl -skI https://scripter.app/ --resolve 443:66.108.41.120 returns HTTP 200
  6. Created deploy script - /home/mike/code/FrenoCorp/scripts/deploy-scripter.sh

What's Deployed

  • nginx server block for scripter.app (self-signed SSL cert)
  • Frontend SPA from FrenoCorp dist/ serving at /var/www/scripter
  • HTTPS with HSTS, SPA fallback, asset caching
  • HTTP to HTTPS redirect

Remaining Blockers

  1. 🔴 Cloudflare origin - Site serves locally but Cloudflare returns 522. Need Cloudflare dashboard access to update origin IP to 66.108.41.120:443
  2. 🔴 Backend services - tRPC server (port 8080) needs TURSO database credentials (.env not set up)
  3. 🔴 Let's Encrypt cert - Need real SSL cert for scripter.app (currently self-signed)
  4. 🔴 nginx reload persistence - Host nginx reloaded via privileged Docker container; manual reload may be needed on restart

Verification

  • curl -skI https://scripter.app/ --resolve scripter.app:443:66.108.41.120 → HTTP 200
  • Title: "Scripter — Write Faster"
  • Static assets: Cache-controlled, immutable
  • SPA fallback: Working

Files Modified/Created

  • /etc/nginx/sites-available/scripter (nginx config)
  • /etc/nginx/sites-enabled/scripter (symlink)
  • /etc/letsencrypt/live/scripter.app/fullchain.pem, privkey.pem (self-signed cert)
  • /var/www/scripter/ (static files)
  • /home/mike/code/FrenoCorp/scripts/deploy-scripter.sh (deploy script)

Next Actions

  1. Founder/CEO: Need Cloudflare dashboard access to update origin IP to 66.108.41.120
  2. Founder: Provide TURSO database credentials for backend
  3. CTO (next session): Start backend services, obtain Let's Encrypt cert