Skip to content

update faq - remove publish commands from docs #587

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 16, 2024
Merged

update faq - remove publish commands from docs #587

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 4 additions & 12 deletions 6.x/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Backpack PRO is a closed-source add-on, which requires payment in order to recei
<a name="backpack-pro-for-non-commercial-projects"></a>
### Can I get Backpack PRO for free to use in a non-commercial project?

No - we're no longer giving away free licenses. But we _have_ released Backpack CRUD v5 and v6 under the MIT License, which means it's free and open-source. It has fewer features, but you can do absolutely anything you want with it.
No - we're no longer giving away free licenses. But we _have_ released Backpack CRUD v5 and v6 under the MIT License, which means it's free and open-source. It has fewer features, but you can do absolutely do anything you want with it.

<a name="Installation"></a>
## Installation
Expand All @@ -48,17 +48,11 @@ No - we're no longer giving away free licenses. But we _have_ released Backpack
<a name="how-do-i-update-backpack"></a>
### How do I update Backpack to the latest non-breaking version?

First of all, **run `composer update` on your project**. That will pull in the latest supported version of all your Backpack packages.
Run **`composer update`** on your project to update the dependencies given your version constrains in `composer.json`. If you want to update a specific package, you can run **`composer update backpack/crud`** for example to only update `backpack/crud` and it's dependencies.

Then you should **re-publish the JS and CSS assets**. There are two ways to do that:

(A) Run `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:
- delete the public/packages directory and all its contents;
- run `php artisan vendor:publish --provider="Backpack\CRUD\BackpackServiceProvider" --tag=public`
- if you use elFinder, also delete `resources/views/vendor/elfinder` and run `php artisan backpack:filemanager:install`
If you have your assets cached you can run `php artisan basset:clear` to clear the cache too. You can manually rebuild the asset cache if necessary with `php artisan basset:cache`. We do recommend you keep basset disabled on localhost while developing.

Some packages may require you to run additional commands to update the database schema or publish new assets. Please refer to the package documentation or upgrade guide for more information.

<a name="how-do-i-uninstall-backpack"></a>
### How do I uninstall Backpack from my project?
Expand All @@ -70,8 +64,6 @@ You can remove Backpack from your project pretty easily, if you decide to stop u
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

Expand Down