A14

14-amaliy mashg‘ulot · 14-mavzu · 2 soat · Korxona ilovalarini dasturlash

Docker stek, GitHub Actions va VPS ga joylashtirish

Jamoa loyihasi (OmborPro) bosqichi, 5 ta amaliy PHP topshiriq va 3 ta ma’ruzadagi mashq. Yo‘riqnoma bo‘yicha loyihada ishlang, havolani topshiring va PHP topshiriqlarni yeching — server yashirin testlar bilan tekshiradi, o‘qituvchi baho qo‘yadi.

Mashg‘ulot maqsadi

  • Yig‘ish — OmborPro uchun production image lar (app va web) va to‘liq Compose stekini: web, app, worker, scheduler, db, redis
  • Avtomatlashtirish — GitHub Actions quvurini: Pint, Larastan, Pest (PostgreSQL bilan), image ni GHCR ga yuklash va deploy
  • Joylashtirish — ilovani VPS serverga: SSH kalit, ufw, Docker, maxfiy .env, migratsiya va keshlar
  • Himoyalash — HTTPS ni yoqish, db va redis portlarini yopish, maxfiy qiymatlarni Secrets da saqlash
  • Tekshirish — ommaviy URL ishlashini (/up, kirish, buyurtma yaratish) hamda zaxira va tiklashni

1. 1-qadam: production Docker Compose stek

assets va web image · entrypoint · scheduler va worker · lokal sinov

Ma’ruzadagi Dockerfile ni loyihangizga qo‘shing va uni ikki yo‘nalishda to‘ldiring. Birinchidan, Blade sahifalari Vite yig‘gan CSS/JS dan foydalanadi: node:20-alpine bosqichida npm ci && npm run build bajarilib, public/build papkasi hosil bo‘ladi. Bu papka ikki joyga kerak: nginx image iga (fayllarni berish uchun) va app image iga (@vite direktivasi public/build/manifest.json ni PHP tomonda o‘qiydi). Ikkinchidan, nginx uchun alohida web bosqichi yoziladi: FROM nginx:1.27-alpine, nginx.conf va public/ nusxasi. Natijada ikkita image: omborpro (php-fpm) va omborpro-web (nginx). .dockerignore faylini albatta yarating.

docker/entrypoint.sh skripti har bir konteyner ishga tushganda php artisan optimize ni bajaradi — keshlar shu muhitning haqiqiy o‘zgaruvchilari bilan yaratiladi (build paytida .env yo‘q!). Keyin exec "$@" asosiy buyruqni ishga tushiradi: app uchun php-fpm, worker uchun queue:work, scheduler uchun schedule:work. docker/php.ini da OPcache yoqiladi va opcache.validate_timestamps=0 qo‘yiladi. Dockerfile ga ENTRYPOINT qo‘shsangiz, CMD ["php-fpm"] ni ham qayta yozing — ENTRYPOINT asos image dagi CMD ni bekor qiladi.

compose.yaml ni ma’ruzadagi ikki qism asosida yig‘ing va scheduler servisini qo‘shing (10-mavzudagi kam qoldiq bildirishnomasi rejalashtirilgan vazifa sifatida shu yerda ishlaydi). worker ga stop_grace_period: 60s bering — Docker konteynerni to‘xtatishda avval SIGTERM yuboradi, queue:work joriy vazifani tugatadi (pcntl kerak), belgilangan vaqtdan keyin esa SIGKILL keladi. Hech bir servisda db va redis uchun ports bo‘lmasin. Lokal kompyuterda docker compose build, docker compose up -d, docker compose ps bilan barcha servislar running / healthy ekanini tekshiring, so‘ng docker compose exec app php artisan migrate --force va db:seed bilan sinov ma’lumotlarini yuklang.

Oxirida stekni “production ko‘zi” bilan tekshiring: http://localhost/up 200 qaytaradimi; http://localhost/.env 403 beradimi; docker compose exec app php artisan about da Environment — production, Debug Mode — OFF; docker compose restart worker dan keyin navbat vazifasi yo‘qolmadimi; docker compose down va up -d dan keyin ma’lumotlar saqlanib qoldimi (volume). Topilgan muammolarni jamoaning README faylidagi “Deploy” bo‘limiga yozing.

DOCKERFILE · ASSETS VA WEB

Vite fayllari va nginx image

FROM node:20-alpine AS assets
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci
COPY . .
RUN npm run build                  # -> public/build

FROM nginx:1.27-alpine AS web
COPY docker/nginx.conf /etc/nginx/conf.d/default.conf
COPY --from=assets /app/public /var/www/public

# app bosqichiga (ma’ruzadagi Dockerfile) qo‘shing:
# COPY --from=assets /app/public/build /var/www/public/build
# COPY --chmod=755 docker/entrypoint.sh /usr/local/bin/entrypoint
# ENTRYPOINT ["entrypoint"]
# CMD ["php-fpm"]
▶ Natija
$ docker build --target web -t ghcr.io/jamoa/omborpro-web:dev .
$ docker build -t ghcr.io/jamoa/omborpro:dev .
$ docker images | grep omborpro
ghcr.io/jamoa/omborpro-web   dev   52MB
ghcr.io/jamoa/omborpro       dev   151MB
  • AS assets — Node faqat build uchun; yakuniy image larga kirmaydi
  • --target web — bitta Dockerfile dan nginx image ini yig‘ish
  • public/build ikki joyda — nginx fayllarni beradi, Laravel manifest.json ni o‘qiydi
  • CMD qayta yoziladi — ENTRYPOINT asos image ning CMD ini bekor qiladi
ENTRYPOINT VA PHP.INI

Konteyner ishga tushganda keshlar

#!/bin/sh
# docker/entrypoint.sh — app, worker, scheduler uchun umumiy
set -e
if [ "$APP_ENV" = "production" ]; then
    php artisan optimize      # config, event, route, view keshlari
fi
exec "$@"                     # php-fpm | queue:work | schedule:work

# docker/php.ini
# opcache.enable=1
# opcache.validate_timestamps=0
# opcache.memory_consumption=128
# memory_limit=256M
# upload_max_filesize=20M
# post_max_size=20M
▶ Natija
$ docker compose logs app | head -3
   INFO  Caching framework bootstrap, configuration, and metadata.
  config ........................................ DONE
  routes ........................................ DONE
  • optimize ishga tushishda — keshlar serverdagi haqiqiy .env qiymatlari bilan yaratiladi
  • exec "$@" — asosiy jarayon PID 1 bo‘ladi va signallarni to‘g‘ri oladi
  • validate_timestamps=0 — konteyner ichida kod o‘zgarmaydi — tekshiruv keraksiz
  • upload_max_filesize — nginx dagi client_max_body_size bilan mos bo‘lsin
COMPOSE · QO‘SHIMCHA

scheduler va worker ning production sozlamalari

  worker:
    <<: *app
    command: php artisan queue:work redis --tries=3 --max-time=3600
    stop_grace_period: 60s
  scheduler:
    <<: *app
    command: php artisan schedule:work
  caddy:
    image: caddy:2-alpine
    ports: ["80:80", "443:443"]
    volumes:
      - ./docker/Caddyfile:/etc/caddy/Caddyfile:ro
      - caddy_data:/data
    depends_on: [web]
    restart: unless-stopped
# web servisidan `ports` olib tashlanadi: tashqariga faqat caddy
# volumes ga qo‘shing: caddy_data: {}
▶ Natija
$ docker compose ps --format "table {{.Service}}\t{{.Status}}"
SERVICE     STATUS
app         Up 2 minutes
caddy       Up 2 minutes
db          Up 2 minutes (healthy)
scheduler   Up 2 minutes
worker      Up 2 minutes
  • stop_grace_period — worker joriy vazifani tugatishiga vaqt
  • schedule:work — har daqiqada routes/console.php dagi vazifalarni tekshiradi
  • caddy — HTTPS: Let’s Encrypt sertifikatini avtomatik oladi va yangilaydi
  • caddy_data — sertifikatlar volume da — qayta ishga tushganda yo‘qolmaydi
Scheduler faqat bitta nusxada ishlashi kerak — aks holda har bir vazifa ikki marta bajariladi.

2. 2-qadam: GitHub Actions quvuri va deploy job

ci.yml · Secrets · branch protection · teg orqali reliz

