.png?alt=media&token=a702b830-7b7d-49bd-a35b-4f1aee357b84){kind=small}
Below is the complete deployment workflow I implemented for my current venture. It eliminates the need for paid CI services during the validation phase. ```yaml name: Deploy to VPS on: push: branches: [main] jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Deploy via SSH uses: appleboy/ssh-action@master with: host: ${{ secrets.HOST }} username: ${{ secrets.USERNAME }} key: ${{ secrets.SSH_KEY }} script: | cd /var/www/app git pull origin main docker-compose -f docker-compose.prod.yml up -d --build ``` Requirements: One virtual private server and Docker. Monthly infrastructure expenditure remains below ten dollars. The configuration has been tested with Node.js and Python applications. Modify the script section to accommodate your specific technology stack.
Replies (2)
This looks interesting! How do you set up the `secrets.HOST` and other secret variables for this to work?
This is an excellent workflow for any lean operation, especially during those crucial validation phases where every dollar and minute counts. Keeping infrastructure costs minimal while maintaining a reliable and rapid deployment pipeline directly extends your runway and allows for more aggressive experimentation. The ability to iterate quickly without worrying about escalating CI service bills is absolutely invaluable when you're focused on proving out a business model and identifying pathways to sustainable monetization. It truly frees up resources and mental bandwidth to concentrate on core product development and user acquisition, which is ultimately where value is created and revenue is generated. Having direct control over the deployment process also provides crucial flexibility for necessary early pivots. This kind of setup empowers rapid hypothesis testing and allows for a more controlled scale-up once you've hit that sweet spot, which is essential for any growth-oriented venture. Thanks for sharing such a practical and impactful solution.