10-amaliy mashg‘ulot · 10-mavzu · 2 soat · Korxona ilovalarini dasturlash
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.
docker-compose · .env · Mailpit · tekshiruv buyruqlari
2-mavzuda yaratilgan docker-compose.yml da app, nginx, db va redis servislari bor. Bugun yana uchtasini qo‘shamiz: queue (worker), scheduler va mailpit. Worker va scheduler app bilan bir xil obrazdan quriladi — faqat ishga tushirish buyrug‘i boshqa. Shunda kod bitta, jarayonlar esa alohida: veb-so‘rovlar sekinlashsa ham workerlar ishlayveradi va aksincha. restart: unless-stopped — Supervisor vazifasini Docker bajaradi.
.env da QUEUE_CONNECTION=redis, CACHE_STORE=redis (ShouldBeUnique va onOneServer qulflari uchun), MAIL_MAILER=smtp, MAIL_HOST=mailpit, MAIL_PORT=1025 va APP_TIMEZONE=Asia/Tashkent ni o‘rnating. Laravel 12 da sozlamalar o‘zgargach konfiguratsiya keshi bo‘lsa, php artisan config:clear qiling. Database bildirishnomalari uchun php artisan make:notifications-table va php artisan migrate ni bajaring (failed_jobs jadvali Laravel 12 da boshidanoq bor).
Tekshiruv: docker compose up -d, so‘ng docker compose logs -f queue — worker “Processing jobs from the [reports,default] queues” deb yozishi kerak. php artisan tinker da App\Jobs\SendLowStockAlert::dispatch() ni bajaring va worker logida RUNNING/DONE qatorlarini ko‘ring. Xatlar http://localhost:8025 dagi Mailpit interfeysida chiqadi. Keng tarqalgan muammo: worker konteyneri eski kodni ishlatyapti — kod o‘zgargach docker compose restart queue yoki php artisan queue:restart.
queue: build: . command: > php artisan queue:work redis --queue=reports,default --tries=3 --max-time=3600 depends_on: [db, redis] restart: unless-stopped scheduler: build: . command: php artisan schedule:work depends_on: [db, redis] restart: unless-stopped mailpit: image: axllent/mailpit ports: ["8025:8025", "1025:1025"]
$ docker compose ps omborpro-queue-1 running omborpro-scheduler-1 running omborpro-mailpit-1 running 0.0.0.0:8025->8025/tcp
build: . — worker va scheduler — app bilan bir xil kod va obraz--queue=reports,default — hisobotlar ustuvor; e-mail lar default daschedule:work — har daqiqada schedule:run — faqat bitta replika!APP_TIMEZONE=Asia/Tashkent QUEUE_CONNECTION=redis CACHE_STORE=redis REDIS_HOST=redis MAIL_MAILER=smtp MAIL_HOST=mailpit MAIL_PORT=1025 MAIL_FROM_ADDRESS="noreply@omborpro.test" MAIL_FROM_NAME="OmborPro"
$ php artisan about --only=drivers Cache ............ redis Mail ............. smtp Queue ............ redis
CACHE_STORE=redis — ShouldBeUnique, onOneServer va queue:restart signali uchunMAIL_HOST=mailpit — xatlar real manzillarga ketmaydinow() Toshkent vaqtidaphp artisan make:notifications-table → php artisan migratedocker compose up -d → docker compose ps — hammasi runningdocker compose logs -f queue — “Processing jobs from …”App\Jobs\SendLowStockAlert::dispatch() → logda DONEhttp://localhost:8025 — Mailpit da xat ko‘rinadiReportService::exportSales · job · endpoint · yuklab olish
9-mavzudagi ReportService ga exportSales(User $user, string $from, string $to): string metodini qo‘shamiz: u maatwebsite/excel ning Excel::store() usuli bilan faylni storage/app/reports/{user_id}/ papkasiga yozadi va yo‘lini qaytaradi. Fayl nomi davrdan tuziladi (sales-2026-10-01_2026-10-31.xlsx) — shuning uchun job takror bajarilsa ham fayl shunchaki qayta yoziladi: amal idempotent. Foydalanuvchi id si yo‘lda bo‘lgani uchun yuklab olishda faylning egasini tekshirish oson.
Job tries = 3, timeout = 80 (bizda retry_after = 90), backoff = [30, 120] bilan sozlanadi va reports navbatiga yuboriladi. handle() faylni yaratgach foydalanuvchiga ReportReadyNotification (faqat database kanali, toArray() da fayl nomi va yuklab olish havolasi) yuboradi. failed() metodida ham foydalanuvchiga “hisobot tayyorlanmadi, qayta urinib ko‘ring” degan xabar yuboring — aks holda u abadiy kutadi.
Endpoint: POST /reports/sales (buxgalter va admin uchun, 5-mavzudagi Policy/Gate bilan), so‘rovni validatsiya qilib jobni yuboradi va 202 qaytaradi. GET /reports/{file} — Storage::download() bilan faylni beradi, lekin faqat yo‘l joriy foydalanuvchi papkasida bo‘lsa. Sinov: brauzer DevTools da so‘rov vaqti 100 ms dan kam ekanini, worker logida jobning RUNNING/DONE qatorlarini, so‘ng bildirishnoma va faylni tekshiring. Keyin Redis ni vaqtincha to‘xtatib, xato holatda nima bo‘lishini kuzating.
public function exportSales( User $user, string $from, string $to, ): string { $path = "reports/{$user->id}/sales-{$from}_{$to}.xlsx"; Excel::store(new SalesReportExport($from, $to), $path, 'local'); return $path; }
storage/app/reports/7/sales-2026-10-01_2026-10-31.xlsx (412 KB)
$path — aniq nom: takroriy bajarilish faylni qayta yozadi (idempotent){$user->id} — fayl egasi yo‘ldan aniq — yuklab olishda tekshiriladiExcel::store — maatwebsite/excel: eksport sinfini diskka yozadiclass GenerateSalesReport implements ShouldQueue { use Queueable; public int $tries = 3; public int $timeout = 80; public array $backoff = [30, 120]; public function __construct( public User $user, public string $from, public string $to, ) {} public function handle(ReportService $reports): void { $path = $reports->exportSales( $this->user, $this->from, $this->to, ); $this->user->notify(new ReportReadyNotification($path)); } }
2026-10-27 10:15:02 App\Jobs\GenerateSalesReport ..... RUNNING 2026-10-27 10:15:06 App\Jobs\GenerateSalesReport . 3.91s DONE
$timeout = 80 — retry_after = 90 dan kichik$backoff = [30, 120] — baza band bo‘lsa — 30 s, keyin 2 daqiqa kutishdatabase kanali: qo‘ng‘iroqchada havola| Ssenariy | Kutilgan natija | Qayerda ko‘rinadi |
|---|---|---|
| To‘g‘ri davr bilan so‘rov | 202, javob < 100 ms | DevTools → Network |
to < from | 422, job navbatga tushmaydi | Javob JSON, worker logi bo‘sh |
omborchi roli bilan so‘rov | 403 | Policy / Gate |
| Worker ishlayapti | RUNNING → DONE, fayl paydo bo‘ladi | logs -f queue, storage/app/reports |
| Worker to‘xtatilgan | Job Redis da kutadi, ishga tushgach bajariladi | redis-cli LLEN ...queues:reports |
| Begona foydalanuvchi faylni so‘raydi | 403 yoki 404 | GET /reports/{file} |
lowStock so‘rovi · SendLowStockAlert · LowStockNotification · Schedule
Avval “kam qoldiq” ni aniq ta’riflaymiz: faol mahsulotning barcha omborlardagi mavjud qoldig‘i yig‘indisi (quantity − reserved) min_stock dan kichik. Buni ProductRepository::lowStock() metodida bitta SQL so‘rov bilan hisoblaymiz: products ga stocks ni LEFT JOIN qilib, GROUP BY va HAVING bilan. LEFT JOIN muhim — umuman qoldig‘i yo‘q (ombor yozuvi yo‘q) mahsulot ham ro‘yxatga tushadi. Natijani sku bo‘yicha tartiblang, available ni butun songa o‘tkazing.
SendLowStockAlert jobi ma’ruzadagi idempotent shablon bo‘yicha yoziladi: ShouldBeUnique, kunlik kesh kaliti, ro‘yxat bo‘sh bo‘lsa — hech narsa yubormaslik, belgi faqat muvaffaqiyatdan keyin. Qabul qiluvchilar — omborchi va menejer rollaridagi faol foydalanuvchilar. LowStockNotification ga Eloquent kolleksiyasi emas, sku, name, available, min_stock maydonlaridan iborat oddiy massiv beriladi; via() — mail va database.
Jadval routes/console.php da: Schedule::job(new SendLowStockAlert())->weekdays()->at('09:00')->timezone('Asia/Tashkent')->onOneServer(). Tekshirish uchun php artisan schedule:list (keyingi ishga tushish vaqti), php artisan schedule:test (darhol sinash) va Mailpit dan foydalaning. Sinov ma’lumoti: seeder yoki tinker bilan bitta mahsulotning qoldig‘ini min_stock dan kamaytiring; jobni ikki marta ishga tushiring va xat faqat bitta kelganini tasdiqlang.
public function lowStock(): Collection { $sum = 'COALESCE(SUM(stocks.quantity - stocks.reserved), 0)'; return Product::query() ->select('products.sku', 'products.name', 'products.min_stock') ->selectRaw("$sum AS available") ->leftJoin('stocks', 'stocks.product_id', '=', 'products.id') ->where('products.is_active', true) ->groupBy('products.id', 'products.sku', 'products.name', 'products.min_stock') ->havingRaw("$sum < products.min_stock") ->orderBy('products.sku') ->get(); }
sku | name | min_stock | available UN-001 | Un 1-nav 50 kg | 10 | 4 UN-014 | Shakar 50 kg | 5 | 0
quantity - reserved — mavjud qoldiq — rezerv hisobga olinadiWHERE da emasphp artisan tinker > Stock::where('product_id', 1)->update(['quantity' => 3]); > App\Jobs\SendLowStockAlert::dispatchSync(); > App\Jobs\SendLowStockAlert::dispatchSync(); > Cache::get('low-stock-alert:' . now()->toDateString()); > exit php artisan schedule:list php artisan schedule:test --name="App\Jobs\SendLowStockAlert"
= true 0 9 * * 1-5 App\Jobs\SendLowStockAlert ... Next Due: 21 hours from now Mailpit: 1 ta xat (“Kam qoldiq: 1 ta mahsulot”)
dispatchSync() — navbatsiz darhol bajarish — tez sinov uchunCache::has da to‘xtaydi — xat bittaschedule:test — jadvaldagi vazifani vaqtini kutmasdan ishga tushiradiavailable yo‘qoladidailyAt('09:00') — xat 14:00 dafailed() yo‘q — xato jim o‘tib ketadiShouldBeUnique — kuniga bitta xatsku, name, available, min_stock->timezone('Asia/Tashkent')->onOneServer()failed() logga yozadi va adminni ogohlantiradiNatija: hisobot so‘rovi 202 javob bilan darhol qaytadi va worker tomonidan fon rejimida tayyorlanadi; ish kunlari 09:00 da kam qoldiq haqida e-mail va panel bildirishnomasi avtomatik, kuniga bir marta yuboriladi.
Baholash mezonlaridocker-compose.yml da queue, scheduler va mailpit servislari bor; QUEUE_CONNECTION=redis.POST /reports/sales 202 qaytaradi, noto‘g‘ri davrda 422; job reports navbatiga tushadi.GenerateSalesReport da tries, timeout (< retry_after), backoff va failed() bor.ProductRepository::lowStock() mavjud qoldiqni (quantity − reserved) bitta SQL so‘rov bilan hisoblaydi.SendLowStockAlert idempotent: ikki marta ishga tushirilsa ham bir kunda bitta xat.LowStockNotification mail va database kanallariga yuboradi, massiv qabul qiladi.php artisan schedule:list da vazifa 0 9 * * 1-5 va Asia/Tashkent bilan ko‘rinadi.📤 GitHub repo dagi feature/queues tarmog‘idan ochilgan Pull Request havolasini yuboring; PR tavsifiga Mailpit dagi xat, worker logi va schedule:list natijasining skrinshotlarini qo‘shing.
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.