Vaibhav Srivastava

Building RushDeploy: git push to live containers, no Dockerfile needed 🚀 | Full-stack dev, Shipping with AI agents | Noida

[Vaibhav Srivastava @vsrihq]

Shipping a side project shouldn't mean an evening of SSH, Nginx and Dockerfiles.

With RushDeploy you:
• connect a GitHub repo
• git push
• get a live URL with SSL

One-click Postgres/Redis and instant rollbacks included.

https://t.co/amjzeXUZRV

[Vaibhav Srivastava @vsrihq]

Deploy tip: read your port from the PORT env var instead of hardcoding 3000.

A hardcoded port is a common reason a container builds fine but never answers requests.

On RushDeploy you can skip the Dockerfile too: push your repo, get a live URL with SSL.

https://t.co/amjzeXUZRV

[Vaibhav Srivastava @vsrihq]

@shivam74689 Exactly. A green status just means it booted, and real traffic plus logs tell you it works. Keep the streak going, see you on Day 143 🙌

[Vaibhav Srivastava @vsrihq]

7/ If you're tired of babysitting servers, try it: https://t.co/amjzeXUs2n

Building in public from here, so follow along 🙌

[Vaibhav Srivastava @vsrihq]

I built RushDeploy, a deployment platform, almost entirely with AI agents. Here's what that was actually like, what worked and what didn't 🧵

[Vaibhav Srivastava @vsrihq]

6/ Biggest lesson: AI writes code fast, but you still own the architecture and the edge cases. Review everything that touches data.

[Vaibhav Srivastava @vsrihq]

@arvidkahl One major version at a time is the key part. Having the agent read the official migration guide first and run the test suite after each hop catches most surprises before they stack up.

[Vaibhav Srivastava @vsrihq]

@rauchg Surviving restarts and redeploys is the part most agent demos skip. Curious how in-flight tool calls are handled: replay from the last checkpoint, or does it expect tools to be idempotent?

[Vaibhav Srivastava @vsrihq]

@stresixcom Great data. People throw more vCPUs at it and wonder why nothing changes. One next start per core behind a reverse proxy (or separate containers) is the usual fix. Did memory become the limit once you scaled out?

[Vaibhav Srivastava @vsrihq]

@fullstacklover Agree. Even if you end up on a PaaS, doing it once by hand (SSH, systemd, Nginx, certs, firewall) makes every outage less scary because you know what's actually underneath.

[Vaibhav Srivastava @vsrihq]

@makyslab Too real 😅 The stuff that saves weekends: health checks with auto-restart, uptime alerts on your phone, and keeping the last good build one click away so a bad deploy is a rollback, not a rebuild.

[Vaibhav Srivastava @vsrihq]

@devgenix If you want everything in one place, I built RushDeploy for this: connect the GitHub repo, git push, and your Next.js app runs in a container with SSL. Postgres/Redis are one click if you need a backend too. Happy to help you move over: https://t.co/amjzeXUs2n

[Vaibhav Srivastava @vsrihq]

Build-in-public note: someone asked if RushDeploy's rollback also reverts a Postgres migration.

Honest answer: no. Rollback restores the previous app image. Committed migrations stay put, so keep them backward-compatible.

Next up: making that difference clear in the UI.

[Vaibhav Srivastava @vsrihq]

@satvikpathak007 Great question. Right now rollback restores the previous app image only. It doesn't reverse a migration that's already committed, so migrations should stay backward-compatible. Making that distinction explicit in the UI is a great idea, and I'm adding it to the roadmap 🙏

[Vaibhav Srivastava @vsrihq]

Shipping a side project shouldn't mean an evening of SSH, Nginx and Dockerfiles.

With RushDeploy you:
• connect a GitHub repo
• git push
• get a live URL with SSL

One-click Postgres/Redis and instant rollbacks included.

https://t.co/amjzeXUZRV

[Vaibhav Srivastava @vsrihq]

@SandeepMiriyala Nice approach keeping projects lightweight. If the Python side ever outgrows serverless limits, container hosting helps. RushDeploy runs Next.js and FastAPI side by side from one git push: https://t.co/amjzeXUZRV

[Vaibhav Srivastava @vsrihq]

@KrishChhabra25 @WeMakeDevs @falkordb @Docker @awscloud All the best for Graph Hacks! 🚀 What stack are you deploying?