chore: serve static files directly via Nginx

[jinrenjie]

What was changed

Static files for the frontend SPA are now served directly via Nginx instead of being routed through the backend project. This removes the need for any SPA-specific configuration in the backend.

Why?

In the current version, refreshing on any frontend route other than the Home page results in a 404 response. By serving SPA routes directly with Nginx, we can handle routing at the web server level, simplifying backend configuration and improving performance.

Checklist

• Closes Why not serve SAP with Nginx? #5
• Tested
  • Tested manually
  • Unit tests added

[butschster]

Hey! Thx for the PR! Did you try 1.13.4-dev version?

[jinrenjie]

@butschster I deployed it using a Docker image with one click. Are we going to abandon updating the Docker image and instead build it directly from the source code?

[butschster]

@jinrenjie I released version buggregator 1.13.4-dev, where (if I’m not mistaken) I fixed the issue with navigating between pages. Did you have a chance to try it?

Regarding the Docker image — if I recall correctly, that’s how we used to do it before. Later we switched to handling HTML on the PHP side, since there are some additional limits there.

[jinrenjie]

@jinrenjie I released version buggregator 1.13.4-dev, where (if I’m not mistaken) I fixed the issue with navigating between pages. Did you have a chance to try it?

Regarding the Docker image — if I recall correctly, that’s how we used to do it before. Later we switched to handling HTML on the PHP side, since there are some additional limits there.

@butschster I deploying with the ghcr.io/buggregator/server:1.13.4-dev image, the 404 error on page refresh still persists!

[jinrenjie]

If the frontend is to be served via PHP, is what I did in this buggregator/server#290 PR correct?

[butschster]

If the frontend is to be served via PHP, is what I did in this buggregator/server#290 PR correct?

Good question! I'll check it. Thx!

[butschster]

Hi @jinrenjie 👋
I’ve already replied to your pull request buggregator/server#290 and left a review there. That one should be enough to fix the issue. If for some reason it doesn’t fully resolve the problem, then we can revisit this repository as a fallback. Thanks again for taking the time to work on this 🙌