The latest articles on DEV Community by vineel vanjari (@vineelvanjari). https://dev.to/vineelvanjari https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3785671%2Fc3c0477e-2d19-46bb-b001-8e047e984679.jpg https://dev.to/vineelvanjari en vineel vanjari Tue, 24 Feb 2026 02:15:46 +0000 https://dev.to/vineelvanjari/automating-flutter-web-deployment-to-render-using-branch-strategy-4lhe https://dev.to/vineelvanjari/automating-flutter-web-deployment-to-render-using-branch-strategy-4lhe <p>When deploying my Flutter Web app 🌐 to Render, I initially followed a manual process — build locally 💻, copy the build/web folder 📁 into another repo, and push to deploy. It worked, but it wasn’t scalable. I simplified everything using a single repository with two branches 🌿: master for development and production for deployment. Render watches production and runs a build.sh script ⚙️ to build automatically. I also added an SPA rewrite rule 🔁 to fix routing. Now deployment is simple, clean, and fully automated 🚀.</p> <p>Full guide:<br> <a href="https://vineelvanjari.com/blogs/flutter/flutter-render-deployment-guide" rel="noopener noreferrer">https://vineelvanjari.com/blogs/flutter/flutter-render-deployment-guide</a></p> render devops webdev flutter vineel vanjari Mon, 23 Feb 2026 05:50:11 +0000 https://dev.to/vineelvanjari/sync-a-private-repo-subfolder-to-a-public-repo-using-github-actions-5784 https://dev.to/vineelvanjari/sync-a-private-repo-subfolder-to-a-public-repo-using-github-actions-5784 <p>While building my website 🌐, I ran into an architecture constraint 🧠.</p> <p>My entire repository needed to stay private 🔒 because it contains drafts and internal structure. However, one folder (/website) powers the basic version of my blog and had to be public 🌍.</p> <p>I didn’t want:</p> <p>Duplicate repositories 📂</p> <p>Manual copying ❌</p> <p>Risk of exposing private files 🚫</p> <p>Inconsistent content between repos 🔁</p> <p>⚙️ The Solution</p> <p>I implemented a GitHub Actions workflow 🤖 inside the private repository that:</p> <p>Triggers only on website/** changes 📁</p> <p>Uses a Personal Access Token (PAT) stored as a secret 🔑</p> <p>Clones the public repository 🌐</p> <p>Syncs using rsync --delete 🪞</p> <p>Commits and pushes automatically 🚀</p> <p>The --delete flag ensures removed files are also mirrored, keeping both repositories perfectly in sync 🔄.</p> <p>🏗️ Final Setup</p> <p>Private repo → Full development workspace 🧑‍💻<br> Public repo → Clean blog content layer 📦<br> Publishing → Fully automated pipeline ⚡</p> <p>This approach keeps a single source of truth 📌 while maintaining proper separation of concerns 🧩.</p> <p>If you're facing similar repo separation challenges, this pattern works cleanly and reliably.</p> <p>Full step-by-step guide 🔗<br> <a href="https://vineelvanjari.com/blog/sync-private-repo-subfolder-to-public-repo-using-github-actions" rel="noopener noreferrer">https://vineelvanjari.com/blog/sync-private-repo-subfolder-to-public-repo-using-github-actions</a></p> webdev automation devops github