Download the PHP package cybercog/laravel-service-provider without Composer
On this page you can find all versions of the php package cybercog/laravel-service-provider. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download cybercog/laravel-service-provider
More information about cybercog/laravel-service-provider
Files in cybercog/laravel-service-provider
Package laravel-service-provider
Short Description Service Provider for Laravel 5 Packages
License BSD-3-Clause
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-service-provider
Laravel Service Provider
Basic service provider mockup with utility functions to speedup packages deployment.
PROJECT IS UNMAINTAINED
Our company dropped support of this package and started to use clean Laravel Service Providers since they are able to perform migrations without publishing.
Installation
Simply install the service provider package with composer:
Usage
Create service provider in your package and extend this one.
Migration stubs
To create migrations you could add usual Laravel's migration file and place them in package's database/migrations directory.
Migration files has specific naming convention 0001_create_my_table.stub:
- First 4 digits are required to save chronological order of migration files. This is a fix for a cases when your migration try to use other package's tables which are positioning below your migrations, because of static timestamp in name and ordering not by publish date, but by date of migration's development.
- Name of file is class name converted to
snake_case(as usual for migrations in Laravel). - Extenstion
.phpreplaced with.stubto prevent class names conflicts in package and application's migrations directory.
When you are publishing migrations:
- Prefixed digits are converting to current timestamp.
- Extension is swapping to
.php. - Prepared migration file moving to application's migrations directory.
