Setting web_path results in 404 after setup about ampache-docker HOT 6 OPEN

are you proxying the container to be /ampache through something like nginx/etc?

The container is set to the / path on the webroot you would probably need the local_web_path set as well depending on your setup.

There are some issues with docker/proxying that i'll have a search for and see if there's anything in the wiki. cause i'm sure we've had this issue with people before

from ampache-docker.

I'm not proxying yet, just testing directly. But I'm planning to proxy via either caddy or apache.

I'll check local_web_path.

from ampache-docker.

config/ampache.cfg.php has these web_path values:

web_path = "/ampache"
;local_web_path = "http://localhost/ampache"

Adding local_web_path = "http://localhost/ampache" (uncommented) to the config file doesn't fix things.

from ampache-docker.

I found a way to fix the 404, but I'm not sure how to fold this into the container so you can easily deploy a new container.

I ended up appending the following to /etc/apache2/sites-enabled/001-ampache.conf:

Alias /ampache "/var/www/public"

The issue is that docker can't know what the alias will be until after the initial ampache setup in the web UI.

from ampache-docker.

I'd recommend adding a docker environment variable that can be passed into the docker command or set in docker-compose.yml to ensure this Alias is set.

... unless I'm missing something and there's a better way to do this. But on my previous installation (that I'm migrating from) Alias is how I set this up.

from ampache-docker.