5-amaliy mashg‘ulot · 5-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.
permission: middleware, buyurtmalarni OrderPolicy bilan@can / @role direktivalari bilan rolga qarabcomposer · migratsiya · HasRoles · seeder · test foydalanuvchilar
1-qadam. Jamoa loyihasida yangi tarmoq oching (feature/rbac-audit). Paketni o‘rnating va konfiguratsiya hamda migratsiyani nashr qiling: composer require spatie/laravel-permission, so‘ng php artisan vendor:publish --provider="Spatie\Permission\PermissionServiceProvider" va php artisan migrate. Natijada config/permission.php va beshta jadval paydo bo‘ladi: roles, permissions, model_has_roles, model_has_permissions, role_has_permissions. PostgreSQL da ularni \dt bilan tekshiring.
2-qadam. app/Models/User.php ga use HasRoles; trait ini qo‘shing. 3-mavzuda yaratgan users jadvalida is_active ustuni bor — uni $fillable ga va casts() ga ('is_active' => 'boolean') qo‘shing. $hidden da password va remember_token borligiga ishonch hosil qiling: ular JSON javoblarga ham, audit jurnaliga ham tushmasligi kerak.
3-qadam. php artisan make:seeder RolesAndPermissionsSeeder buyrug‘i bilan seeder yarating va ma’ruzadagi matritsani yozing: 14 ta ruxsat (products.view, products.manage, orders.view, orders.create, orders.confirm, orders.cancel, stock.view, stock.move, invoices.view, invoices.create, payments.create, reports.view, users.manage, audit.view) va 4 ta rol. Seeder boshida keshni tozalang, findOrCreate va syncPermissions ishlating — seeder ni ikki marta ishga tushirganda ham natija bir xil bo‘lishi shart.
4-qadam. Har bir rol uchun bittadan test foydalanuvchi yarating (admin@omborpro.test, menejer@omborpro.test, omborchi@omborpro.test, buxgalter@omborpro.test) va bitta bloklangan (is_active = false) foydalanuvchi. Parol — faqat lokal muhit uchun umumiy test paroli; uni README da “faqat development” deb belgilang. DatabaseSeeder dan ikkala seeder ni chaqiring va php artisan migrate:fresh --seed bilan tekshiring.
git switch -c feature/rbac-audit composer require spatie/laravel-permission php artisan vendor:publish \ --provider="Spatie\Permission\PermissionServiceProvider" php artisan migrate php artisan make:seeder RolesAndPermissionsSeeder php artisan make:policy OrderPolicy --model=Order php artisan migrate:fresh --seed
INFO Publishing assets. config/permission.php ......................... DONE database/migrations/..._create_permission_tables.php ... DONE INFO Policy [app/Policies/OrderPolicy.php] created successfully.
vendor:publish — config/permission.php va jadvallar migratsiyasini loyihaga nusxalaydimake:policy --model — CRUD metodlari tayyor Policy skeletini yaratadimigrate:fresh --seed — faqat lokal bazada: hammasini qayta yaratib, seeder larni ishga tushiradinamespace App\Models; use Illuminate\Foundation\Auth\User as Authenticatable; use Spatie\Permission\Traits\HasRoles; class User extends Authenticatable { use HasRoles; protected $fillable = ['name', 'email', 'password', 'is_active']; protected $hidden = ['password', 'remember_token']; protected function casts(): array { return ['password' => 'hashed', 'is_active' => 'boolean']; } }
>>> User::firstWhere('email', 'menejer@omborpro.test')
... ->getPermissionNames()
= ["orders.view", "orders.create", "orders.confirm",
"orders.cancel", "products.view", "stock.view", "reports.view"]assignRole, hasRole, getRoleNames, getPermissionNames va boshqalar$hidden — toArray()/JSON da parol va token chiqmaydicasts() — Laravel 12 uslubi — $casts xossasi o‘rniga metod| Rol | is_active | Kutilgan xatti-harakat | |
|---|---|---|---|
admin@omborpro.test | admin | true | hamma modul, foydalanuvchilar va audit |
menejer@omborpro.test | menejer | true | buyurtmalar: yaratish, tasdiqlash, bekor qilish |
omborchi@omborpro.test | omborchi | true | ombor harakatlari, mahsulot katalogi |
buxgalter@omborpro.test | buxgalter | true | hisob-faktura, to‘lovlar, hisobotlar |
blocked@omborpro.test | menejer | false | login rad etiladi |
middleware aliaslari · marshrut guruhlari · OrderPolicy · @can
5-qadam. Laravel 12 da app/Http/Kernel.php yo‘q — middleware aliaslari bootstrap/app.php faylidagi withMiddleware ichida $middleware->alias([...]) bilan ro‘yxatdan o‘tkaziladi. spatie paketi uchta middleware beradi: role, permission, role_or_permission. Bir nechta ruxsatdan biri yetarli bo‘lsa, ular | bilan yoziladi: permission:invoices.view|reports.view.
6-qadam. routes/web.php da marshrutlarni modullar bo‘yicha guruhlang. Barcha ichki sahifalar auth middleware i ostida; har bir modul guruhi o‘z permission: ruxsati bilan. Ma’ruzadagi tamoyil: middleware — modulga kirish, Policy — aniq hujjat ustidagi amal. AppServiceProvider::boot() ga Gate::before ni qo‘shing (admin uchun true, boshqalar uchun null).
7-qadam. OrderPolicy da view, create, update, confirm, cancel metodlarini yozing (ruxsat + holat + muallif). OrderController ning confirm, cancel, update metodlarida Gate::authorize(...) chaqiring — 4-mavzudagi OrderService faqat ruxsat tekshirilgandan keyin chaqirilsin. Laravel 12 Policy ni nomlash qoidasi bo‘yicha o‘zi topadi.
8-qadam. Interfeysda menyu bandlari va tugmalarni @can bilan rolga moslang: omborchi “Hisob-fakturalar” bandini ko‘rmaydi, buxgalter “Tasdiqlash” tugmasini ko‘rmaydi. So‘ng har bir test foydalanuvchi bilan kirib, yashirilgan sahifalarni manzil satri orqali ochishga urinib ko‘ring — har safar 403 chiqishi kerak. Natijalarni jadval ko‘rinishida PR tavsifiga yozing.
return Application::configure(basePath: dirname(__DIR__)) ->withRouting( web: __DIR__ . '/../routes/web.php', commands: __DIR__ . '/../routes/console.php', ) ->withMiddleware(function (Middleware $middleware) { $middleware->alias([ 'role' => RoleMiddleware::class, 'permission' => PermissionMiddleware::class, 'role_or_permission' => RoleOrPermissionMiddleware::class, ]); }) ->withExceptions(function (Exceptions $exceptions) { // }) ->create();
php artisan route:list --path=invoices
GET|HEAD invoices ......... invoices.index › InvoiceController@index
⇂ web, auth, permission:invoices.viewSpatie\Permission\Middleware\RoleMiddleware — faylning boshida use bilanalias([...]) — marshrutlarda qisqa nom bilan ishlatish uchunRoute::middleware('auth')->group(function () { Route::middleware('permission:orders.view')->group(function () { Route::resource('orders', OrderController::class); Route::post('orders/{order}/confirm', [OrderController::class, 'confirm'])->name('orders.confirm'); }); Route::middleware('permission:stock.view') ->get('stock', [StockController::class, 'index']); Route::middleware('permission:invoices.view') ->resource('invoices', InvoiceController::class); Route::middleware('permission:audit.view') ->get('audit', [AuditLogController::class, 'index']) ->name('audit.index'); });
omborchi GET /invoices → 403 Forbidden buxgalter GET /invoices → 200 OK menejer GET /audit → 403 Forbidden mehmon GET /orders → 302 /login
middleware('auth') — login qilmagan — login sahifasiga yo‘naltirishpermission:orders.view — butun modulga kirish; aniq amallar Policy daRoute::resource — CRUD marshrutlari bitta qatorda — guruh middleware i hammasiga qo‘llanadi<nav> @can('orders.view') <a href="{{ route('orders.index') }}">Buyurtmalar</a> @endcan @can('invoices.view') <a href="{{ route('invoices.index') }}">Hisob-fakturalar</a> @endcan @role('admin') <a href="{{ route('audit.index') }}">Audit jurnali</a> @endrole </nav> @can('confirm', $order) <form method="POST" action="{{ route('orders.confirm', $order) }}"> @csrf <button type="submit">Tasdiqlash</button> </form> @endcan
menejer → Buyurtmalar · [Tasdiqlash] buxgalter → Buyurtmalar · Hisob-fakturalar admin → Buyurtmalar · Hisob-fakturalar · Audit jurnali · [Tasdiqlash]
@can('orders.view') — spatie ruxsati — Gate orqali tekshiriladi@can('confirm', $order) — Policy metodi — obyekt va holat bilan@role('admin') — spatie direktivasi; lekin imkon qadar ruxsatni tekshiring/orders/{id}/edit orqali ochish — 403migratsiya · AuditLog modeli · Auditable trait · login hodisalari · ko‘rish sahifasi
9-qadam. audit_logs jadvali uchun migratsiya yozing (agar 3-mavzuda yaratilmagan bo‘lsa): user_id (nullable, users ga tashqi kalit), action, polimorf auditable_type + auditable_id (nullableMorphs), old_values va new_values (jsonb), ip, created_at. updated_at bo‘lmaydi — yozuv o‘zgarmaydi. (auditable_type, auditable_id) va created_at ga indeks qo‘ying.
10-qadam. AuditLog modelida const UPDATED_AT = null;, JSON maydonlar uchun array cast va o‘zgartirishni taqiqlovchi hodisalar: updating va deleting da LogicException tashlang. Shunda dastur kodi xato bilan ham jurnalni o‘zgartira olmaydi. Production uchun README ga PostgreSQL buyrug‘ini yozing: REVOKE UPDATE, DELETE ON audit_logs FROM omborpro_app;.
11-qadam. Ma’ruzadagi Auditable trait ini app/Models/Concerns/Auditable.php ga yozing va uni created, updated, deleted hodisalari uchun to‘ldiring; Product, Order, Invoice modellariga qo‘shing. Rol o‘zgarishini (role_changed) foydalanuvchini tahrirlash controllerida aniq yozing. Login hodisalari uchun AppServiceProvider::boot() da Illuminate\Auth\Events\Login va Failed hodisalariga Event::listen bilan obuna bo‘ling — muvaffaqiyatsiz urinishda e-mail yoziladi, parol esa hech qachon.
12-qadam. audit.view ruxsati bilan himoyalangan /audit sahifasini yarating: so‘nggi yozuvlar latest()->paginate(50), foydalanuvchi va amal bo‘yicha filtr, old_values → new_values farqi jadvalda. Tekshirish: menejer bilan mahsulot narxini o‘zgartiring, admin bilan jurnalda yozuv paydo bo‘lganini, parol o‘zgarganda esa *** yoki maydon umuman yo‘qligini ko‘ring.
Schema::create('audit_logs', function (Blueprint $table) { $table->id(); $table->foreignId('user_id')->nullable()->constrained(); $table->string('action', 40); $table->nullableMorphs('auditable'); $table->jsonb('old_values')->nullable(); $table->jsonb('new_values')->nullable(); $table->ipAddress('ip')->nullable(); $table->timestamp('created_at')->useCurrent()->index(); });
INFO Running migrations. 2026_10_27_090000_create_audit_logs_table ........ 18ms DONE \d audit_logs → ip: inet, old_values: jsonb, index audit_logs_auditable_type_auditable_id_index
nullableMorphs('auditable') — auditable_type, auditable_id va ikkalasiga birgalikdagi indeksinet turiclass AuditLog extends Model { const UPDATED_AT = null; protected $guarded = ['id']; protected $casts = [ 'old_values' => 'array', 'new_values' => 'array', ]; protected static function booted(): void { $deny = fn () => throw new LogicException('Audit o‘zgarmaydi'); static::updating($deny); static::deleting($deny); } }
>>> AuditLog::first()->update(['action' => 'x'])
LogicException Audit o‘zgarmaydi
>>> AuditLog::latest('id')->first()->action
= "login_failed"UPDATED_AT = null — Eloquent updated_at ni yozishga urinmaydi — ustun yo‘q$casts 'array' — jsonb ustunlar PHP massivi sifatida o‘qiladi va yoziladifn () => throw ... mumkin — istisno update()/delete() ni to‘xtatadiremember_token ko‘rinadiupdate() bilan o‘zgartirilgan va iz qolmagan/audit sahifasini menejer ham ocha oladiupdate() qilish mumkinProduct, Order, Invoice da created/updated/deleted yoziladilogin va login_failed IP bilan yoziladi/audit faqat audit.view (admin) uchun, filtr va sahifalash bilanAuditLog o‘zgartirilganda LogicExceptionNatija: OmborPro da to‘rtta rol va 14 ta modul ruxsati seeder orqali yaratilgan, marshrutlar va buyurtma amallari middleware hamda OrderPolicy bilan himoyalangan, asosiy modellardagi o‘zgarishlar va login urinishlari o‘zgartirib bo‘lmaydigan audit jurnaliga yoziladi.
spatie/laravel-permission o‘rnatilgan, User modelida HasRoles; RolesAndPermissionsSeeder takroriy ishga tushirilganda ham bir xil natija beradi.modul.amal ruxsati ma’ruzadagi matritsaga mos.auth va permission: middleware bilan himoyalangan; yashirilgan sahifa URL orqali ochilganda 403.OrderPolicy (update, confirm, cancel) ruxsat va buyurtma holatini tekshiradi; controller da Gate::authorize chaqiriladi.@can bilan rolga moslashgan; barcha POST formalarda @csrf.audit_logs ga Product, Order, Invoice o‘zgarishlari va login/login_failed yoziladi; parol va tokenlar yo‘q.AuditLog yozuvini o‘zgartirish yoki o‘chirish LogicException beradi; /audit sahifasi faqat audit.view uchun.📤 feature/rbac-audit tarmog‘idan main ga ochilgan Pull Request havolasini yuboring. PR tavsifida rol × sahifa natijalari jadvali va /audit sahifasining skrinshoti (narx o‘zgarishi va login_failed yozuvi ko‘ringan) bo‘lsin.
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.