Can i use Backpack also for a complete Web App? Not only as Backoffice

[martinschenk]

Can i use Backpack also for a complete Web App? Not only as Backoffice

[pxpm]

Hey @martinschenk thanks for the question.

I am not sure if I'v understood your requirements completely, but from what I can tell Backpack is just a package that provide you with some auth mechanism, a "backoffice" concept, we call it CRUD, and some widgets/templates for other stuff. (Bootstrap v5)

Backpack will help you most build the "admin" side of your app, but Backpack is just a Laravel package, so you can build your front-end using any technology you want on top of Laravel if you are building a monolithic.

If you want to be more specific I can try to help you understand if Backpack does fit in your requirements.

Cheers

[martinschenk]

Thanks very much. The web app i am building is a reservation system. The "user" aplication can be done perfectly in webpack. I am just asking myself if i also need an "admin" panel for the app, is it better to program the real admin panel in the same webpack panel or in another one? Regards, Martin

…

________________________________ Martin Schenk Ingeniero Diplomado en Automatización Martin Schenk S.L. Calle de la Hiruela 3, 7-5 28035 Madrid ***@***.*** www.martin-schenk.es Móvil 669 686 832 Am Fr., 2. Juni 2023 um 11:08 Uhr schrieb Pedro Martins < ***@***.***>:

Hey @martinschenk <https://github.com/martinschenk> thanks for the question. I am not sure if I'v understood your requirements completely, but from what I can tell Backpack is just a package that provide you with some auth mechanism, a "backoffice" concept, we call it CRUD, and some widgets/templates for other stuff. (Bootstrap v5) Backpack will help you most build the "admin" side of your app, but Backpack is just a Laravel package, so you can build your front-end using any technology you want on top of Laravel if you are building a monolithic. If you want to be more specific I can try to help you understand if Backpack does fit in your requirements. Cheers — Reply to this email directly, view it on GitHub <#511 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE3HMZY55VD33EIZQWRGVLXJGURZANCNFSM6AAAAAAYWZ7QTE> . You are receiving this because you were mentioned.Message ID: <Laravel-Backpack/community-forum/repo-discussions/511/comments/6069533@ github.com>

[pxpm]

Well, it depends. The admin panel makes more sense for the people/company receiving the reservations.

They can login to their account, view reservations, filter them, export etc.

For the other side of the coin, the "end users", I don't think an "admin panel" it's the best UI for them to make the reservations.

You can have all of them in the same application, using the same login process etc but separated with roles/permissions so that you can make control user actions/views.

About the separation of concerns I would say it all depends on the project/complexity and needs of the teams.
Most of the times you will be fine by having users separated with roles/permissions.
If it's mission critical stuff you don't want to mix concerns, I don't think it's the case for a simple reservation system, but in the end it's always up to you.

Cheers

[martinschenk]

Hi Pedro, the idea is just this: - Using the panel for the people who receive the reservation. - But also use the panel for the enduser to make reservations. And show them their own easy to use menus which much less information. Just the necessary to create the reservations. I thought about using spatie permission package to differentiate between three main user roles: Root, Admin and User. Admin are the people working behind the "desk". I am making a test these days with laravel filament and it seems to work fine. But since years i am looking and following your backpack admin panel. I have also done project in Nova. But up to now never in BackPack. Regards, Martin

…

________________________________ Martin Schenk Ingeniero Diplomado en Automatización Martin Schenk S.L. Calle de la Hiruela 3, 7-5 28035 Madrid ***@***.*** www.martin-schenk.es Móvil 669 686 832 Am Mo., 5. Juni 2023 um 13:50 Uhr schrieb Pedro Martins < ***@***.***>:

Well, it depends. The admin panel makes more sense for the people/company receiving the reservations. They can login to their account, view reservations, filter them, export etc. For the other side of the coin, the "end users", I don't think an "admin panel" it's the best UI for them to make the reservations. You can have all of them in the same application, using the same login process etc but separated with roles/permissions so that you can make control user actions/views. About the separation of concerns I would say it all depends on the project/complexity and needs of the teams. Most of the times you will be fine by having users separated with roles/permissions. If it's mission critical stuff you don't want to mix concerns, I don't think it's the case for a simple reservation system, but in the end it's always up to you. Cheers — Reply to this email directly, view it on GitHub <#511 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE3HM7HKNJFAKFZIMX5EEDXJXBYHANCNFSM6AAAAAAYWZ7QTE> . You are receiving this because you were mentioned.Message ID: <Laravel-Backpack/community-forum/repo-discussions/511/comments/6089706@ github.com>

[pxpm]

In that regard we have a similar idea, we also have a first-party package to integrate with spatie permission package https://github.com/Laravel-Backpack/PermissionManager

I've built some panels in the way you describe with roles and permissions and have been working just fine for years.

I would recommend you to give it a try in v6, we are in beta at the moment and will be releasing the final version by the end of this month.

Here is the online demo if you want to play with it: https://demo-v6.backpackforlaravel.com/admin/login

The docs: https://backpackforlaravel.com/docs/6.x/installation#install-using-composer

Cheers

[martinschenk]

Pedro, thanks, i'll have a look. Regards, Martin

…

________________________________ Martin Schenk Ingeniero Diplomado en Automatización Martin Schenk S.L. Calle de la Hiruela 3, 7-5 28035 Madrid ***@***.*** www.martin-schenk.es Móvil 669 686 832 Am Mo., 5. Juni 2023 um 16:14 Uhr schrieb Pedro Martins < ***@***.***>:

In that regard we have a similar idea, we also have a first-party package to integrate with spatie permission package https://github.com/Laravel-Backpack/PermissionManager I've built some panels in the way you describe with roles and permissions and have been working just fine for years. I would recommend you to give it a try in v6, we are in beta at the moment and will be releasing the final version by the end of this month. Here is the online demo if you want to play with it: https://demo-v6.backpackforlaravel.com/admin/login The docs: https://backpackforlaravel.com/docs/6.x/installation#install-using-composer Cheers — Reply to this email directly, view it on GitHub <#511 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE3HMZQIHI6FQROA6I2ZTTXJXSSTANCNFSM6AAAAAAYWZ7QTE> . You are receiving this because you were mentioned.Message ID: <Laravel-Backpack/community-forum/repo-discussions/511/comments/6091149@ github.com>

[jcastroa87]

Due to no activity, I will close this issue, but please feel free to re-open or create a new one if needed.

Cheers.