README

FilamentExtendedStarterKit is a Filament distribution with lots of basic utilities and goodies pre-installed.

New Installation

composer create-project agusprema/webdefault

Install dependencies

composer update

Run migrations

php artisan migrate

Create the first/admin user:

php artisan make:filament-user

Init FilamentShield

php artisan shield:install

Run the artisan command to run scheduled tasks

php artisan schedule:run

For the FilamentShield install, answer "yes" to all questions it asks.

In theory, that should be it. You can now go to /admin on your site and you should see the filament login screen. Log in with the user you created in step #4 above.

Installed Plugins

• User
• Curator
• Exceptions
• Shild
• JobsMonitor
• FilamentSocialite
• FilamentLogManager
• FilamentDatabaseSchedule
• Settings
• Breezy
• LanguageSwitch
• FilamentFontawezome
• SpatieBackups
• SpatieHealth
• ThemeColorSwitcher
• Logger

All relevant migrations, views and config files have been published to the main Laravel directory tree to the locations where you would expect them. If a package (such as, for exmaple, the Spatie packages) is based upon another package, the base package migrations and config files have been published as well.

Some of the above packages are self-explanatory (ie: you'll see them in the admin GUI) while others are development components which require some knowledge of the component for it to be used. Take a look a the component pages, some have docs on the component page, others on their github repo (linked from the component page).

Admin Menu

In order to achieve better menu item grouping, the admin menu is generated by the App\Providers\FilamentServiceProvider class. You can disable the use of this functionality (which will enable the default Filament menu generation) by setting the useCustomMenuGenerator config option to false in the /config/filament-extended-starter-kit.php config file.

HealthCheck

The health checks are also defined and configued in the App\Providers\FilamentServiceProvider class. The only variable which might require tuning is the "nCpuCores" variable which is used to configure CPU load and needs to know the number of CPU cores on you system in order to make this calculation correct.