misaf / vendra
The skeleton application for the Vendra framework.
Requires
- php: ^8.3
- bezhansalleh/filament-panel-switch: ^3.1
- dedoc/scramble: ^0.13.26
- dutchcodingcompany/filament-developer-logins: ^2.1
- filament/filament: ^5.6.6
- filament/spatie-laravel-settings-plugin: ^5.6.6
- flowframe/laravel-trend: >=0.5
- internachi/modular: ^3.0.2
- laravel/framework: ^13.13
- laravel/horizon: ^5.47.2
- laravel/sanctum: ^4.3.2
- laravel/tinker: ^3.0.2
- misaf/vendra-activity-log: dev-master
- misaf/vendra-affiliate: dev-master
- misaf/vendra-api: dev-master
- misaf/vendra-blog: dev-master
- misaf/vendra-blog-api: dev-master
- misaf/vendra-currency: dev-master
- misaf/vendra-custom-page: dev-master
- misaf/vendra-faq: dev-master
- misaf/vendra-faq-api: dev-master
- misaf/vendra-jalali: dev-master
- misaf/vendra-language: dev-master
- misaf/vendra-multimedia: dev-master
- misaf/vendra-multimedia-api: dev-master
- misaf/vendra-newsletter: dev-master
- misaf/vendra-permission: dev-master
- misaf/vendra-product: dev-master
- misaf/vendra-product-api: dev-master
- misaf/vendra-tagger: dev-master
- misaf/vendra-tenant: dev-master
- misaf/vendra-testing: dev-master
- misaf/vendra-transaction: dev-master
- misaf/vendra-user: dev-master
- misaf/vendra-user-profile: dev-master
- owenvoke/blade-fontawesome: ^3.2.2
Requires (Dev)
- ergebnis/composer-normalize: ^2.52
- fakerphp/faker: ^1.24.1
- fruitcake/laravel-debugbar: ^4.3.0
- larastan/larastan: ^3.10.0
- laravel/boost: ^2.4.8
- laravel/pail: ^1.2.5
- laravel/pao: ^1.0.6
- laravel/pint: ^1.27
- mockery/mockery: ^1.6.12
- nunomaduro/collision: ^8.9.4
- orchestra/testbench: ^11.1
- pestphp/pest: ^4.7.2
- pestphp/pest-plugin-laravel: ^4.1
This package is auto-updated.
Last update: 2026-06-09 11:15:25 UTC
README
Vendra is a modular Laravel 12 application for e-commerce and marketplace use cases.
Tech Stack
- PHP 8.2+
- Laravel 12
- Filament 5
- Livewire 4
- Pest 4
- Tailwind CSS 4
Requirements
- PHP 8.2 or newer
- Composer
- Node.js and npm
- MySQL (or another configured Laravel-supported database)
Quick Start
composer install cp .env.example .env php artisan key:generate php artisan migrate npm install npm run build
To populate a fresh installation with demo data, run these commands after migrating the database. Without this step, the website can run but will not have demo content:
php artisan db:seed --module=vendra-tenant --class=DemoContentSeeder php artisan vendra-permission:seed vendra all php artisan vendra-user:seed vendra all php artisan vendra-currency:seed vendra all php artisan vendra-product:seed vendra all php artisan vendra-faq:seed vendra all php artisan vendra-custom-page:seed vendra all php artisan vendra-tagger:seed vendra all php artisan vendra-language:seed vendra all
For local development:
composer dev
This starts the web server, queue listener, logs, and Vite in watch mode.
Repository Structure
app/main application codeapp-modules/local path packages (modular features)config/framework and package configurationdatabase/migrations, factories, seedersresources/views, frontend assets
Modular Packages (app-modules/*)
This project uses Composer path repositories:
{
"repositories": [
{
"type": "path",
"url": "app-modules/*",
"options": {
"symlink": true
}
}
]
}
Each package in app-modules/* can be developed locally and consumed by the app as a Composer dependency.
Typical package workflow:
- Edit package code inside
app-modules/<package-name>. - Ensure the package is required in root
composer.json. - Run
composer update <vendor/package>(orcomposer dump-autoload) when needed. - Run tests from the root app and/or package scope.
SMS Gateway Packages in This Workspace
misaf/laravel-sms-gateway(core manager/facade/contracts)misaf/laravel-sms-gateway-ghasedakmisaf/laravel-sms-gateway-sunwaymisaf/laravel-sms-gateway-kavenegarmisaf/laravel-sms-gateway-smsir
See app-modules/laravel-sms-gateway/README.md for full usage and extensibility details.
Useful Commands
# Test suite composer test # Laravel tests directly php artisan test --compact # Code style vendor/bin/pint --dirty --format agent # Static analysis (if configured) vendor/bin/phpstan analyse
Troubleshooting
- If package changes are not reflected, run
composer dump-autoload. - If provider discovery seems stale, run
php artisan package:discover. - If configuration values look outdated, run
php artisan config:clear. - If frontend changes do not appear, run
npm run devornpm run build.
License
MIT. See LICENSE.