mirkoschmidt/gitlab
Composer 安装命令:
composer require mirkoschmidt/gitlab
包简介
A GitLab bridge for Laravel
README 文档
README
A GitLab bridge for Laravel.
// Fetch projects. $gitlab->api('projects')->all(); // Create issues. $gitlab->api('issues')->create($id, $params); // Want to use the facade? GitLab::api('users')->show($id);
Installation
Laravel GitLab is decoupled from any library sending HTTP requests (like Guzzle), instead it uses an abstraction called HTTPlug which provides the http layer used to send requests to exchange rate services. This gives you the flexibility to choose what HTTP client and PSR-7 implementation you want to use.
Read more about the benefits of this and about what different HTTP clients you may use in the HTTPlug documentation. Below is an example using Guzzle 6:
$ composer require vinkla/gitlab php-http/guzzle6-adapter
Add the service provider to config/app.php in the providers array, or if you're using Laravel 5.5, this can be done via the automatic package discovery.
Vinkla\GitLab\GitLabServiceProvider::class
If you want you can use the facade. Add the reference in config/app.php to your aliases array.
'GitLab' => Vinkla\GitLab\Facades\GitLab::class
Configuration
Laravel GitLab requires connection configuration. To get started, you'll need to publish all vendor assets:
$ php artisan vendor:publish
This will create a config/gitlab.php file in your app that you can modify to set your configuration. Also, make sure you check for changes to the original config file in this package between releases.
Default Connection Name
This option default is where you may specify which of the connections below you wish to use as your default connection for all work. Of course, you may use many connections at once using the manager class. The default value for this setting is main.
GitLab Connections
This option connections is where each of the connections are setup for your application. Example configuration has been included, but you may add as many connections as you would like.
Usage
GitLabManager
This is the class of most interest. It is bound to the ioc container as gitlab and can be accessed using the Facades\GitLab facade. This class implements the ManagerInterface by extending AbstractManager. The interface and abstract class are both part of Graham Campbell's Laravel Manager package, so you may want to go and checkout the docs for how to use the manager class over at that repository. Note that the connection class returned will always be an instance of GitLab\Client.
Facades\GitLab
This facade will dynamically pass static method calls to the gitlab object in the ioc container which by default is the GitLabManager class.
GitLabServiceProvider
This class contains no public methods of interest. This class should be added to the providers array in config/app.php. This class will setup ioc bindings.
Examples
Here you can see an example of just how simple this package is to use. Out of the box, the default adapter is main. After you enter your authentication details in the config file, it will just work:
// You can alias this in config/app.php. use Vinkla\GitLab\Facades\GitLab; GitLab::api('projects')->all(); // We're done here - how easy was that, it just works! GitLab::api('users')->all(true); // This example is simple and there are far more methods available.
The GitLab manager will behave like it is a GitLab\Client. If you want to call specific connections, you can do that with the connection method:
use Vinkla\GitLab\Facades\GitLab; // Writing this… GitLab::connection('main')->api('projects')->all(); // …is identical to writing this GitLab::api('projects')->all(); // and is also identical to writing this. GitLab::connection()->api('projects')->all(); // This is because the main connection is configured to be the default. GitLab::getDefaultConnection(); // This will return main. // We can change the default connection. GitLab::setDefaultConnection('alternative'); // The default is now alternative.
If you prefer to use dependency injection over facades like me, then you can inject the manager:
use Vinkla\GitLab\GitLabManager; class Foo { protected $gitlab; public function __construct(GitLabManager $gitlab) { $this->gitlab = $gitlab; } public function bar() { $this->gitlab->api('users')->all(true); } } App::make('Foo')->bar();
Documentation
There are other classes in this package that are not documented here. This is because the package is a Laravel wrapper of the official GitLab package.
License
mirkoschmidt/gitlab 适用场景与选型建议
mirkoschmidt/gitlab 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 16 次下载、GitHub Stars 达 0, 最近一次更新时间为 2018 年 02 月 14 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「api」 「git」 「laravel」 「gitlab」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 mirkoschmidt/gitlab 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 mirkoschmidt/gitlab 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 mirkoschmidt/gitlab 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Easily manage git hooks in your composer config
MediaWiki extension that allows embedding external content, specified by URL, into your wiki pages
Nagios plugin to verify a git repository.
A PSR-7 compatible library for making CRUD API endpoints
GitHub Webhook Listener with plugin-based API for creating your own triggerered actions
This project will create a WordPress base installation using wp-cli/wp-cli package and using vlucas/phpdotenv package to expose configuration values in PHP $_ENV super global.
统计信息
- 总下载量: 16
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 2
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2018-02-14
