# Modules

Extract and modularize your code for maintainability. Essentially creates "mini-laravel" structures to organize your application.

# Installation

Simply install the package through Composer. From here the package will automatically register its service provider and Module facade.

composer require caffeinated/modules

# Config

To publish the config file, run the following:

php artisan vendor:publish --provider="Caffeinated\Modules\ModulesServiceProvider" --tag="config"

Below you will find the contents of the provided config file for reference.

<?php

return [

    /*
|--------------------------------------------------------------------------
| Default Location
|--------------------------------------------------------------------------
|
| This option controls the default module location that gets used while
| using this package. This location is used when another is not explicitly
| specified when exucuting a given module function or command.
|
*/ 'default_location' => 'app', /*
|--------------------------------------------------------------------------
| Locations
|--------------------------------------------------------------------------
|
| Here you may define all of the module locations for your application as
| well as their drivers and other configuration options. This gives you
| the flexibility to structure modules as you see fit in each location.
|
*/ 'locations' => [
'app' => [
'driver' => 'local',
'path' => app_path('Modules'),
'namespace' => 'App\\Modules\\',
'enabled' => true,
'provider' => 'ModuleServiceProvider',
'manifest' => 'module.json',
'mapping' => [ // Here you may configure the class mapping, effectivly
// customizing your generated default module structure. 'Config' => 'Config',
'Database/Factories' => 'Database/Factories',
'Database/Migrations' => 'Database/Migrations',
'Database/Seeds' => 'Database/Seeds',
'Http/Controllers' => 'Http/Controllers',
'Http/Middleware' => 'Http/Middleware',
'Providers' => 'Providers',
'Resources/Lang' => 'Resources/Lang',
'Resources/Views' => 'Resources/Views',
'Routes' => 'Routes'
],
],
], /*
|--------------------------------------------------------------------------
| Default Driver
|--------------------------------------------------------------------------
|
| Here you may specify the default module storage driver that should be
| used by the package. A "local" driver is available out of the box that
| uses the local filesystem to store and maintain module manifests.
|
*/ 'default_driver' => 'local', /*
|--------------------------------------------------------------------------
| Drivers
|--------------------------------------------------------------------------
|
| Here you may configure as many module drivers as you wish. Use the
| local driver class as a basis for creating your own. The possibilities
| are endless!
|
*/ 'drivers' => [
'local' => 'Caffeinated\Modules\Repositories\LocalRepository',
],
];

# Basic Usage

When it comes to larger applications, instead of mixing and matching your controllers, models, etc. across the various domains of your project, modules can group related logic together into a tidy "package". Out of the box, modules are stored in the app/Modules directory. Later on we'll go over how you can change this location or even add additional locations to store your modules.

# Creating Modules

Modules can be created by the use of the make:module Artisan command:

php artisan make:module Blog

This command will generate all the necessary files and folders to get you up and running quickly at app/Modules/Blog.

You'll notice that the structure of modules closely resemble the default Laravel folder structure. This is intentional and should feel immediately familiar to you. Nothing too scary here!

# Manifest

One of the important files that must be present at the root of every module, is the module's manifest file: module.json. This file contains the info and identification of your module. You may also use this to store module-specific settings if you wish. Let's look at the contents provided out of the box and go over each in detail:

{
"name": "Blog",
"slug": "blog",
"version": "1.0",
"description": "Only the best blog module in the world!",
}
Property Description
name * The human-readable name of your module.
slug * The slug of your module used to reference in commands and code.
version * The version of your module.
description * A simple description of your module.
order You may also optionally pass in the order in which your module is loaded. Defaults to 9001.

* These properties are required in every manifest.

Once you've made a change to a manifest file, you will need to re-optimize your module manifest cache. You can do this by running the following Artisan command:

php artisan module:optimize

# Service Providers

Just as the case with Laravel packages, service providers are the connection points between your module and Laravel. A service provider is responsible for binding things into Laravel's service container and information Laravel where to load module resources such as views, configuration, and localization files.

A ModuleServiceProvider and RouteServiceProvider is provided out of the box with some defaults configured for your module's localization, view, migration, configuration, factory, and route files. Feel free to modify these files or create your own service providers as needed.

