## Publishing Files

If you need even more control over your application, LAP comes with several publishing commands that make this a breeze. Some of these files are already published upon installation.

### Config

    php artisan vendor:publish --provider="Kjjdion\LaravelAdminPanel\LapServiceProvider" --tag="config"

This publishes the config file to `config/lap.php`.

### Public Assets

    php artisan vendor:publish --provider="Kjjdion\LaravelAdminPanel\LapServiceProvider" --tag="public"

This publishes all of the public assets, such as CSS, JS, and fonts, to `public/*.*`.

### Views

    php artisan vendor:publish --provider="Kjjdion\LaravelAdminPanel\LapServiceProvider" --tag="views"

This publishes all of the package view files to `resources/views/vendor/lap/*.*`.

### BackendController

    php artisan vendor:publish --provider="Kjjdion\LaravelAdminPanel\LapServiceProvider" --tag="backend_controller"

This publishes the default `BackendController` into `app/Http/Controllers/Admin`.

### CRUD Template Stubs

    php artisan vendor:publish --provider="Kjjdion\LaravelAdminPanel\LapServiceProvider" --tag="crud_stubs"

This publishes the default CRUD template stubs to `resources/stubs/crud/default/*.*`. This is useful for creating your own CRUD stub templates.

### Migrations

    php artisan vendor:publish --provider="Kjjdion\LaravelAdminPanel\LapServiceProvider" --tag="migrations"

This publishes all of the package migration files to `database/migrations/*.*`. Useful if you need more control over the package migrations.

Remember that you can also use `--force` at the end of each command to replace any existing files you have. This will effectively revert them back to the package defaults.