Oliver

Hi Dev Hunt I'm on the product team at MAMP. serrv came out of a specific annoyance: you finish a static site and want to test it as it will actually be served, but your options don't quite get there. file:// breaks root-relative paths, fetch(), ES modules. localhost:PORT is closer, but it's not a secure context for every API, the port leaks into every URL, and Service Workers / camera / clipboard behave differently than under real HTTPS — Firefox especially doesn't treat plain localhost the same way Chrome does. serrv gives each site a real hostname (https://yoursite.local/) with a genuinely trusted certificate, so the lock shows up in every browser and secure-context APIs just work. Serving is Caddy, upload is rclone — the app's job is to make that zero-config on macOS. Everything runs at once at stable addresses, nothing lives in a terminal tab. To be upfront about limits: it's static files only, no PHP/DB. That's deliberate — for a dynamic stack we point people to MAMP PRO. serrv is scoped to one job: previewing static builds at production fidelity. Free for 3 sites; serrv max adds unlimited sites, FTP/SFTP, and an HTML check. Would especially love feedback from anyone testing Service Workers or PWAs locally — that's the case it was built for. What does your current local-HTTPS setup look like?