You may generate a new provider via the make:module:provider command:

php artisan make:module:provider blog PublisherServiceProvider

NOTE

Be sure to register your custom service providers within your ModuleServiceProvider. Refer to Laravel's service provider documentation as needed.

# Migrations

We've extended Laravel's migrations system to make it easier to work with migrations for your modules. Particularly, you're able to run, rollback, reset, and refresh migrations for individual modules separate from your application (or other modules). This makes it super easy to work with modules during development.

# Generating Migrations

To create a module migration, use the make:module:migration Artisan command:

php artisan make:module:migration blog create_posts_table

The new migration will be placed in your defined migrations directory (by default this is Database/Migrations). Migrations follow the same workflow and structure as any other Laravel migration, so be sure to check out the documention on them here for reference.

# Running Migrations

To run all of your outstanding module migrations, execute the module:migrate Artisan command:

php artisan module:migrate

You may optionally specificy the exact module you'd like to run migrations against by passing through the slug:

php artisan module:migrate blog

Lastly, every module migrate command accepts the use of the --location flag to specify which module location to target.

# Rolling Back Migrations

To rollback the latest migration operation, you use the module:migrate:rollback command.

php artisan module:migrate:rollback

The rollback command also supports the step option to rollback a certain number of migrations:

php artisan module:migrate:rollback --step=5

You may also specify the module you wish to rollback, specifically:

php artisan module:migrate:rollback blog

The module:migrate:reset command will roll back all of your module migrations or the migrations of the module you pass through:

php artisan module:migrate:reset

php artisan module:migrate:reset blog

# Enabling Modules

Modules may be enabled either through the module:enable artisan command or through the facade with enable():

php artisan module:enable blog
Module::enable('blog');

# Disabling Modules

Modules may be disabled either through the module:disable artisan command or through the facade with disable():

php artisan module:disable blog
Module::disable('blog');

# Digging Deeper

# Locations

You may configure as many locations for your modules as necessary. For example, you may to split up your "core" modules from optional "add-on" modules.

The location configuration is found in the config/modules.php file under "locations". Here you may customize locations as needed. By default, the package is configured to store and reference modules from the app/Modules directory.

Each location may have its own configuration options on how you'd like to structure your modules:

Property Description
driver The module driver to use for this location.
path The root path where you wish to store modules for this location.
namespace The root namespace used when generating modules for this location.
enabled Whether or not modules are enabled by default or not in this location.
provider The master provider class name for modules in this location.
manifest The manifest filename for modules in this location. Must be a JSON file.
mapping The custom mapping of directories for modules in this location.

# Publishing Resources

Typically, you will need to publish your module's resources to the application's own directories. This will allow users of your module to easily override your default resources.

To publish your module's resources to the application, you may call the service provider's publishes method within the boot method of your service provider. The publishes method accepts an array of module paths and their desired publish locations. For example, to publish a config file for your blog module, you may do the following:

/**
* Perform post-registration booting of services.
*
* @return void
*/
public function boot()
{
$this->publishes([
module_path('blog', 'config/blog.php') => config_path('blog.php'),
]);
}

# Provided Middleware

The bundled Identify Module middleware provides the means to pull and store module manifest information within the session on each page load. This provides the means to identify routes from specific modules.

# Register

Simply register as a route middleware with a short-hand key in your app/Http/Kernel.php file.

protected $routeMiddleware = [
...
'module' => \Caffeinated\Modules\Middleware\IdentifyModule::class,
];

# Usage

Now, you may simply use the middleware key in the route options array. The IdentifyModule middleware expects the slug of the module to be passed along in order to locate and load the relevant manifest information.

Route::group(['prefix' => 'blog', 'middleware' => ['module:blog']], function() {
Route::get('/', function() {
dd(
'This is the Blog module index page.',
session()->all()
);
});
});

# Results

If you dd() your session, you'll see that you have a new module array key with your module's manifest information available.

