There's nothing special about add-ons. They are simple Composer packages.
But for consistency, we recommend you follow our simple folder structure. Our rule of thumb: organize your src folder like it were a Laravel application. We do this because it's easier for users to understand how the package works, and it makes it easy to copy-paste the code inside their apps and modify, for complicated use cases. That way, add-ons can be kept super-simple, with everybody adding functionality in their own apps. Example folder structure:
Requirements:
We're going to use the Backpack demo project to create a new package. Follow the instructions in the Installation chapter.
Any Laravel & Backpack app would work. But since you're going to require packages that you only need during package development, and make various changes to app files, we recommended you create the package using a Backpack demo. After the package is online (with zero functionality), you will install it in a real application, and modify it right there, in the vendor folder. You will then delete this Backpack demo project.
We're going to use Jeroen-G/laravel-packager to generate a new package. Follow the instructions in the Installation chapter.
Next up, decide what your vendor name will be. This is NOT the package name, it's the name all your packages will reside under. For example, Laravel uses "laravel". Backpack for Laravel uses "backpack". Jeffrey Way uses "way". If unsure, use your github username for the vendor name. That's what people usually do, if they don't run a company / brand.
Then decide what your package name will be. Ex: newscrud, usermanager, etc.
Then run:
php artisan packager:new myvendor mypackageThis will create a /packages/ folder in your root directory, where your package will be stored, so you can build it. It will also pull a very basic package template, created by thephpleague. Everything you have right now is in packages/myvendor/mypackage - check it out.
Now let's customise it and add some boilerplate code, everything that most Laravel Packages will need. Replace everything you need in composer.json, CHANGELOG.md, CONTRIBUTING.md, LICENSE.md, README.md. Make it yours.
If you want to use Laravel package auto-discovery (and why wouldn't you), make sure to include the Laravel providers section in your composer.json's extra section, like so:
"extra": {
"branch-alias": {
"dev-master": "1.0-dev"
},
"laravel": {
"providers": [
"Backpack\\NewsCRUD\\NewsCRUDServiceProvider"
]
}
}In /src/ you'll find your service provider. That's where your package's logic is, but it's empty. Use this Service Provider template and replace League with your myvendor and Skeleton with your mypackage. Your package will probably need some Controllers, routes and config files.
Here are a few commands that could help you do that:
# make sure everything is inside your src folder
cd src/
# to create a controller
echo "<?php " >app/Http/Controllers/ControllerName.php
# to create a request file
echo "<?php " >app/Http/Requests/EntityRequest.php
# to create a route file
echo "<?php " >routes/mypackage.php
# to create a config file
echo "<?php " >config/mypackage.php
# to create a views folder
mkdir resources/views/You use the routes, config and controller files just like you use the ones in your application. Nothing changes there. But remember that all classes should have the package's namespace:
namespace MyVendor\MyPackage\Http\Controllers;Add your service provider to your app's /config/app.php
If not, add it:
"MyVendor\MyPackage\MyPackageServiceProvider",Check that you autoload your package in composer.json:
"autoload" : {
"psr-4": {
"Domain\\PackageName\\": "packages/Domain/PackageName/src"
}
},Let's recreate the autoload
cd ../../../..
composer dump-autoloadIf you have a config file to publish, do:
php artisan vendor:publishNow test it. Start by doing a dd('testing) in your service provider's boot() method. If your package is working fine, I recommend you put it online first, even before it does anything useful. You'll get the setup out of the way, and be able to focus on code. Plus, you'll be able to install it in a real Backpack application, and edit it from the vendor/myvendor/mypackage folder (and push to your git remote).
cd packages/domain/packagename/
git init
git add .
git commit -m "first commit"Create a new GitHub repository.
git remote add origin [email protected]:yourusername/yourrepository.git
git push -u origin master
git tag -a 1.0.0 -m 'First version'
git push --tagsTags are the way you will version your package, so it's important you do it. People will only be able to get updates if you tag them.
On Packagist.org, submit a new package. Enter your package's GitHub URL and click Check. If any errors occur, follow the onscreen instructions.
When you're done, you'll be taken to your packagist page, where you'll probably get a notice like this:
This package is not auto-updated. Please set up the GitHub Service Hook for Packagist so that it gets updated whenever you push!
Let's take care of that. Click that link, get your API token and go to your package's GitHub page, in Settings / Webhooks & Services / Add a new service. Search for Packagist. Enter your username and the token and hit Submit. Your error in Packagist should disappear in 5–10 minutes.
Congrats! You now have a working package online. You can now require it with composer.
We've instructed you to create the package in a disposable backpack-demo install. If you've done so, you can now install your package in your real project:
composer require myvendor/mypackage --prefer-sourceUsing the prefer-source flag will actually clone the git repo inside your vendor/myvendor/mypackage directory. So you can do:
cd /vendor/myvendor/mypackage
git checkout masterThen after each change you want to publish, you would mark that change in your CHANGELOG.md file and do:
git pull origin master
git add .
git commit -am "fixes #14189 - some problem or feature with an id"
git tag 1.0.3
git push origin master --tagsThat's it. Go build your package! If you end up with something you like, please share it with the community in the Gitter Chatroom, and add it to the Community Add-Ons page, so other people know about it (login, then click Edit in the top-right corner of the page).
You can now delete the Backpack project, and the database you've created for it (if any).
For extra reading credits, these are the resources we've used to create this guide:
Then you'll love our premium add-ons - productivity tools and tons of new features.