Boy132
Boy132
I would say let's focus on the admin area first. There is no reason to start on the client area while the admin area isn't even finished.
#202 was a different error.
Make sure you created the queue worker service: https://pelican.dev/docs/panel/getting-started/#creating-queue-worker
Please run the following command and share the link again: `tail -n 300 /var/www/pelican/storage/logs/laravel-2024-05-18.log | nc pteropaste.com 99` (the logs you originally posted don't contain the actual error)
> Note: pelican has consolidated both subuser and account, and included all of the missing fields in this pr: [pelican-dev/panel#423](https://github.com/pelican-dev/panel/pull/423) > > I'd suggest doing the same thing Feel free...
> @Boy132 sqlite tests are still failling I found the reason: the `sort` for the bungeecord variables is `null`. For all other eggs the `sort` is filled.
> Would be nice if this could be set to the user's prefered theme so we don't get _Throwing flash bang_ It already does. :) 
> Since disk space does not work on windows do we have a way to detect that? Many not show it as crashed? We don't support windows anyways?
> > > Since disk space does not work on windows do we have a way to detect that? Many not show it as crashed? > > > > >...
I want to remove [shuvroroy/filament-spatie-laravel-health](https://github.com/shuvroroy/filament-spatie-laravel-health) but for some reason tailwind classes (colors) aren't working with the custom page/ view:  Might be related to https://github.com/pelican-dev/panel/issues/377?