Filament v3 w. Laravel 11 and AWS hosting
Hi, usually our frontends are hosted on S3 buckets, however with Filament it is directly linked to our API, and therefor also our API URL, i.e.
api.xxxx.com/<some-filament-route>.
I was wondering if there is a way around this? Right now I have set up a CNAME that refers to the Filament origin in AWS, however it basically just redirects. My main thought is that I wanted to use a more descriptive name than api.xxxx.com/<some-filament-route>
Do you have any inputs? Thanks!4 Replies
Did you set a
->domain() for the panel?No but as I read the docs this is only for limiting requests from other urls?
The "issue" here is a reverse dns issue I think. Given thet our CNAME is dashboard.xxx.com but the real deployment is located on api.xxx.com and thus it redirecta to this.
So if I'm correct there are 2 ways out of this.
1. Is to somehow setup a reverse dns with the filament part of the api.
Or
2. Separate the API and filament, but I'm unsure if this is possible?
Maybe there are other options, I'm just guessing a bit here.
Does what I say make any sense?
Maybe this is some AWS thing and you need to allow TrustedProxies (Laravel). But you should be able to set a CNAME without it redirecting to a different domain
Could be, I'll check up on it. I was wondering whether the issue is related to the CNAME
api.xxx.com and in reality Filament is just a subdirectory on that api.xxx.com/dashboard etc. I'll try to investigate more in details. I was just wondering if there was an obvious thing that I was missing.
Thanks!