🟢 #1 Add deployment configs and DEPLOYMENT.md so the repo can be launched as a website +719 2mo ago self by
cphlabspace ↗ analysis ↗ GitHub <!-- CURSOR_AGENT_PR_BODY_BEGIN -->
cphlabspace/mikeOSS
Deployment infrastructure: Dockerfiles, Wrangler config, CI, and a multi-host guide
cphlabspace/mikeOSS has one recorded topic: filling in the deployment gap between a working local dev setup and an actual hosted site. The work adds Dockerfiles for the backend and frontend, a root-level Docker Compose file, a Cloudflare Wrangler config (without which npm run deploy was broken), a GitHub Actions CI workflow with parallel builds, and a deployment guide covering six hosting options.
No application code changes are present in the tracked history.
What's in it
- Deployable by default @cphlabspace is filling in the missing pieces so Mike can be hosted as a public site, not just run on a laptop.
- Hands off the product The application itself is left alone - this fork is about operations, not features.
Direction
infrastructure
Activity
📝 cphlabspace adds Dockerfiles, Wrangler config, and a deployment guide to fill the gap between local dev and a live site 0 commits — infrastructureworkflow draft
The repo already built locally, but `npm run deploy` was broken - the Wrangler config it depended on didn't exist. cphlabspace adds that config, Dockerfiles for both services, a root-level Compose file, and a GitHub Acti…
Threads of work (detailed view)
cphlabspace adds Dockerfiles, Wrangler config, and a deployment guide to fill the gap between local dev and a live site
The repo already built locally, but `npm run deploy` was broken - the Wrangler config it depended on didn't exist. cphlabspace adds that config, Dockerfiles for both services, a root-level Compose file, and a GitHub Actions CI workflow, along with a narrative deployment guide covering six host options.
Pull requests (detailed view)
🟢 Open (1)
by
cphlabspace · opened 2mo ago