The Ziggy routes file has been generated during the image build. Since it is relying on the APP_URL env, which might be set later to something different, when running the container, it failed in cases with different URL settings.
This is the first fix that pulls the route information via API endpoint from the currently running instance. In this case, we should always get the correct routes file, even if the APP_URL setting is going to change.
The Ziggy routes file has been generated during the image build. Since it is relying on the APP_URL env, which might be set later to something different, when running the container, it failed in cases with different URL settings.
This is the first fix that pulls the route information via API endpoint from the currently running instance. In this case, we should always get the correct routes file, even if the APP_URL setting is going to change.