.github/workflows/ci.yml ga ma’ruzadagi lint, test va build joblarini qo‘shing. build ikkita image yig‘sin: omborpro (sukut bo‘yicha oxirgi bosqich) va omborpro-web (target: web). Teglar: commit SHA va v* teglarida semver versiya — buni docker/metadata-action@v5 (type=semver,pattern={{version}}) yoki amaliy topshiriqdagi teg funksiyasi mantiqi bilan yasang. Birinchi push dan keyin Actions sahifasida uchala job yashil ekanini va Packages bo‘limida image paydo bo‘lganini tekshiring. Paket xususiy (private) bo‘lsa, serverda docker login ghcr.io uchun read:packages huquqli token kerak bo‘ladi.

Repozitoriy sozlamalarida (Settings → Secrets and variables → Actions) maxfiy qiymatlarni yarating: DEPLOY_HOST (server IP yoki domen), DEPLOY_SSH_KEY (faqat deploy uchun yaratilgan ed25519 kalitning yopiq qismi) va kerak bo‘lsa DEPLOY_KNOWN_HOSTS. Yopiq kalitni hech qachon repozitoriyga, Telegram yoki e-mail ga yubormang. Production uchun GitHub Environment (production) yaratib, deploy ni jamoa yetakchisining tasdig‘iga bog‘lash mumkin — bu Continuous Delivery.

main tarmog‘i uchun branch protection yoqing: PR orqali birlashtirish, kamida bitta tasdiq (review) va lint, test joblari majburiy. Reliz jarayoni: main dagi yashil commit ga git tag v1.0.0 && git push --tags → build image ni 1.0.0 tegi bilan yuklaydi → deploy job SSH orqali serverdagi deploy.sh 1.0.0 ni chaqiradi. Shunday qilib, production dagi har bir versiya git tegi, image tegi va CHANGELOG yozuvi bilan bir-biriga bog‘langan bo‘ladi — muammo chiqsa, oldingi teg bilan deploy.sh 0.9.0 orqali tez qaytish mumkin.

DEPLOY JOB

Teg push qilinganda serverga chiqarish

  deploy:
    needs: [build]
    if: startsWith(github.ref, 'refs/tags/v')
    runs-on: ubuntu-latest
    environment: production
    steps:
      - name: SSH orqali deploy
        env:
          KEY: ${{ secrets.DEPLOY_SSH_KEY }}
          HOST: ${{ secrets.DEPLOY_HOST }}
          KNOWN: ${{ secrets.DEPLOY_KNOWN_HOSTS }}
        run: |
          mkdir -p ~/.ssh && chmod 700 ~/.ssh
          echo "$KEY" > ~/.ssh/id_ed25519 && chmod 600 ~/.ssh/id_ed25519
          echo "$KNOWN" > ~/.ssh/known_hosts
          ssh deploy@"$HOST" \
            "/opt/omborpro/deploy.sh ${GITHUB_REF_NAME#v}"  # 1.0.0
