Joriy etish va DevOps
OmborPro jamoa noutbugida mukammal ishlaydi. Ertadan 40 ta xodim undan internet orqali foydalanadi. Nima noto‘g‘ri ketishi mumkin?
Hozircha javob bermang — noutbuk va production server orasidagi farqlarni sanab chiqing.
Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
pdo_pgsql, redis, opcache, composer install --no-devroot public, try_files, fastcgi_pass app:9000APP_DEBUG=false, config:cache, optimize, queue:restartDocker: image, konteyner va Dockerfile
Image, konteyner, qatlam, registry
Image
ghcr.io/jamoa/omborpro:1.4.0.Konteyner
Qatlam (layer)
RUN / COPY natijasi; o‘zgarmagan qatlam keshdan olinadi.Registry
ghcr.io).Asosiy ko‘rsatmalar
| Ko‘rsatma | Vazifasi | OmborPro misoli |
|---|---|---|
FROM | Asos image (bosqich boshlanishi) | FROM php:8.2-fpm-alpine |
WORKDIR | Ishchi papka | WORKDIR /var/www |
COPY | Fayllarni image ga nusxalash | COPY composer.json composer.lock ./ |
RUN | Build paytida buyruq bajarish | RUN docker-php-ext-install pdo_pgsql |
USER | Kim nomidan ishlash | USER www-data |
CMD / ENTRYPOINT | Konteyner ishga tushganda bajariladigan buyruq | CMD ["php-fpm"] |
ENV va ARG ga parol yozmang — ular image tarixida (docker history) ko‘rinadi.OmborPro uchun production Dockerfile
# 1-bosqich: PHP bog‘liqliklari FROM composer:2 AS vendor WORKDIR /app COPY composer.json composer.lock ./ RUN composer install --no-dev --no-scripts --no-autoloader COPY . . RUN composer dump-autoload --optimize --no-dev --no-scripts # 2-bosqich: production image (php-fpm) FROM php:8.2-fpm-alpine RUN apk add --no-cache postgresql-dev $PHPIZE_DEPS \ && docker-php-ext-install pdo_pgsql opcache pcntl \ && pecl install redis && docker-php-ext-enable redis COPY docker/php.ini /usr/local/etc/php/conf.d/omborpro.ini WORKDIR /var/www COPY --from=vendor /app /var/www RUN chown -R www-data:www-data storage bootstrap/cache USER www-data
$ docker build -t ghcr.io/jamoa/omborpro:1.4.0 . => CACHED [vendor 4/6] RUN composer install --no-dev ... => [stage-1 6/7] COPY --from=vendor /app /var/www => naming to ghcr.io/jamoa/omborpro:1.4.0 done $ docker images ghcr.io/jamoa/omborpro ghcr.io/jamoa/omborpro 1.4.0 7c1e... 148MB
/app) olinadiCACHED)queue:work SIGTERM ni ushlab, joriy vazifani tugatishi uchunCMD ["php-fpm"] buyrug‘i meros qilib olinadi — qayta yozish shart emas.Ko‘rsatmalar tartibi build tezligini belgilaydi
Noto‘g‘ri: avval butun kod
COPY . .→RUN composer install- Bitta Blade fayl o‘zgarsa ham kesh buziladi
- Har build da 80+ paket qayta yuklanadi
.dockerignoreyo‘q —.envvavendorimage ga tushadi
To‘g‘ri: kam o‘zgaradigani yuqorida
COPY composer.json composer.lock ./→install- Keyin
COPY . .vadump-autoload - Paketlar qatlami faqat
composer.locko‘zgarganda yangilanadi .dockerignore:.git,.env,vendor,node_modules
1-bo‘lim yakuni: Docker: image, konteyner va Dockerfile
composer.json ni manba koddan oldin nusxalaymiz?1-topshiriq: Docker image teglari (semver)
GitHub Actions git teg (v1.4.2) asosida Docker image uchun teglar ro‘yxatini yasaydi. Teg vX.Y.Z yoki X.Y.Z ko‘rinishida, ixtiyoriy pre-release qismi bilan (-rc.1, -beta: harf, raqam, nuqta). Barqaror versiya uchun teglar: X.Y.Z, X.Y, X, latest. Agar asosiy versiya 0 bo‘lsa — faqat 0.Y.Z va 0.Y (API hali barqaror emas). Pre-release versiya faqat to‘liq tegini oladi. Format noto‘g‘ri bo‘lsa — InvalidArgumentException.
Imzo: function image_teglari(string $teg): array
Qaytaradi: Satrlar ro‘yxati, aynan yuqoridagi tartibda (boshidagi v olib tashlanadi).
image_teglari('v1.4.2')["1.4.2","1.4","1","latest"]
Docker Compose stek: web, app, worker, db, redis
Oltita servis — bitta compose.yaml
Bir xil omborpro image dan uchta servis ishlaydi; farqi — faqat buyruq.
1web — nginx
.php ni app:9000 ga uzatadi.2app — php-fpm
/api/v1 REST API.3worker
php artisan queue:work — hisobotlar, kam qoldiq bildirishnomalari.4scheduler
php artisan schedule:work — har daqiqada rejalashtirilgan vazifalar.5db — PostgreSQL 16
pgdata volume da.6redis — Redis 7
web, app, worker — umumiy sozlama yakor bilan
x-app: &app image: ghcr.io/jamoa/omborpro:${TAG:-latest} env_file: .env volumes: [storage:/var/www/storage/app] restart: unless-stopped depends_on: db: { condition: service_healthy } redis: { condition: service_started } services: web: image: ghcr.io/jamoa/omborpro-web:${TAG:-latest} ports: ["80:80"] depends_on: [app] restart: unless-stopped app: *app worker: <<: *app command: php artisan queue:work --tries=3 --max-time=3600
$ TAG=1.4.0 docker compose up -d ✔ Container omborpro-db-1 Healthy ✔ Container omborpro-redis-1 Started ✔ Container omborpro-app-1 Started ✔ Container omborpro-worker-1 Started ✔ Container omborpro-web-1 Started
*app va <<: *app bilan qayta ishlatiladiTAG=1.4.0app faqat PostgreSQL tayyor bo‘lgach ishga tushadinginx.conf va public/ (CSS/JS) ichidaversion: kaliti eskirgan — Compose v2 uni e’tiborsiz qoldiradi, yozmang.db va redis: volume va healthcheck
db: image: postgres:16-alpine environment: POSTGRES_DB: omborpro POSTGRES_USER: omborpro POSTGRES_PASSWORD: ${DB_PASSWORD:?DB_PASSWORD kerak} volumes: [pgdata:/var/lib/postgresql/data] healthcheck: test: ["CMD-SHELL", "pg_isready -U omborpro -d omborpro"] interval: 5s retries: 10 restart: unless-stopped redis: image: redis:7-alpine volumes: [redisdata:/data] restart: unless-stopped volumes: { pgdata: {}, redisdata: {}, storage: {} }
$ docker compose ps db NAME IMAGE STATUS omborpro-db-1 postgres:16-alpine Up 3 minutes (healthy)
DB_HOST=dbhealthydocker compose down ma’lumotni saqlaydi; down -v — o‘chiradi!Laravel uchun nginx konfiguratsiyasi
server { listen 80; server_name omborpro.example.uz; root /var/www/public; index index.php; client_max_body_size 20m; location / { try_files $uri $uri/ /index.php?$query_string; } location ~ \.php$ { fastcgi_pass app:9000; fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name; include fastcgi_params; } location ~ /\.(?!well-known).* { deny all; } }
$ curl -I http://omborpro.example.uz/.env HTTP/1.1 403 Forbidden $ curl -I http://omborpro.example.uz/orders HTTP/1.1 302 Found Location: http://omborpro.example.uz/login
public ochiq; .env va app/ brauzerga ko‘rinmaydiindex.php (Laravel marshrutlari)127.0.0.1 emas.env, .git kabi yashirin fayllar — 403client_max_body_size — Excel import (8-mavzu) uchun fayl hajmi chegarasi; sukut bo‘yicha 1 MB.nginx so‘rovni qayerga yuboradi?
// nginx qoidalarining soddalashtirilgan modeli function nginx(string $uri, array $files): string { $path = parse_url($uri, PHP_URL_PATH); $query = parse_url($uri, PHP_URL_QUERY) ?? ''; if (preg_match('#/\.(?!well-known)#', $path)) { return '403 (deny all)'; } if (in_array($path, $files, true)) { return "statik fayl: $path"; } return "php-fpm: /index.php?$query"; } $files = ['/favicon.ico', '/build/app.css']; foreach (['/build/app.css', '/orders?page=2', '/.env', '/api/v1/products'] as $u) { echo str_pad($u, 18), '→ ', nginx($u, $files), PHP_EOL; }
/build/app.css → statik fayl: /build/app.css /orders?page=2 → php-fpm: /index.php?page=2 /.env → 403 (deny all) /api/v1/products → php-fpm: /index.php?
location lar prefiks / dan ustun turadipublic/ dagi haqiqiy fayllar — PHP ishga tushmaydi, tezpage=2 Laravel ga $request->query('page') bo‘lib yetadi2-bo‘lim yakuni: Docker Compose stek: web, app, worker, db, redis
.env da DB_HOST=127.0.0.1 emas, DB_HOST=db yoziladi?depends_on va condition: service_healthy ning farqi nimada?root ni loyiha ildiziga qaratsak, qanday xavf paydo bo‘ladi?2-topshiriq: Konteyner healthcheck holati
Docker har interval da healthcheck buyrug‘ini bajaradi. Konteyner starting holatida boshlanadi. Muvaffaqiyatli tekshiruv (true) holatni healthy qiladi va ketma-ket xatolar hisoblagichini 0 ga tushiradi. Muvaffaqiyatsiz tekshiruv (false) hisoblagichni oshiradi; hisoblagich retries ga yetsa — unhealthy, aks holda holat o‘zgarmaydi. Har bir tekshiruvdan keyingi holatlar ro‘yxatini qaytaring. retries < 1 bo‘lsa — InvalidArgumentException.
Imzo: function healthcheck_holatlari(array $natijalar, int $retries): array
Qaytaradi: $natijalar uzunligidagi satrlar ro‘yxati: starting, healthy yoki unhealthy.
healthcheck_holatlari([false, false, true, true], 3)
["starting","starting","healthy","healthy"]
CI/CD: GitHub Actions bilan lint, test, build
ci.yml: hodisalar va lint job
name: CI on: push: { branches: [main], tags: ['v*'] } pull_request: permissions: { contents: read, packages: write } jobs: lint: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: shivammathur/setup-php@v2 with: { php-version: '8.2', tools: composer:v2 } - run: composer install --no-interaction --prefer-dist - run: vendor/bin/pint --test - run: vendor/bin/phpstan analyse --memory-limit=1G
lint ✓ Run vendor/bin/pint --test
PASS ............................ 214 files
lint ✓ Run vendor/bin/phpstan analyse --memory-limit=1G
[OK] No errorsv* teg da ishga tushadiphpstan.neon dagi daraja bilanPest testlari PostgreSQL servis konteyneri bilan
test: runs-on: ubuntu-latest services: postgres: image: postgres:16 env: { POSTGRES_PASSWORD: secret, POSTGRES_DB: testing } ports: ['5432:5432'] options: --health-cmd pg_isready --health-retries 10 env: { DB_CONNECTION: pgsql, DB_HOST: 127.0.0.1, DB_DATABASE: testing, DB_USERNAME: postgres, DB_PASSWORD: secret } steps: - uses: actions/checkout@v4 - uses: shivammathur/setup-php@v2 with: { php-version: '8.2', extensions: pdo_pgsql } - run: composer install --no-interaction --prefer-dist - run: cp .env.example .env && php artisan key:generate - run: vendor/bin/pest
PASS Tests\Feature\OrderServiceTest ✓ buyurtmani tasdiqlash qoldiqni rezervlaydi 0.21s ✓ mavjud qoldiqdan ko‘p rezerv taqiqlanadi 0.08s Tests: 86 passed (241 assertions) Duration: 9.42s
.env dagi qiymatlardan ustun turadiAPP_KEYImage ni yig‘ish va GHCR ga yuklash
build: needs: [lint, test] if: github.event_name == 'push' runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: docker/login-action@v3 with: registry: ghcr.io username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - uses: docker/build-push-action@v6 with: context: . push: true tags: | ghcr.io/jamoa/omborpro:${{ github.sha }} ghcr.io/jamoa/omborpro:latest
build ✓ docker/build-push-action@v6 #12 pushing ghcr.io/jamoa/omborpro:9f3c2a1... done #12 pushing ghcr.io/jamoa/omborpro:latest done
ghcr.io da kichik harflarda bo‘lishi shart. Semver teglar uchun docker/metadata-action@v5 qulay.3-bo‘lim yakuni: CI/CD: GitHub Actions bilan lint, test, build
pint emas, pint --test ishlatiladi?needs kerak?Production konfiguratsiyasi va keshlash
Production uchun asosiy sozlamalar
APP_NAME=OmborPro APP_ENV=production APP_DEBUG=false APP_KEY=base64:... # key:generate --show APP_URL=https://omborpro.example.uz APP_TIMEZONE=Asia/Tashkent LOG_LEVEL=warning DB_CONNECTION=pgsql DB_HOST=db DB_DATABASE=omborpro DB_USERNAME=omborpro DB_PASSWORD= # faqat serverda to‘ldiriladi CACHE_STORE=redis QUEUE_CONNECTION=redis SESSION_DRIVER=redis SESSION_SECURE_COOKIE=true REDIS_HOST=redis
$ docker compose exec app php artisan about --only=environment Application Name ......................... OmborPro Environment ............................ production Debug Mode ................................... OFF Timezone ............................ Asia/Tashkent
.env — git da emas. Serverda: chmod 600 .env, egasi — deploy foydalanuvchisi.Deploy paytidagi artisan buyruqlari
| Buyruq | Nima qiladi | Eslatma |
|---|---|---|
config:cache | Konfiguratsiyani bitta faylga yig‘adi | Keyin .env o‘qilmaydi |
route:cache | Marshrutlar ro‘yxatini keshlaydi | Marshrutlar ko‘p bo‘lsa sezilarli tezlik |
view:cache | Blade shablonlarini oldindan kompilyatsiya qiladi | Birinchi so‘rov sekinlashmaydi |
event:cache | Hodisa → tinglovchi xaritasini keshlaydi | Avto-topish har so‘rovda ishlamaydi |
optimize | Laravel 12: yuqoridagi to‘rttasini bajaradi | Har deployda |
optimize:clear | Barcha keshlarni tozalaydi | Muammo bo‘lsa birinchi qadam |
queue:restart | Worker larga “joriy vazifadan keyin qayta ishga tush” signali | Kod yangilangandan keyin |
.env va marshrut o‘zgarishlari ko‘rinmay qoladi.Production .env ni deploydan oldin tekshirish
function prodXatolar(array $env): array { $x = []; if (($env['APP_ENV'] ?? '') !== 'production') { $x[] = 'APP_ENV=production bo‘lishi kerak'; } if (($env['APP_DEBUG'] ?? 'true') !== 'false') { $x[] = 'APP_DEBUG=false bo‘lishi kerak'; } if (!str_starts_with($env['APP_KEY'] ?? '', 'base64:')) { $x[] = 'APP_KEY o‘rnatilmagan'; } return $x; } $env = ['APP_ENV' => 'production', 'APP_DEBUG' => 'true']; echo implode(PHP_EOL, prodXatolar($env)), PHP_EOL; echo count(prodXatolar(['APP_ENV' => 'production', 'APP_DEBUG' => 'false', 'APP_KEY' => 'base64:a2V5'])), PHP_EOL;
APP_DEBUG=false bo‘lishi kerak APP_KEY o‘rnatilmagan 0
.env dagi qiymat — satr; (bool) 'false' esa true!key:generate yaratgan kalit formaticonfig:cache dan keyin env() qayerda ishlaydi?
Noto‘g‘ri: env() kod ichida
CbuRateService:Http::get(env('CBU_URL'))- Lokal muhitda ishlaydi — kesh yo‘q
- Production da
config:cache→.envo‘qilmaydi →null - Xato faqat serverda chiqadi — eng qimmat xato
To‘g‘ri: env() faqat config/ da
config/services.php:'cbu' => ['url' => env('CBU_URL')]- Kodda:
config('services.cbu.url') - Qiymat kesh faylida saqlanadi
- Code review va Larastan qoidasi bilan nazorat qilinadi
env('CBU_URL', 'https://cbu.uz/...').4-bo‘lim yakuni: Production konfiguratsiyasi va keshlash
APP_DEBUG=true qolsa, qanday xavf bor?php artisan optimize qaysi keshlarni yaratadi?config:cache dan keyin controller ichidagi env('CBU_URL') nima qaytaradi va nima uchun?Zaxira nusxalar (backup) va tiklash
Nimani, qancha va qayerda saqlaymiz?
1RPO
2RTO
33 nusxa
42 vosita
51 offsite
6Shifrlash va sinov
down -v, xato DELETE yoki hosting bloklanishidan himoya qilmaydi.Kunlik zaxira skripti va cron
#!/usr/bin/env bash # /opt/omborpro/backup.sh — har kuni cron orqali set -euo pipefail cd /opt/omborpro FILE="backups/omborpro_$(date +%F_%H%M).dump" docker compose exec -T db \ pg_dump -U omborpro -Fc omborpro > "$FILE" test -s "$FILE" # bo‘sh fayl — xato rclone copy "$FILE" offsite:omborpro-backups find backups -name '*.dump' -mtime +14 -delete # crontab -e (server vaqti: Asia/Tashkent) # 30 2 * * * /opt/omborpro/backup.sh >> /var/log/omb-backup.log 2>&1 # Tiklash mashqi — ALOHIDA test bazaga: # docker compose exec -T db pg_restore --clean --if-exists \ # -U omborpro -d omborpro_restore_test < backups/oxirgi.dump
$ ls -lh /opt/omborpro/backups | tail -2 -rw-r--r-- 1 deploy deploy 18M Oct 26 02:30 omborpro_2026-10-26_0230.dump -rw-r--r-- 1 deploy deploy 18M Oct 27 02:30 omborpro_2026-10-27_0230.dump
pg_restore bilan tanlab tiklanadiQaysi nusxalar qoladi? (kunlik + haftalik)
function saqlanadi(array $sanalar, int $kunlik, int $hafta): array { rsort($sanalar); $keep = array_slice($sanalar, 0, $kunlik); $yak = array_filter($sanalar, fn ($s) => (new DateTimeImmutable($s))->format('N') === '7'); $keep = array_unique([...$keep, ...array_slice($yak, 0, $hafta)]); rsort($keep); return $keep; } $bugun = new DateTimeImmutable('2026-10-27'); $sanalar = []; for ($i = 0; $i < 30; $i++) { $sanalar[] = $bugun->modify("-$i day")->format('Y-m-d'); } $keep = saqlanadi($sanalar, 3, 3); echo implode(PHP_EOL, $keep), PHP_EOL; echo 'O‘chiriladi: ', count($sanalar) - count($keep), PHP_EOL;
2026-10-27 2026-10-26 2026-10-25 2026-10-18 2026-10-11 O‘chiriladi: 25
Y-m-d satrlari alifbo bo‘yicha ham sana bo‘yicha saralanadio-W) va noto‘g‘ri sanalar tekshiruvi bilan.5-bo‘lim yakuni: Zaxira nusxalar (backup) va tiklash
docker compose exec ga -T bayrog‘i qo‘shiladi?Production migratsiyalari va xavfsiz deploy
Ustunni uzilishsiz qayta nomlash
✗ Bir qadamda: renameColumn
$table->renameColumn('method', 'channel')- Migratsiya tugadi — eski konteyner hali
methodga yozadi - To‘lov webhooklari 500 xato beradi
- Orqaga qaytarish ham uzilish bilan
✓ Expand/contract: 3 reliz
- 1.5:
channelqo‘shiladi, kod ikkalasiga yozadi - 1.5: eski yozuvlar qismlarga bo‘lib ko‘chiriladi
- 1.6: kod faqat
channelni o‘qiydi - 1.7:
methodustuni o‘chiriladi (contract)
Katta jadvalga indeksni qulfsiz qo‘shish
<?php use Illuminate\Database\Migrations\Migration; use Illuminate\Support\Facades\DB; return new class extends Migration { // CONCURRENTLY tranzaksiya ichida ishlamaydi public $withinTransaction = false; public function up(): void { DB::statement('CREATE INDEX CONCURRENTLY IF NOT EXISTS ' . 'invoices_status_due_at_idx ' . 'ON invoices (status, due_at)'); } };
$ php artisan migrate --force INFO Running migrations. 2026_10_27_090000_add_invoices_status_due_index .. 2s DONE
invoices ga yozish bloklanmaydiServerdagi deploy.sh — har qadam yozilgan
#!/usr/bin/env bash # ishlatish: ./deploy.sh 1.4.0 set -euo pipefail cd /opt/omborpro export TAG="$1" ./backup.sh # 1) avval zaxira docker compose pull # 2) yangi image lar docker compose run --rm app \ php artisan migrate --force # 3) orqaga mos migratsiya docker compose up -d --remove-orphans # 4) konteynerlarni yangilash docker compose exec -T app php artisan queue:restart curl -fsS https://omborpro.example.uz/up > /dev/null \ && echo "Deploy $TAG: OK" # 5) tutun testi
$ ./deploy.sh 1.4.0 ✔ app Pulled ✔ web Pulled 2026_10_27_090000_add_invoices_status_due_index .. DONE ✔ Container omborpro-app-1 Recreated ✔ Container omborpro-worker-1 Recreated Deploy 1.4.0: OK
php artisan optimize konteyner ishga tushganda entrypoint skriptida bajariladi (amaliy mashg‘ulotda).6-bo‘lim yakuni: Production migratsiyalari va xavfsiz deploy
migrate emas, migrate --force yoziladi?down --secret) foydalanuvchi va administrator nimani ko‘radi?3-topshiriq: Migratsiya xavfini baholash
Production ga chiqishdan oldin bitta SQL buyrug‘ining (PostgreSQL) xavf darajasini aniqlang (katta-kichik harf farqsiz). xavfli: DROP TABLE, DROP COLUMN, RENAME, ALTER COLUMN <ustun> TYPE yoki SET DATA TYPE, yoki ADD COLUMN + NOT NULL bo‘lib, DEFAULT yo‘q. ehtiyot: CREATE INDEX / CREATE UNIQUE INDEX CONCURRENTLY siz, yoki SET NOT NULL. Qolganlari — xavfsiz. Bir nechta qoida mos kelsa — eng yuqori daraja. Bo‘sh (yoki faqat bo‘sh joydan iborat) SQL — InvalidArgumentException.
Imzo: function migratsiya_xavfi(string $sql): string
Qaytaradi: 'xavfsiz', 'ehtiyot' yoki 'xavfli'.
migratsiya_xavfi('ALTER TABLE products DROP COLUMN unit')"xavfli"
Asosiy xulosalar
1Bir marta yig‘, hamma joyda ishlat
--no-dev, pdo_pgsql, redis, opcache; bir xil image test va production da.2Compose — butun stek
service_healthy.3nginx + php-fpm
root public, try_files ... /index.php?$query_string, fastcgi_pass app:9000.4CI/CD quvuri
--test, Larastan, Pest (PostgreSQL bilan) → image GHCR ga → deploy.5Production sozlamalari
APP_DEBUG=false, maxfiy .env, optimize, env() faqat config da, queue:restart.6Zaxira va migratsiya
-Fc + 3-2-1 + tiklash mashqi; migrate --force, expand/contract, CONCURRENTLY.Yakunlashdan oldin sakkizta savol
COPY composer.json COPY . . dan oldin?depends_on yetarli emasmi?fastcgi_pass qayerga qaratiladi?pint --test nima qiladi?config:cache dan keyin env()?14-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
.env qatorini tahlil qilish
Tashqariga ochiq portlarni aniqlash
Servislarni ishga tushirish tartibi
CI pipeline bosqichlari va davomiyligi
Zaxira nusxalarni saqlash siyosati (GFS)
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.