"This is the Blog module index page."
array:2 [▼
"_token" => "..."
"module" => array:6 [▼
"name" => "Blog"
"slug" => "blog"
"version" => "1.0"
"description" => "This is the description for the Blog module."
"enabled" => true
"order" => 9001
]
]

# Helpers

Caffeinated Modules includes a handful of global "helper" PHP functions. These are used by the package itself; however, you are free to use them in your own code if you find them convenient.



# modules

The modules function returns a collection of all modules and their accompanying manifest information.

$modules = modules();

# module_path

The module_path function returns the fully qualified path to the specified module's directory. You may also use the module_path function to generate a fully qualified path to a file relative to the module:

$path = module_path('blog');

$path = module_path('blog', 'Http/Controllers/BlogController.php');

If your module is not found within your configured default location, you may pass a third option to specify the location:

$path = module_path('blog', 'Http/Controllers/BlogController.php', 'add-on');

# module_class

The module_class function returns the full namespace path of the specified module and class.

$namespace = module_class('blog', 'Http\Controllers\BlogController');

If your module is not found within your configured default location, you may pass a third option to specify the location:

$namespace = module_class('blog', 'Http\Controllers\BlogController', 'add-on');

# API Reference


# all

Get all modules, returned as a Collection.

$modules = Module::all();

# slugs

Get all modules, returned as a Collection.

$modules = Module::slugs();

# where

Find a module based on a where clause, returns a Collection.

$blogModule = Module::where('slug', 'blog');

# sortBy

Get all modules sorted by key in ascending order, returned as a Collection.

$modules = Module::sortBy('name');

# sortByDesc

Get all modules sorted by key in descending order, returned as a Collection.

$modules = Module::sortByDesc('name');

# exists

Check if given module exists, returns a Boolean.

if (Module::exists('blog')) {
// Do something with it
}

# count

Returns a count of all modules.

$count = Module::count();

# getManifest

Get a module's manifest contents, returned as a Collection.

$manifest = Module::getManifest('blog');

# get

Returns the given module manifest property value. If a value is not found, you may define a default value as the second parameter.

$name = Module::get('blog::post_limit', 15);

# set

Set the given module manifest property value.

Module::get('blod::description', 'This is a fresh new description of the blog module.');

# enabled

Gets all enabled modules, returned as a Collection.

$enabled = Module::enabled();

# disabled

Gets all disabled modules, returned as a Collection.

$disabled = Module::disabled();

# isEnabled

Checks if the given module is enabled, returns a Boolean.

if (Module::isEnabled('blog')) {
// Do something
}

# isDisabled

Checks if the given module is disabled, returns a Boolean.

if (Module::isDisabled('blog')) {
// Do something
}

# enable

Enable the given module.

Module::enable('blog');

# disable

Disable the given module.

