Download the PHP package llama-laravel/modules without Composer

Laravel-Modules

• Upgrade Guide
• Installation
• Configuration
• Creating Module
• Artisan Commands
• Facades
• Entity
• Auto Scan Vendor Directory
• Publishing Modules

llama-laravel/modules is a laravel package which created to manage your large laravel app using modules. Module is like a laravel package, it has some views, controllers or models.

This package is supported and tested in Laravel 5.

This package was inspired by nwidart/laravel-modules.

Upgrade Guide

Installation

Quick

To install through composer, simply run the following command:

Add Service Provider

Next add the following service provider in config/app.php.

Next, add the following aliases to aliases array in the same file.

Next publish the package's configuration file by running:

Autoloading

By default controllers, entities or repositories are not loaded automatically. You can autoload your modules using psr-4. For example:

After that, you must run statement below for dumps the autoloader:

Configuration

• 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.
• seed - Used for save the modules's seeds if you publish the modules's seeds.
• generator - Used for generate modules folders.
• scan - Used for allow to scan other folders.
• enabled - If true, the package will scan other paths. By default the value is false
• paths - The list of path which can scanned automatically by the package.
• composer
• vendor - Composer vendor name.
• author.name - Composer author name.
• author.email - Composer author email.
• cache
• enabled - If true, the scanned modules (all modules) will cached automatically. By default the value is false
• key - The name of cache.
• lifetime - Lifetime of cache.

Creating A Module

To create a new module, you can simply run:

• <module-name> - Required. The name of module will be created.

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.

Naming Convention

Because we are autoloading the modules using psr-4, we strongly recommend using StudlyCase convension.

Folder Structure

Artisan Commands

You must be setting up modules folder for first use

Create new module.

Use the specified module.

Show all modules in command line.

Create new command for the specified module.

Create new migration for the specified module.

Rollback, Reset and Refresh The Modules Migrations.

Rollback, Reset and Refresh The Migrations for the specified module.

Migrate from the specified module.

Migrate from all modules.

Create new seeder for the specified module.

Seed from the specified module.

Seed from all modules.

Create new controller for the specified module.

Publish assets from the specified module to public directory.

Publish assets from all modules to public directory.

Create new model for the specified module.

Create new service provider for the specified module.

Create new policy for the specified module.

Create new route provider for the specified module.

Create new form request for the specified module.

Create new event for the specified module.

Create new job for the specified module.

Create new listener for the specified module.

Create new middleware for the specified module.

Create new mail for the specified module.

Create new notification for the specified module.

Enable the specified module.

Disable the specified module.

Update dependencies for the specified module.

Update dependencies for all modules.

Show the list of modules.

Facades

Using Model Factories

Normally, you can use model factories to conveniently generate large amounts of database records. I have defined new way to writing seeder for the specified module.

Get all modules.

Get all cached modules.

Get ordered modules. The modules will be ordered by the priority key in module.json file.

Get scanned modules.

Find a specific module.

Find a module, if there is one, return the Module instance, otherwise throw Llama\Modules\Exeptions\ModuleNotFoundException.

Get scanned locations.

Get all modules as a collection instance.

Get modules by the status. 1 for active and 0 for inactive.

Check the specified module. If it exists, will return true, otherwise false.

Get all enabled modules.

Get all disabled modules.

Get count of all modules.

Get module path.

Register the modules.

Boot all available modules.

Get all enabled modules as collection instance.

Get module path from the specified module.

Get assets path from the specified module.

Get config value from this package.

Get used storage path.

Get used module for cli session.

Set used module for cli session.

Get modules's assets path.

Get modules's namespace.

Get asset url from specific module.

Install the specified module by given module name.

Update dependencies for the specified module.

Entity

Get an entity from a specific module.

Get module name.

Get module name in lowercase.

Get module name in studlycase.

Get module path.

Get extra path.

Disable the specified module.

Enable the specified module.

Delete the specified module.

Get namespace specified module.

Custom Namespaces

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:

Calling View:

Calling Config:

Publishing Modules

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.

Auto Scan Vendor Directory

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:

You can verify the module has been installed using module:list command:

Publishing Modules

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.

1. Create A Module.
2. Push the module to github.
3. Submit your module to the packagist website.

Submit to packagist is very easy, just give your github repository, click submit and you done.

Credits

• XuaNguyen
• All Contributors

About XuaNguyen

XuaNguyen is a freelance web developer specialising on the laravel framework.

License

The MIT License (MIT). Please see License File for more information.