The latest articles on DEV Community by Siddharth (@siddharth123). https://dev.to/siddharth123 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3672936%2Fc7de6c05-2bfa-4b09-bbaa-cd5e37b1c8f9.webp https://dev.to/siddharth123 en Siddharth Sun, 26 Apr 2026 18:05:23 +0000 https://dev.to/siddharth123/i-published-my-puzzle-game-tubetidy-on-google-play-fan https://dev.to/siddharth123/i-published-my-puzzle-game-tubetidy-on-google-play-fan <h1> I Published My Puzzle Game TubeTidy on Google Play </h1> <p>I’ve just launched <strong>TubeTidy</strong>, a ball sort puzzle game, on Google Play.</p> <p>This project was more than just building a game screen. It involved the complete publishing workflow:</p> <ul> <li>preparing the Android app bundle</li> <li>Play Console setup</li> <li>package verification</li> <li>store listing creation</li> <li>screenshots and graphics</li> <li>content declarations</li> <li>production rollout</li> <li>ad and monetization planning</li> </ul> <h2> About the game </h2> <p>TubeTidy is a mobile puzzle game where players sort colorful balls into matching tubes. The gameplay is simple to understand but becomes more strategic as levels progress.</p> <p>The current release includes:</p> <ul> <li>core ball sort puzzle gameplay</li> <li>daily rewards</li> <li>stats and achievements</li> <li>themes</li> <li>in-game shop</li> <li>rewarded ad flow</li> <li>polished neon-dark UI style</li> </ul> <h2> Launch link </h2> <p>You can try it here:</p> <p><a href="https://play.google.com/store/apps/details?id=com.pixelinnovations.tubetidypuzzle" rel="noopener noreferrer">https://play.google.com/store/apps/details?id=com.pixelinnovations.tubetidypuzzle</a></p> <h2> What I learned from publishing </h2> <p>One thing that stands out is that building the app is only part of the work. Publishing requires careful handling of:</p> <ul> <li>signing keys</li> <li>package verification</li> <li>app content declarations</li> <li>privacy policy setup</li> <li>store listing assets</li> <li>release review process</li> </ul> <h2> Next updates </h2> <p>The next version will focus on:</p> <ul> <li>stronger monetization flow</li> <li>improved tube sizing and gameplay visuals</li> <li>more polish across the overall player experience</li> </ul> <p>If you’re into Android publishing, indie app launches, or puzzle games, feel free to check it out and share feedback.</p> puzzle gamechallenge android gamedev Siddharth Sun, 21 Dec 2025 18:32:21 +0000 https://dev.to/siddharth123/how-i-run-automation-24x7-on-a-500-vps-exact-setup-444o https://dev.to/siddharth123/how-i-run-automation-24x7-on-a-500-vps-exact-setup-444o <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9s6van2heok56f5wwa06.jpg" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9s6van2heok56f5wwa06.jpg" alt=" " width="800" height="569"></a>Running automation continuously—without relying on a personal computer—requires the right infrastructure. After testing local machines and shared hosting, I settled on a simple VPS-based setup that runs 24×7 with minimal cost and maintenance.</p> <p>Why Local Machines and Shared Hosting Failed</p> <p>Local systems are unreliable for automation because they:</p> <p>Shut down or sleep</p> <p>Depend on unstable internet</p> <p>Cannot scale</p> <p>Shared hosting is designed for websites, not automation:</p> <p>No long-running processes</p> <p>Restricted cron jobs</p> <p>No Docker or custom services</p> <p>What Actually Works for Automation</p> <p>For most automation workloads, you don’t need expensive servers. You need:</p> <p>Root access</p> <p>Background process support</p> <p>Predictable performance</p> <p>A small VPS with 1 vCPU and 2 GB RAM is sufficient.</p> <p>The VPS Setup I Use</p> <p>I currently run my automation workloads on a low-cost VPS that provides:</p> <p>Full SSH access</p> <p>Stable performance</p> <p>Predictable monthly pricing</p> <p>This setup allows me to run scripts, schedulers, and lightweight backend services reliably.</p> <p>Full details are explained here (canonical article):<br> 👉 <a href="https://medium.com/@businesswebsites100/how-i-run-automation-24-7-on-a-500-vps-exact-setup-90e878e4e746" rel="noopener noreferrer">https://medium.com/@businesswebsites100/how-i-run-automation-24-7-on-a-500-vps-exact-setup-90e878e4e746</a></p> <p>Real Usage Example</p> <p>I also run a live file utility platform (pdfio.in) that depends on background processing and scheduled server-side tasks—something shared hosting cannot handle reliably.</p> <p>Final Thought</p> <p>If you need automation that runs continuously without manual intervention, a VPS is the correct tool—not shared hosting or local machines.</p> automation vps devops linux