* Not found property rule
* Make these “better”
* Day 1
* Day 2
* Day 3
* Dat 4
* Remove disabled check
* Day 4 continued
* Run pint
* Final changes hopefully
* Pint fixes
* Fix again
* Reset these
* Update app/Filament/Admin/Pages/Health.php
Co-authored-by: MartinOscar <40749467+rmartinoscar@users.noreply.github.com>
* Update app/Traits/CheckMigrationsTrait.php
Co-authored-by: MartinOscar <40749467+rmartinoscar@users.noreply.github.com>
---------
Co-authored-by: MartinOscar <40749467+rmartinoscar@users.noreply.github.com>
* Remove deploy.locations from validator
* Change location data to optional for backwards compat
* Better styling
* Add back comma to follow coding style
* Remove EventServiceProvider from providers file
Fixes duplicated auth messages in the client Activity tab.
* Add null check on $model->actor
Prevents the client Activity tab page from breaking when an authentication attempt has failed.
* Proper type checking on $model->actor
Chose instanceof as it seems to be the best in terms of type safety.
Co-authored-by: MartinOscar <40749467+RMartinOscar@users.noreply.github.com>
* Revert removal of EventServiceProvider
* Remove subscription of AuthenticationListener
* Remove subscriptions for auth events
* Remove unused import Dispatcher
* Remove unused import AuthenticationListener
---------
Co-authored-by: MartinOscar <40749467+RMartinOscar@users.noreply.github.com>
Modified server deletion to use internal event handlers from the
Eloquent models themselves. Also added a few preliminary event handlers
in the `Pterodactyl\Events\<USer|Server> namespace that users can hook
into in EventServiceProvider to perform their own actions as they
please (such as push notifications and such).
This action allows servers to be deleted, but only be soft-deleted for
10 minutes. After that time period the server will be completely
removed from the database and daemon. This allows some safety if a
server is accidentally deleted.
Force deleting a server will still work. If the daemon is in-accessible
the server will fail to be deleted. When server is soft-deleted admins
can still view its information page in the admin CP, however the server
will be suspended and inaccessible on the front-end or though the
daemon.
Admins can manually delete the server ahead of the delete timer, or if
it failed to delete previously they can do an immediate retry.
