Wrong filament routes/conflicting routes
I don't know if it's a bug in Filament, or if it's because of misconfiguring Nginx.
So I have two Laravel applications each one has its own database, running on the same subdomain:
The first one is on:
app1.domain.local
The second one is on app1.domain.local/app2
Here is the Nginx configuration:
https://i.imgur.com/pGrZfe4.png
https://pastebin.com/ybVH84ys
On the first app, there is no problem at all.
On the second app which is at /app2, weird things happen.
It's working just fine, it's showing data from its own database, but when I create a new record, when I click on the submit button the live wire post request goes to http://app1.domain.local/livewire/update, shouldn't it go to http://app1.domain.com/TEST/livewire/update? and the surprise is that the record is created in the database of the first app, and the redirection after creation goes to the first app too, so basically, since I clicked on the submit button to create a record it's jumped to the first app.
Routes also default to the first app, even if I call them in the second app, I have a button for example that redirects the user to a resource create page:
When I call this one from the second app, it is expected to take me to app1.domain.local/TEST/dashboard/customers/create, but goes to app1.domain.local/dashboard/customers/createPastebin
server { listen 80; server_name app1.domain.local; root "S...
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
0 Replies