Laravel Service Provider

Basic service provider mockup with utility functions to speedup packages deployment., _(*1)

PROJECT IS UNMAINTAINED, _(*2)

Our company dropped support of this package and started to use clean Laravel Service Providers since they are able to perform migrations without publishing., _(*3)

Installation

Simply install the service provider package with composer:, _(*4)

composer require cybercog/laravel-service-provider

Usage

Create service provider in your package and extend this one., _(*5)

<?php

namespace Vendor\Package;

use Cog\ServiceProvider\BaseServiceProvider;

class ServiceProvider extends BaseServiceProvider
{
    public function boot()
    {
        $this->setup(__DIR__)
             ->publishMigrations()
             ->publishConfig()
             ->publishViews()
             ->publishAssets()
             ->loadViews()
             ->loadTranslations()
             ->mergeConfig('package');
    }
}

Migration stubs

To create migrations you could add usual Laravel's migration file and place them in package's database/migrations directory., _(*6)

Migration files has specific naming convention 0001_create_my_table.stub:, _(*7)

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 .php replaced with .stub to prevent class names conflicts in package and application's migrations directory.

When you are publishing migrations:, _(*8)