Download the PHP package rodrigobutta/laravel-attachable-modules without Composer
On this page you can find all versions of the php package rodrigobutta/laravel-attachable-modules. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download rodrigobutta/laravel-attachable-modules
More information about rodrigobutta/laravel-attachable-modules
Files in rodrigobutta/laravel-attachable-modules
Package laravel-attachable-modules
Short Description Make your project scalable with isolated modules
License MIT
Homepage https://github.com/rodrigobutta/laravel-attachable-modules
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-attachable-modules
Laravel Attachable Modules
Make your project scalable with isolated modules
How it works
A project will be made of modules, for example, you may want a Products module and a Users module, in wich case your project structure will have this: \App\Modules\Project** \App\Modules\User**
Where Project an User are the respective folders for each module and will contain every needed file inside (no file should be spread outside this folder besides config or database matter files)
Inside every module folder, there should be a Service Provider that we will call Boot Service Provider. The boot service provider file is where a module is defined, with its namespaces, views, configs, langs, etc.
Laravel Attachable Modules will search for every Boot Service Provider file and use it to load every module to the project. Please refer to the config file to set this logic up (if you wont be usign the default one).
Theres a demo module inside this package ("demos") that has the needed structure and works with RodrigoButta/laravel-admin for handling the backend in a bunch of lines. But of course you can get rid of that and user the module like a boilerplate.
Installation
composer.json:
terminal:
config/app.php:
terminal:
config/attachable-modules.php
- modules_folder_path: path where modules are located (each module should have its own folder, with the boot provider and any files it needs to run)
- module_boot_provider_prefix: expected prefix for the boot service provider file
- module_boot_provider_suffix: expected suffix for the boot service provider file (without the .php extension)
Adding a module
So easy!
1) Copy the module folder inside app\Modules\ (or the folder you've defined for storing modules)
2) terminal:
3) The module is now beign called. Depending on the module architecture, you should know how to test or acces its funcions.
