Download the PHP package jkuchynka/laravel-modular without Composer
On this page you can find all versions of the php package jkuchynka/laravel-modular. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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-modular
Laravel Modular
Requires: Laravel 8.0^
This is a WIP. A lot is changing rapidly as we work towards a stable release. But by all means feel free to give it a try and provide feedback. We're getting close, and below we will detail exactly what's not working and what's coming up in development.
Why use this package?
This package was created to make it easier to use Laravel in a modular setup. You can use a modular pattern with out of the box Laravel, but will run into issues and annoyances, such as:
- Console commands won't map to your modular directory structure
- A lot of Laravel assumes the default mixed directory structure
- Can't cleanly separate migrations, factories, seeders, routes or views
Because of the above, if you manage multiple sites with similar functionality, then copying things from one site to another is painful. Not to mention nearly impossible to keep them in sync. We're still working out the best method to tackle this issue.
A module is setup with the default Laravel directory structure, but only provides functionality related to the module. It can publish a config that can be modified by other modules or at the global level.
Installation
This package can be used in existing or new Laravel apps. If you want a fresh starting point, you can delete all the files in app/, that comes with a default Laravel installation. Modular provides this as a built-in module called "Base". You will need to edit a few files for Laravel to work correctly:
There's nothing special happening in the Modular\Base module, so you can safely create your own App\Base module and pull in these files as needed if you need to change them.
Artisan
All of the make commands work similar to default Laravel, but come with a module param, which creates the file in the right modular directory with the right namespaces etc. Pass the module name as the first param after each make command.
The goal here is to keep all make commands the same as default Laravel, while only changing namespaces and paths where needed. The only commands not currently working are for controllers and models
Coming Soon
A make:module command is in the works, which will create a new module in app/. This will be interactive so you can setup models, controllers, requests, etc... in one command. The new module directory structure can be modified by config/modular.php.
Custom stubs are also in the works. Use your own custom stubs and plug them into make commands.
Module
A module can simply be a directory in app/, with a NameModule.php class. This must extend Modular/Module and provide some required properties and methods. This module must be enabled in config/modular.php by adding the namespaced module with an array of config variables to overwrite.
Config
A module can provide its own config, which can be modified by other modules or the global app in config/modular.php. This can be useful to have flexible modules that can satisfy numerous use cases. For example, an Auth module can by default provide login by password, Google and Facebook, and you can specify which login methods to use in config/modular.php.
Examples for using a module config:
Routes
In the Module class, a module can provide routes. This method should return an array of groups, with child routes. A group defaults to a web route. Each child route is prefixed by the module key, unless the URI starts with a /, which considers the route as absolute. In this example, uses is omitted, so it would use the default module controller, e.g. PostController
