You don't need a license code AT ALL. Go head and install Backpack CRUD on your machine - it's free and open-source, released under the MIT License.
Yes you can! Use Backpack CRUD v6, which is free & open-source, released under the MIT License.
In short - no, you cannot. Please use Backpack CRUD v6 instead, which is free & open-source, released under the MIT License.
Backpack PRO is a closed-source add-on, which requires payment in order to receive an access token. If you did include
backpack/pro as a dependency in your open-source software... your software would no longer be open-source. Everybody who installed your project/package would need to pay for Backpack PRO, to get access to it.
No - we're no longer giving away free licenses. But we have released Backpack CRUD v5 and v6 under MIT License, which means it's free & open-source. It has fewer features, but you can do absolutely anything you want with it.
First of all, run
composer update on your project. That will pull in the latest supported version of all your Backpack packages.
Then you should re-publish the JS and CSS assets. There are two ways to do that:
php artisan vendor:publish --provider="Backpack\CRUD\BackpackServiceProvider" --tag=public --force. Please note this will overwrite anything that's already there. This B solution has a downside: unused files are not removed. A few files Backpack no longer uses will still be in your public/packages folder, even though they're no longer used.
(B) If you have NOT touched you
public/packages folder, or placed anything custom inside it:
php artisan vendor:publish --provider="Backpack\CRUD\BackpackServiceProvider" --tag=public
php artisan backpack:filemanager:install
You can remove Backpack from your project pretty easily, if you decide to stop using it. You just have to do the opposite of the installation process:
# delete the files Backpack has placed inside your application rm -rf app/Http/Middleware/CheckIfAdmin.php rm -rf config/backpack rm -rf config/gravatar.php rm -rf public/packages rm -rf resources/views/errors rm -rf resources/views/vendor/backpack rm -rf routes/backpack # delete any CrudControllers you've created, so MAYBE: rm -rf app/Http/Controllers/Admin # delete any Requests you've created for your CrudControllers. # MAKE SURE YOU DON'T NEED ANYTHING IN THIS DIRECTORY ANYMORE. # You might have OTHER requests that are not Backpack-related. rm -rf app/Http/Requests # (MUST) remove other Backpack packages that you are using, like PRO, Editable Columns, DevTools etc: composer remove --dev backpack/devtools composer remove backpack/pro composer remove backpack/editable-columns etc... # After everything related to Backpack is deleted, just need to delete the crud! composer remove backpack/crud
That's it! If you've decided NOT to use Backpack, we'd be super-grateful if you could send us an email telling us WHY you didn't like Backpack, or it didn't fit your project. It might help us take Backpack in a different direction, one where you might want to use it. Thank you 🙏