Download the PHP package sebastienheyd/boilerplate-packager without Composer

Package manager for sebastienheyd/boilerplate.

This package will allow you to easily create and manage your own local packages for sebastienheyd/boilerplate.

Installation

Via Composer

Optionnal: publish configuration file

Usage

By default, a help is displayed when calling boilerplate:packager without any argument.

Create a new package

By default, every package will be generated using sebastienheyd/boilerplate-package-skeleton. Note that you can use a local path instead by setting the skeleton value in the configuration file.

You can also modify the default creation data (author, e-mail, description, license) by modifying the values in the configuration file

Or you can define the package name directly in the command line:

In this example, after asking some questions about author, email, description, license and resource, the command will load the skeleton package in a packages/my-vendor/my-package directory. Then, it will require the local package in your project, a symlink is created in the vendor directory pointing to the local package. All you have to do after that is to code in you freshly installed package.

Options

You can create a package with the option --dev to add the package to the require-dev section in composer.json

Require a package

You can require a package from packagist or by giving a git repository url.

This will clone the package in the packages folder and require it via composer.

Options

You can require a package with the option --dev to add the package to the require-dev section in composer.json

Remove a local package

You can remove a local package by using the remove command. If you called the command without a package name you will be asked to chose the package to remove :

You can also define directly the package name:

This will remove the local package from your project. The command will ask to confirm the deletion of the local folder.

List local package

This will display a table with all local packages, installed or not.

Generate files for crud

This command will generate templates, controllers, views, menus, translations for the tables generated by the package.

To do this, after creating your package with the create command, create the migrations in the package and then run them to generate the tables in the database. After that, run the crud command indicating the package in which the migrations are located.

You can also define directly the package name:

It is possible that the foreign keys point to a model that is not in the package. The command will then ask you to enter the namespace related to the model needed for the relationship.

Be careful, if files already exist in the package they will be overwritten.

You can generate specified resources by using the option --only and one or many of the following keywords : model, routes, lang, permissions, controller, menu, views

Sometimes your package will use prefixed tables, to avoid generating files with the prefix you can remove it by using the option --prefix

Test and coding standard

This package is delivered with tests, to launch tests just launch:

Coding standard can also be checked by using phpcs:

Contributing

Please see contributing.md for details.

Security

If you discover any security related issues, please email author email instead of using the issue tracker.

Credits

• Sébastien HEYD
• All Contributors

License

MIT license. Please see the license file for more information.