Skip to content

Conversation

@Ercogx
Copy link

@Ercogx Ercogx commented Mar 21, 2025

This Filament-based Starter Kit includes essential tools and popular plugins to streamline development.

🌟Panel Include

  • Breezy My Profile page.
  • Themes Themes for Filament panels. Setup for user mode.
  • Shield Access management to your Filament Panel's Resources, Pages & Widgets through spatie/laravel-permission.
  • Settings Integrates Outerweb/Settings into Filament.
  • Backgrounds Beautiful backgrounds for Filament auth pages.
  • Logger Extensible activity logger for filament that works out-of-the-box.

🧑‍💻Development Include

@tnylea
Copy link
Owner

tnylea commented Mar 21, 2025

Looks cool! Testing it out now 🫡

@tnylea
Copy link
Owner

tnylea commented Mar 21, 2025

Thanks @Ercogx,

Have you been able to get everything working correctly by running:

laravel new my-app --using=ercogx/laravel-filament-starter-kit

After I run that and try and open the app, I get the following error:

CleanShot 2025-03-21 at 14 04 16@2x

This is strange because I see that you run the migrations in the post-create-project-cmd https://github.com/Ercogx/laravel-filament-starter-kit/blob/main/composer.json#L58C10-L58C33, but when I run php artisan migrate it seems to solve that, but then when I try and visit in the browser, it looks like it's not loading the assets correctly.

CleanShot 2025-03-21 at 14 03 02@2x

Any thoughts on how to fix those? Let me know. Are you able to get it working fine on your end with the laravel new command

Let me know, and we'll work on getting these resolved and merging them.

Thanks!

@tnylea tnylea added the Awaiting User Response waiting for the user response label Mar 21, 2025
@Ercogx
Copy link
Author

Ercogx commented Mar 21, 2025

Hey @tnylea , thank you! I fixed both issues. Please check again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Awaiting User Response waiting for the user response

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants