GCP Deployment & CI/CD Setup
Budget: $30 – $250 USD
My Node-JS + React (TypeScript) platform is ready to leave the testing nest and I now need a clean, worry-free deployment on Google Cloud Platform. The stack runs one backend server and three front-end “faces”, each destined for its own sub-domain of torly.app:
• ov.torly.app — Admin panel
• cp.torly.app — Owner/business dashboard
• torly.app — Client booking site
Tel-Aviv (or the closest Israel region) is ideal for latency, but I still want enough headroom to scale smoothly when traffic spikes. What matters most to me is a straightforward, low-maintenance setup: push to “test”, push to “live”, and it just works.
Here’s what I’m looking for you to do:
1. Evaluate the GCP options (App Engine, Cloud Run, GKE, Compute Engine—whichever best hits the sweet spot of simplicity and future growth).
2. Draft a brief architecture plan covering DNS, SSL, environment variables and automatic rollbacks.
3. Spin up the resources in my GCP project, connect the torly.app DNS records, and set up staging vs. production.
4. Configure a basic CI/CD pipeline (GitHub Actions is fine) so I can deploy to either environment with a single push.
5. Hand over clear instructions and cost estimates so I’m never surprised at month-end.
If you can get all that running without over-engineering, we’ll be a perfect match.
Some important data:
Repo(s) structure
Mono repo.
How you handle env vars today
Currently env vars are hardcoded
DB type? where it will live?
MySQL, depends on needs, can defenitly be on GCP as well if thats an option, need to evaluate costs.
Need staging env? (recommended)
I'd love that! need it if I want to be serious.
Target cloud
Whether its GCP, AWS, as long as I get easy to use CI CD i don't mind
CI/CD required (yes/no)
Yes, please!
• ov.torly.app — Admin panel
• cp.torly.app — Owner/business dashboard
• torly.app — Client booking site
Tel-Aviv (or the closest Israel region) is ideal for latency, but I still want enough headroom to scale smoothly when traffic spikes. What matters most to me is a straightforward, low-maintenance setup: push to “test”, push to “live”, and it just works.
Here’s what I’m looking for you to do:
1. Evaluate the GCP options (App Engine, Cloud Run, GKE, Compute Engine—whichever best hits the sweet spot of simplicity and future growth).
2. Draft a brief architecture plan covering DNS, SSL, environment variables and automatic rollbacks.
3. Spin up the resources in my GCP project, connect the torly.app DNS records, and set up staging vs. production.
4. Configure a basic CI/CD pipeline (GitHub Actions is fine) so I can deploy to either environment with a single push.
5. Hand over clear instructions and cost estimates so I’m never surprised at month-end.
If you can get all that running without over-engineering, we’ll be a perfect match.
Some important data:
Repo(s) structure
Mono repo.
How you handle env vars today
Currently env vars are hardcoded
DB type? where it will live?
MySQL, depends on needs, can defenitly be on GCP as well if thats an option, need to evaluate costs.
Need staging env? (recommended)
I'd love that! need it if I want to be serious.
Target cloud
Whether its GCP, AWS, as long as I get easy to use CI CD i don't mind
CI/CD required (yes/no)
Yes, please!
Related categories:
Linux
DNS
MySQL
Node.js
Backend Development
Google Cloud Platform
Continuous Integration
DevOps
SSL
CI/CD