---
title: "Discussion on \"Vibe Coding to Production\" | Hashnode"
description: "Discussion on \"Vibe Coding to Production\". Deploying a Gemini App with Cloud Run and GitHub"
url: "https://hashnode.com/posts/vibe-coding-to-production/69a5c924c25336d0790aaf8d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Vibe Coding to Production](https://blog.ankur.cc/vibe-coding-to-production?utm_source=hashnode&utm_medium=feed)

Deploying a Gemini App with Cloud Run and GitHub

Mar 2 · 4 min read · blog.ankur.cc  
Updated Mar 9  
Read the article

-   [#vibe-coding](https://hashnode.com/tag/vibe-coding)
-   [#cloud-run](https://hashnode.com/tag/cloud-run)
-   [#gemini-cli](https://hashnode.com/tag/gemini-cli)
-   [#cloud-build](https://hashnode.com/tag/cloud-build)

## Written by

[Ankur Kotwal](https://hashnode.com/@ankurkotwal)

@ankurkotwal

  
[View profile](https://hashnode.com/@ankurkotwal)

## Responses 1

Markdown supported · ⌘↵ to post

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 3](https://hashnode.com/posts/vibe-coding-to-production/69a5c924c25336d0790aaf8d/comment/6ac06b3b20b5422fcb752d83)

Vibe coding is fine for discovering the product shape. The failure mode starts when the same chat-driven edits become the release process: no branch protections, no tests on push, and no way to roll back when a prompt change breaks auth.

A practical bar is simple. One repo the company owns, a pipeline that runs your real checks on every PR, staging that mirrors production enough to catch config mistakes, and a deploy you can reverse without heroics. Until that exists, you still have a prototype with customers attached.

Ascendra Ventures often packages that first production chapter as a fixed-price atomic problem: CI/CD, secrets, and the boring reliability work that turns a demo into something you can put in front of paying users. The workflow in this post is the right starting map.
