Filament on offline production server: blank components
I'm new to filament and it works great in my development environment. But I'm having trouble to make filament work well on our production server. The setup is unconventional because there is no internet connection in the production environment. Also, the project needs to run in a subfolder of the webserver (eq: https://webserver/laravel-project1). Development is done in a separate environment with internet connection. The vendor folder is being zipped and moved over to production manually, as is the 'build' folder. The laravel app works, except for the filament admin panel. The menu items of the resources are displayed, but when clicked, a gateway timeout eventually occurs and there are no errors in the browser console. Also on the homepage of the dashboard, all cards are displayed empty. Obviously, something is missing or not being found... . Any pointers to get me in the right direction? I already did the basics mentioned in the forum rules. Thx.
4 Replies
wait if there is no internet connection in the production server, how do you access the site?
It's on the local network environment.
Could it be that you havent migrated?
Idk, also its generally bad practice to copy-paste vendor
Maybe missing node modules:
npm install and npm run build
Check the .env as wellThx for the help. Still stuck however.
-All table are present in staging/production and have the correct permissions/structure.
-I know it's not ideal to have to manually install vendor, but since there is no internet connection..., I also tried through git but we ran into problems.
-Unfortunately the node modules need also to be zipped & moved over. I also double checked this for the correct version.
Some 'progress' : the user table on production and staging was different from the one in local dev. I need to use a custom user table in my apps. After installing the alternate user table in local dev, the dashboard also displays empty components in local dev. So probably the dashboard problem and the resource problem are not related. I implemented the getFilamentName() function on the user model, but the dashboard problem remains.