CI/CD in a nutshell: how to set up an auto-deploy without pain in an evening

In the Kodika community We recently discussed how to quickly and easily roll out an auto-deploy. Without unnecessary magic and complex terms — here is a short guide that will help you implement CI/CD in just one evening. Even if you've only heard about it before 👀

🔧 What is CI/CD?

CI (Continuous Integration) — automatic build and testing of code at each commit.

CD (Continuous Delivery or Deployment) — automatic uploading of updates to the server after passing all checks.

Together they give you the opportunity to "pour" features immediately after the push - without dancing with a tambourine on the prod 🔥

📦 Minimum stack for auto-deploy

• 💻 GitHub (or GitLab, Bitbucket)

• 🛠️ CI/CD system: GitHub Actions / GitLab CI / Drone CI / Jenkins

• 📂 Server with SSH access (for example, Ubuntu VPS)

• ⚙️ Docker or Node/PM2 — as you like

🪄 How it works: step by step

1. You push the code to the repository

2. GitHub Actions (or other CI) is triggered

3. The code is being compiled, tests are being run

4. If everything is OK, the deployment to the server is performed

👨‍🍳 Example: Deploying a Node.js application with GitHub Actions

At the root of the project, create the .github/workflows/deploy.yml file:

name: 🚀 Deploy to Server

on:
  push:
    branches:
      - main

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repo
        uses: actions/checkout@v3

      - name: Install dependencies
        run: npm ci

      - name: Run tests
        run: npm test

      - name: Deploy via SSH
        uses: appleboy/ssh-action@v1
        with:
          host: ${{ secrets.HOST }}
          username: ${{ secrets.USERNAME }}
          key: ${{ secrets.SSH_KEY }}
          script: |
            cd ~/app-folder
            git pull origin main
            npm ci
            pm2 restart app

🔐 All secrets (SSH key, login, IP) are added through GitHub Secrets — it's safer.

⚡ What will be the result?

Every time you push the code, it automatically:

• is going to

• testing

• rolls out to the server

And all this - without a single manual action 🤯

📌 Tips from practitioners

• Set up a separate branch staging — for tests before uploading to main

• Add notifications to Telegram or Slack via Webhook

• Gradually expand the pipeline: liners, migrations, alerts

🧠 Conclusion

CI/CD is not about "too complicated". It's about "once you set it up, you forget about it." And most importantly, it's already an industry standard. If you want to be a sought-after developer, automation is your must-have.

🤖 Where to train?

In Kodik app you can not only learn Git and CI/CD, but also go through real projects with auto-deploy. Everything is interactive, step-by-step and with feedback 💬

And we also have Telegram community, where you can ask a question, discuss the pipeline and find a team for a pet project.

💬 Write in the comments if you want a guide on deploying Docker containers or setting up CI for Python. We'll discuss it and do it! 😉