Christian Lück

> @clue do you think it can be merged once rebased Afaict there are still some outstanding, uncommented issues in this PR, other than that I'm good with this change...

> In practice though for such small project it might be an overkill. I'd get to tagging when / if things start to break due to dependencies change, i.e. Adminer...

Thanks for your input @mikehaertl, I think your making some valid points, so let's reopen this :+1: > […] users will always know, which version of adminer they are using....

Thanks for your feedback so far, I'd like to hear some more opinions on this though. This image is currently set up to automatically trigger a build regularly, see also...

I think we all agree that tags _can_ be useful :+1: > Here's a proposal to make everyone happy: […] I think this is a sane proposal, however this will...

> There is now an official image based on alpine (eg php:7.0-fpm-alpine), so it could solve #16 at the same time Sounds good to me! :+1: Does anybody feel like...

> this image can be simplified a lot. That's good to hear and I'm not opposed to getting any optimization in here at all :) This image has initially been...

To clarify this a bit, the following should be supported: ``` $ docker run -d --name=mysql mysql $ docker run -d --name=adminer -p 80:80 --link mysql:mysql clue/adminer ```

See also http://integricho.github.io/2014/02/22/running-django-on-a-subpath/ which suggests a similar solution: ``` RequestHeader append X-SCRIPT-NAME /mydjapp RequestHeader edit X-SCRIPT-NAME ", /" "/" ```

After looking into this again it looks like there's still no standard way of how different applications handle this. It looks like `X-Forwarded-Path: /foo` would be an easy addition here...