▶ Natija
deploy  ✓ SSH orqali deploy
  ✔ Container omborpro-app-1     Recreated
  ✔ Container omborpro-worker-1  Recreated
  Deploy 1.0.0: OK
  • if: refs/tags/v — faqat v1.0.0 kabi teglarda ishlaydi
  • environment: production — GitHub da tasdiq va alohida secret lar uchun
  • known_hosts — server kaliti oldindan ma’lum — MITM hujumidan himoya
  • ${GITHUB_REF_NAME#v} — v1.0.0 → 1.0.0: image tegi
SECRETS

Quvur uchun kerakli maxfiy qiymatlar

NomiQayerda ishlatiladiQanday olinadi
GITHUB_TOKENGHCR ga login (build)GitHub avtomatik beradi
DEPLOY_HOSTSSH manziliVPS IP yoki omborpro.example.uz
DEPLOY_SSH_KEYServerga kirishssh-keygen -t ed25519 -f deploy_key
DEPLOY_KNOWN_HOSTSServer kalitini tekshirishssh-keyscan -H <host> (bir marta, tekshirib)
Server .envLaravel sozlamalariFaqat serverda, chmod 600 — GitHub da emas
Ochiq kalit (deploy_key.pub) serverdagi ~deploy/.ssh/authorized_keys ga qo‘shiladi.
RELIZ OQIMI

Kod o‘zgarishidan production gacha

  1. Feature tarmoq → PR — lint va test avtomatik ishlaydi; kamida bitta review
  2. main ga merge — build: image sha tegi bilan GHCR ga
  3. git tag v1.0.0 — build: image 1.0.0 tegi bilan
  4. deploy job — SSH → deploy.sh 1.0.0 → zaxira, migratsiya, up -d
  5. Tutun testi — /up = 200; muammo bo‘lsa deploy.sh 0.9.0 bilan qaytish
Ma’lumotlar bazasi orqaga qaytmaydi — shuning uchun migratsiyalar orqaga mos (expand/contract) bo‘lishi shart.

3. 3-qadam: VPS ga joylashtirish va ommaviy URL

Server tayyorlash · ufw · Docker · HTTPS · tutun testi · topshirish

O‘qituvchi bergan (yoki jamoa ijaraga olgan) Ubuntu 22.04/24.04 VPS ga root sifatida bir marta kiring va serverni tayyorlang: tizimni yangilang, deploy foydalanuvchisini yarating va unga SSH kalit bilan kirishni sozlang, so‘ng parol bilan kirishni (PasswordAuthentication no) va root sifatida kirishni o‘chiring. Docker ni rasmiy o‘rnatish skripti yoki rasmiy apt repozitoriysi orqali o‘rnating va deploy ni docker guruhiga qo‘shing (bu guruh root ga teng huquq beradi — boshqa foydalanuvchini qo‘shmang).

Tarmoq himoyasi: ufw da faqat 22 (SSH), 80 va 443 portlarga ruxsat bering. Esda tuting: Docker ports bilan ochgan portlar ufw ni chetlab o‘tadi, shuning uchun himoyaning asosiy qatlami — compose.yaml da db va redis uchun port ochmaslik. /opt/omborpro papkasiga compose.yaml, deploy.sh, backup.sh, docker/Caddyfile va .env ni joylashtiring (.env faqat shu yerda, chmod 600). APP_KEY ni docker compose run --rm app php artisan key:generate --show bilan yarating va .env ga yozing.

HTTPS uchun domen kerak (masalan, o‘qituvchi bergan jamoa1.omborpro.example.uz subdomeni, DNS A yozuvi server IP siga qaratilgan). Eng sodda yo‘l — stek oldiga Caddy qo‘yish: Caddyfile da jamoa1.omborpro.example.uz { reverse_proxy web:80 } yozilsa, Caddy Let’s Encrypt sertifikatini o‘zi oladi va yangilaydi. Muqobil yo‘l — host dagi nginx + certbot. Domen bo‘lmasa, o‘qituvchi bilan kelishgan holda vaqtincha HTTP va IP manzil orqali topshiriladi, lekin SESSION_SECURE_COOKIE ni faqat HTTPS bo‘lganda yoqing.

Birinchi deploy: TAG=1.0.0 ./deploy.sh 1.0.0, keyin seed (docker compose exec app php artisan db:seed --force) bilan demo foydalanuvchilarni yarating — real parol emas, faqat test qiymatlar. Tutun testlarini bajaring va natijani README ga yozing. crontab ga backup.sh ni qo‘shing va bir marta qo‘lda ishga tushirib, dump faylini test bazaga tiklab ko‘ring. Oxirida ommaviy URL, reliz tegi va CI ishga tushirish havolasini topshirish shakliga kiriting.

SERVER TAYYORLASH

Ubuntu VPS: foydalanuvchi, ufw, Docker

# root sifatida, bir marta
apt update && apt -y upgrade
adduser --disabled-password --gecos "" deploy
mkdir -p /home/deploy/.ssh
cp ~/.ssh/authorized_keys /home/deploy/.ssh/
chown -R deploy:deploy /home/deploy/.ssh

ufw allow OpenSSH
ufw allow 80/tcp && ufw allow 443/tcp
ufw enable

curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh                  # rasmiy o‘rnatish skripti
usermod -aG docker deploy
mkdir -p /opt/omborpro/backups && chown -R deploy /opt/omborpro
# /etc/ssh/sshd_config: PasswordAuthentication no, PermitRootLogin no
▶ Natija
$ ufw status
Status: active
To                         Action      From
OpenSSH                    ALLOW       Anywhere
80/tcp                     ALLOW       Anywhere
443/tcp                    ALLOW       Anywhere
  • deploy foydalanuvchi — root emas; faqat SSH kalit bilan kiradi
  • ufw — faqat 22, 80, 443 — qolgani yopiq
  • docker guruhi — root ga teng huquq — faqat deploy foydalanuvchisiga
  • sshd_config — parol va root kirishini o‘chirish — brute-force dan himoya
sshd_config ni o‘zgartirishdan oldin yangi oynada deploy bilan kira olishingizni tekshiring — aks holda serverdan qulflanib qolasiz.
HTTPS

Sertifikat olishning ikki yo‘li

Caddy (stek ichida)
  • Caddyfile: domen { reverse_proxy web:80 }
  • Let’s Encrypt sertifikatini avtomatik oladi va yangilaydi
  • Tashqariga faqat Caddy ning 80/443 portlari
  • Talaba loyihasi uchun eng sodda yo‘l
Host nginx + certbot
  • Server da alohida nginx teskari proksi
  • certbot --nginx -d domen bilan sertifikat
  • Yangilash — certbot taymeri
  • Bir serverda bir nechta loyiha bo‘lsa qulay
Ikkala holatda ham DNS A yozuvi server IP siga qaratilgan bo‘lishi va 80-port ochiq bo‘lishi kerak (HTTP-01 tekshiruvi).
TUTUN TESTI

Deploydan keyin 5 daqiqalik tekshiruv

TekshiruvBuyruq / harakatKutilgan natija
Health endpointcurl -i https://domen/upHTTP/2 200
Yashirin fayllarcurl -i https://domen/.env403 yoki 404
KirishDemo menejer bilan loginBosh sahifa ochiladi
Buyurtma oqimiBuyurtma yaratish → tasdiqlashQoldiq rezervlanadi
NavbatHisobotni so‘rashWorker logida job DONE
PortlarBoshqa kompyuterdan nc -zv IP 5432Ulanish rad etiladi
Zaxira./backup.sh → test bazaga tiklashYozuvlar soni mos

Loyiha bosqichi: natija va topshirish

Natija: OmborPro to‘liq Docker Compose stekida (web, app, worker, scheduler, db, redis) VPS serverda ommaviy URL orqali ishlaydi; har bir v* teg GitHub Actions da lint, test va build dan o‘tib, avtomatik joylashtiriladi.

Baholash mezonlari
  • Dockerfile multi-stage: composer --no-dev, pdo_pgsql, redis, opcache, pcntl; USER www-data; .dockerignore mavjud
  • compose.yaml da web, app, worker, scheduler, db, redis; db uchun healthcheck va service_healthy; db/redis portlari ochilmagan
  • nginx konfiguratsiyasi: root /var/www/public, try_files, fastcgi_pass app:9000, yashirin fayllar uchun deny all
  • GitHub Actions: lint (Pint --test, Larastan), test (Pest + PostgreSQL servis), build (GHCR) — oxirgi ishga tushirish yashil
  • Teg orqali deploy ishlaydi: deploy.sh da zaxira, migrate --force, up -d, queue:restart, tutun testi
  • Production .env: APP_ENV=production, APP_DEBUG=false, APP_KEY o‘rnatilgan; .env git da yo‘q
  • Ommaviy URL ochiladi (HTTPS yoki kelishilgan HTTP), /up 200 qaytaradi, /.env ochilmaydi
  • backup.sh cron da; README da tiklash mashqi natijasi va tutun testi jadvali yozilgan

📤 GitHub repozitoriy havolasi, reliz tegi (masalan v1.0.0) va shu teg uchun yashil GitHub Actions ishga tushirish havolasi hamda ommaviy URL ni topshiring; README da deploy bo‘limi, tutun testi jadvali va demo foydalanuvchi (test parol) ko‘rsatilsin.

?

Qanday ishlaydi. Chapdan topshiriqni tanlang, shartni o‘qing va shartdagi imzo bo‘yicha sof PHP funksiya yoki sinf yozing (Laravelsiz). ▶ Sinab ko‘rish — pastdagi chaqiruv ifodasini kodingiz bilan bajaradi (baholanmaydi). ✓ Topshirish — server kodni namunaviy va yashirin testlar bilan tekshiradi; natija o‘qituvchiga ko‘rinadi.

Yechildi 0 / 8
Ball 0

💡 Maslahat

PHP 8.3 kodi · avtomatik saqlanadi