`fpm` image does not serve static files

[eta-orionis]

Code of Conduct

• [X] I agree to follow this project's Code of Conduct.

Submission validity

• [X] This is not a personal support request, that should be posted on discussions community.
• [X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

• [X] I've read the documentation and made sure to follow it.
• [X] I've read the troubleshooting first steps and frequent issues guides.

Version

1.9.2

Description

Running latest yourls:fpm-alpine image with an nginx reverse proxy in front of it. jQuery and other static assets are "404 not found" by nginx -- which is to be expected, since they are not on the nginx container and the nginx container cannot access files on another container (yourls). As a result, the interface simply does not work.

Expectation

• The interface should work
• There should be a documented way how to configure reverse proxies in front of the fpm image

Reproduction steps

docker-compose with three containers

• yourls:fpm-alpine
• mysql
• nginx

Configure yourls and nginx as per documentation at https://yourls.org/docs/guide/server-configuration#the-basic-nginx-server-configuration Try accessing any of the static files, e.g. /js/jquery-3.5.1.min.js?v=1.9.2

Context

The documentation does not provide any way or example to use the fpm image together with a reverse proxy. Such an example would be appreciated. If this is not possible at all, then the fpm image is of little use and could be deprecated/removed.

[LeoColomb]

Thanks for opening this issue @eta-orionis. That said, I'm not sure to follow your point. You are indeed free to use/build the infrastructure you want, and FPM images are an option that could match architecture needs. But YOURLS documentation is focused on how to use YOURLS software, not really on how to design a complete service infra. Indeed, there is literally an infinite of possibilities.

Now in your specific case, if I understood correctly, you are using Nginx as a reverse proxy to handle FastCGI forwarding, which is great. That said, you are referring to the Nginx server configuration template, which is a different usage of Nginx. If you have used this configuration, static files won't be served, indeed.

I'd suggest two options:

• If you are skilled enough regarding Nginx proxying or if your provider offers technical support: Nginx can be tweaked to forward all requests with the correct criteria to YOURLS via Fast CGI protocol, static files included. It must be done according to your environment.
• If not: it's probably much easier to start with the default image, latest tag or apache tag, which comes with a ready to use HTTP-server.