- Upgrade Guide
- Installation
- Configuration
- Naming Convension
- Folder Structure
- Creating Module
- Artisan Commands
- Facades
- Entity
- Auto Scan Vendor Directory
- Publishing Modules
pingpong/modules is a laravel package which created to manage your large laravel app using modules. Module is like a laravel package, it have some views, controllers or models. This package is supported and tested in both Laravel 4 and Laravel 5.
If you have been updated to version 2.0.18, please read this release note.
Previously, we add two service provider from this package. In version 2.0.5, we just need register one service provider. Now, we can remove Pingpong\Modules\Providers\BootstrapServiceProvider from providers array, because now it service provider is registered automatically by Pingpong\Modules\ModulesServiceProvider.
If upgrade your Laravel app from Laravel 4 to Laravel 5, there is a few things to do if you are using this package. You will receive some kind errors about config not loaded. To fix this issue, please follow this instruction.
- If you publish the package's configuration file, you need to move the config file from
app/config/packages/pingpong/modules/config.phptoapp/config/modules.php. - If you are not publish the package's configuration file and you want to publish the config file, just run
php artisan vendor:publishcommand and you are done.
New configuration file. This breaking change affected if you publish the configuration file from this package. To fix this issue, create new config file called config.php in your app/config/packages/pingpong/modules/ directory. Next move the array contents from paths.php file to paths array in new configuration file.
Your config file will looks like this.
To install through composer, simply put the following in your composer.json file:
{
"require": {
"pingpong/modules": "~2.1"
}
}And then run composer install to fetch the package.
You could also simplify the above code by using the following command:
composer require "pingpong/modules:~2.1"
Next add the following service provider in config/app.php.
'providers' => array(
'Pingpong\Modules\ModulesServiceProvider',
),Next, add the following aliases to aliases array in the same file.
'aliases' => array(
'Module' => 'Pingpong\Modules\Facades\Module',
),
Next publish the package's configuration file by run :
php artisan vendor:publish
By default controllers, entities or repositories not loaded automatically. You can autoload all that stuff using psr-4. For example :
{
"autoload": {
"psr-4": {
"App\\": "app/",
"Modules\\": "modules/"
}
}
}modules- Used for save the generated modules.assets- Used for save the modules's assets from each modules.migration- Used for save the modules's migrations if you publish the modules's migrations.generator- Used for generate modules folders.scan- Used for allow to scan other folders.enabled- Iftrue, the package will scan other paths. By default the value isfalsepaths- The list of path which can scanned automatically by the package.composervendor- Composer vendor name.author.name- Composer author name.author.email- Composer author email.
cacheenabled- Iftrue, the scanned modules (all modules) will cached automatically. By default the value isfalsekey- The name of cache.lifetime- Lifetime of cache.
To create a new module you can simply run :
php artisan module:make <module-name>
<module-name>- Required. The name of module will be created.
Create a new module
php artisan module:make Blog
Create multiple modules
php artisan module:make Blog User Auth
By default if you create a new module, that will add some resources like controller, seed class or provider automatically. If you don't want these, you can add --plain flag, to generate a plain module.
php artisan module:make Blog --plain
#OR
php artisan module:make Blog -pBecause we are autoloading the modules using psr-4, we strongly recommend using StudlyCase convension.
laravel-app/
app/
bootstrap/
vendor/
modules/
├── Blog/
├── Assets/
├── Config/
├── Console/
├── Database/
├── Migrations/
├── Seeders/
├── Entities/
├── Http/
├── Controllers/
├── Middleware/
├── Requests/
├── routes.php
├── Providers/
├── BlogServiceProvider.php
├── Resources/
├── lang/
├── views/
├── Repositories/
├── Tests/
├── composer.json
├── module.json
├── start.php
Create new module.
php artisan module:make blog
Use the specified module. Please see #26.
php artisan module:use blogShow all modules in command line.
php artisan module:list
Create new command for the specified module.
php artisan module:make-command CustomCommand blog
php artisan module:make-command CustomCommand --command=custom:command blog
php artisan module:make-command CustomCommand --namespace=Modules\Blog\Commands blog
Create new migration for the specified module.
php artisan module:make-migration create_users_table blog
php artisan module:make-migration create_users_table --fields="username:string, password:string" blog
php artisan module:make-migration add_email_to_users_table --fields="email:string:unique" blog
php artisan module:make-migration remove_email_from_users_table --fields="email:string:unique" blog
php artisan module:make-migration drop_users_table blog
Rollback, Reset and Refresh The Modules Migrations.
php artisan module:migrate-rollback
php artisan module:migrate-reset
php artisan module:migrate-refresh
Rollback, Reset and Refresh The Migrations for the specified module.
php artisan module:migrate-rollback blog
php artisan module:migrate-reset blog
php artisan module:migrate-refresh blog
Create new seed for the specified module.
php artisan module:make-seed users blog
Migrate from the specified module.
php artisan module:migrate blog
Migrate from all modules.
php artisan module:migrate
Seed from the specified module.
php artisan module:seed blog
Seed from all modules.
php artisan module:seed
Create new controller for the specified module.
php artisan module:make-controller SiteController blog
Publish assets from the specified module to public directory.
php artisan module:publish blog
Publish assets from all modules to public directory.
php artisan module:publish
Create new model for the specified module.
php artisan module:make-model User blog
php artisan module:make-model User blog --fillable="username,email,password"
Create new service provider for the specified module.
php artisan module:make-provider MyServiceProvider blog
Publish migration for the specified module or for all modules.
This helpful when you want to rollback the migrations. You can also run php artisan migrate instead of php artisan module:migrate command for migrate the migrations.
For the specified module.
php artisan module:publish-migration blog
For all modules.
php artisan module:publish-migration
Enable the specified module.
php artisan module:enable blog
Disable the specified module.
php artisan module:disable blog
Generate new middleware class.
php artisan module:make-middleware Auth
Update dependencies for the specified module.
php artisan module:update ModuleName
Update dependencies for all modules.
php artisan module:update
Show the list of modules.
php artisan module:list
Get all modules.
Module::all();Get all cached modules.
Module::getCached()Get ordered modules. The modules will be ordered by the priority key in module.json file.
Module::getOrdered();Get scanned modules.
Module::scan();Find a specific module.
Module::find('name');
// OR
Module::get('name');Find a module, if there is one, return the Module instance, otherwise throw Pingpong\Modules\Exeptions\ModuleNotFoundException.
Module::findOrFail('module-name');Get scanned paths.
Module::getScanPaths();Get all modules as a collection instance.
Module::toCollection();Get modules by the status. 1 for active and 0 for inactive.
Module::getByStatus(1);Check the specified module. If it exists, will return true, otherwise false.
Module::has('blog');Get all enabled modules.
Module::enabled();Get all disabled modules.
Module::disabled();Get count of all modules.
Module::count();Get module path.
Module::getPath();Register the modules.
Module::register();Boot all available modules.
Module::boot();Get all enabled modules as collection instance.
Module::collections();Get module path from the specified module.
Module::getModulePath('name');Get assets path from the specified module.
Module::getAssetPath('name');Get config value from this package.
Module::config('composer.vendor');Get used storage path.
Module::getUsedStoragePath();Get used module for cli session.
Module::getUsedNow();
// OR
Module::getUsed();Set used module for cli session.
Module::setUsed('name');Get modules's assets path.
Module::getAssetsPath();Get asset url from specific module.
Module::asset('blog:img/logo.img');Install the specified module by given module name.
Module::install('pingpong-modules/hello');Update dependencies for the specified module.
Module::update('hello');Get an entity from a specific module.
$module = Module::find('blog');Get module name.
$module->getName();
Get module name in lowercase.
$module->getLowerName();
Get module name in studlycase.
$module->getStudlyName();
Get module path.
$module->getPath();
Get extra path.
$module->getExtraPath('Assets');
Disable the specified module.
$module->enable();
Enable the specified module.
$module->disable();
Delete the specified module.
$module->delete();
When you create a new module it also registers new custom namespace for Lang, View and Config. For example, if you create a new module named blog, it will also register new namespace/hint blog for that module. Then, you can use that namespace for calling Lang, View or Config. Following are some examples of its usage:
Calling Lang:
Lang::get('blog::group.name');Calling View:
View::make('blog::index')
View::make('blog::partials.sidebar')Calling Config:
Config::get('blog.name')Have you created a laravel modules? Yes, I've. Then, I want to publish my modules. Where do I publish it? That's the question. What's the answer ? The answer is Packagist. In pingpong/modules version >= 1.2.0, when you generate a module, you will see there is a new file generated called composer.json.
By default the vendor directory is not scanned automatically, you need to update the configuration file to allow that. Set scan.enabled value to true. For example :
// file config/modules.php
return [
//...
'scan' => [
'enabled' => true
]
//...
]You can verify the module has been installed using module:list command:
php artisan module:list
After creating a module and you are sure your module module will be used by other developers. You can push your module to github or bitbucket and after that you can submit your module to the packagist website.
You can follow this step to publish your module.
- Create A Module.
- Push the module to github.
- Submit your module to the packagist website. Submit to packagist is very easy, just give your github repository, click submit and you done.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent
