If you can run Laravel 6.0, you can install Backpack. Backpack does not have additional requirements. For the following process, we assume:
you have a working installation of Laravel 6.0 (an existing project is fine, you don't need a fresh Laravel install);
you have put your database and email credentials in your .ENV file;
you can run the
composercommand from any directory (you have
composerregistered as a global command); if you need to run
php composer.pharor reference another directory, please remember to adapt the commands below to your configuration;
Install Core Packages
- Open your project folder in your terminal:
- In your project's main directory, install CRUD using composer:
composer require backpack/crud:"4.0.*" # you might also want to install these tools that help during development composer require backpack/generators --dev composer require laracasts/generators --dev
- Now run the installation commands for Backpack:
php artisan backpack:install
Note: If you'd also like to enable the file manager functionality, reply "yes" when the installer asks you. By default it lets users manage the
public/uploads directory, but you can change that in the
elfinder.php config file. Most of the times it is not recommended to give your admins power over file structure - not even their uploads alone. So
elfinder does not come installed by default.
- [Optional] You should now:
- Change configuration values in
config/backpack/base.phpto make the admin panel your own. Backpack is white label, so you can change everything: menu color, project name, developer name etc.
- If your User model has been moved (it is not
App\User.php, please go change
App\Models\BackpackUser.phpand make sure it extends the correct user model;
- If you have separate admin panels for Users and Administrators, and already have a way to differentiate between the two, please change
checkIfUserIsAdmin($user), to make sure all users who get log into the admin panel have a right to do that;
- If your application has only one login screen (for the admins), that means you're not going to use the auth controllers that Laravel provided by default. You're only going to use Backpack's auth controllers. You can keep the Laravel ones in your project, of course. But some people like to delete them to not get confused later on:
# OPTIONAL! Please read the notice above. rm -rf app/Http/Controllers/Auth #deletes laravel's demo auth controllers
That's it. If you already know how to use Backpack, next up you'll probably want to create CRUD Panels.
If it's your first time installing Backpack, it is highly recommended that you go through our Getting Started series, to understand how Backpack works. That's why we created it - to help you learn how to use this admin panel framework. In ~23 minutes we'll teach you 80% of what you can do, and how.
In case you want to add extra functionality that's already been built, check out the installation steps for the add-ons we've developed.
Frequently Asked Questions
Error: The process X exceeded the timeout of 60 seconds. It might mean Github or Packagist is unavailable at the moment. This usually doesn't last for more than a few minutes, so you can run
php artisan backpack:install --timeout=600to increase the timeout to 10 minutes. If this doesn't work either, take a look behind the scenes with
php artisan backpack:install --timeout=600 --debug, and refer to this thread.
Error: SQLSTATE: Syntax error or access violation: 1071 Specified key was too long. Your MySQL version might be a bit old. Please apply this quick fix, then run
php artisan migrate:fresh.
Any other installation error? If you can't install Backpack\Base because of a different error, you can try the manual installation process, which you can tweak to your needs.