Module::disable('blog);

laravel学习:模块化caffeinated的更多相关文章

  1. laravel的模块化是如何实现的

    laravel的模块化是如何实现的 在laravel提供的官方文档上,有一个这样的名词 服务提供者,文档中介绍了它在laravel框架中的角色,以及如何使用它,但却没有讲明服务提供者的本质--它是为了 ...

  2. 【 js 模块加载 】深入学习模块化加载(node.js 模块源码)

    一.模块规范 说到模块化加载,就不得先说一说模块规范.模块规范是用来约束每个模块,让其必须按照一定的格式编写.AMD,CMD,CommonJS 是目前最常用的三种模块化书写规范.  1.AMD(Asy ...

  3. Laravel学习笔记(三)--在CentOS上配置Laravel

    在Laravel框架上开发了几天,不得不说,确实比较优雅,处理问题逻辑比较清楚.     今天打算在CentOS 7上配置一个Laravel,之前都是在本机上开发,打算实际配置一下.     1)系统 ...

  4. Laravel学习笔记之Session源码解析(上)

    说明:本文主要通过学习Laravel的session源码学习Laravel是如何设计session的,将自己的学习心得分享出来,希望对别人有所帮助.Laravel在web middleware中定义了 ...

  5. 【 js 模块加载 】【源码学习】深入学习模块化加载(node.js 模块源码)

    文章提纲: 第一部分:介绍模块规范及之间区别 第二部分:以 node.js 实现模块化规范 源码,深入学习. 一.模块规范 说到模块化加载,就不得先说一说模块规范.模块规范是用来约束每个模块,让其必须 ...

  6. 《PHP框架Laravel学习》系列分享专栏

    <PHP框架Laravel学习>已整理成PDF文档,点击可直接下载至本地查阅https://www.webfalse.com/read/201735.html 文章 Laravel教程:l ...

  7. Laravel 学习 .env文件 getenv 获得环境变量的值

    Laravel 学习 .env文件 getenv 获得环境变量的值  我们还需要对应用的 .env 文件进行设置,为应用指定数据库名称 sample. .env . . . DB_DATABASE=s ...

  8. laravel学习之旅

    前言:之前写了二篇YII2.0的基本mvc操作,所以,打算laravel也来这一下 *安装现在一般都用composer安装,这里就不讲述了* 一.熟悉laravel (1)如果看到下面这个页面,就说明 ...

  9. laravel学习:主从读写分离配置的实现

    本篇文章给大家带来的内容是关于laravel学习:主从读写分离配置的实现,有一定的参考价值,有需要的朋友可以参考一下,希望对你有所帮助. 在DB的连接工厂中找到以下代码.../vendor/larav ...

  10. Laravel学习笔记之PHP反射(Reflection) (上)

    Laravel学习笔记之PHP反射(Reflection) (上) laravel php reflect 2.1k 次阅读  ·  读完需要 80 分钟 3 说明:Laravel中经常使用PHP的反 ...

随机推荐

  1. eclipse 显示行数

    在左侧添加断点的 地方右击 选择 Show Line Numbers

  2. YTU 2982: 奔跑吧,小明!

    2982: 奔跑吧,小明! 时间限制: 1 Sec  内存限制: 128 MB 提交: 36  解决: 2 题目描述 小明陷入一个充满陷阱的密道之中,现在他要逃脱这里!到达密道的出口即可离开这处绝境! ...

  3. Java String 和 new String()的区别

    Java String 和 new String()的区别 本文转自:http://www.cnblogs.com/heima-jieqi/archive/2012/04/10/2440086.htm ...

  4. CF上的3道小题(1)

    CF上的3道小题 终于调完了啊.... T1:CF702E Analysis of Pathes in Functional Graph 题意:你获得了一个n个点有向图,每个点只有一条出边.第i个点的 ...

  5. 【转】python文件打开方式详解——a、a+、r+、w+区别

    原文地址:http://blog.csdn.net/ztf312/article/details/47259805 第一步 排除文件打开方式错误: r只读,r+读写,不创建 w新建只写,w+新建读写, ...

  6. supervisor - Python进程管理工具

    经常会碰到要写一些守护进程,简单做法放入后台: shell> nohup python xxx.py & 偶尔这么做还可以接受,如果一堆这样的呢? 当然还有一个问题,就是各种服务,对应的 ...

  7. 网易云MongoDB分片集群(Sharding)服务已上线

    此文已由作者温正湖授权网易云社区发布. 欢迎访问网易云社区,了解更多网易技术产品运营经验. MongoDB sharding cluster(分片集群)是MongoDB提供的数据在线水平扩展方案,包括 ...

  8. 51nod 1239 欧拉函数之和【欧拉函数+杜教筛】

    和bzoj 3944比较像,但是时间卡的更死 设\( f(n)=\sum_{d|n}\phi(d) g(n)=\sum_{i=1}^{n}f(i) s(n)=\sum_{i=1}^{n}\phi(i) ...

  9. [App Store Connect帮助]七、在 App Store 上发行(2.1)设定价格与销售范围:为您的 App 设定价格

    在您提交 App 以供审核之前,您必须为您的 App 设定一个价格,该价格将用于 App Store 的所有地区.如果您没有<付费应用程序协议>,则只能选择免费. 必要职能:“帐户持有人” ...

  10. Rabbitmq笔记二

    消息何去何从 mandatory 和 immediate 是 channel . basicPublish 方法中的两个参数,它们都有 当消息传递过程中不可达目的地时将消息返回给生产者的功能. 当 m ...