Download the PHP package benmag/gitlab without Composer
On this page you can find all versions of the php package benmag/gitlab. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download benmag/gitlab
More information about benmag/gitlab
Files in benmag/gitlab
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 gitlab
Laravel GitLab
Laravel GitLab is a GitLab bridge for Laravel using the GitLab API package.
Installation
Require this package, with Composer, in the root directory of your project.
Add the service provider to config/app.php in the providers array.
If you want you can use the facade. Add the reference in config/app.php to your aliases array.
Configuration
Laravel GitLab requires connection configuration. To get started, you'll need to publish all vendor assets:
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:
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:
If you prefer to use dependency injection over facades like me, then you can inject the manager:
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
Laravel GitLab is licensed under The MIT License (MIT).
All versions of gitlab with dependencies
illuminate/contracts Version 5.1.* || 5.2.* || 5.3.*
illuminate/support Version 5.1.* || 5.2.* || 5.3.*
graham-campbell/manager Version ^2.4
benmag/php-gitlab-api Version ^7.13