[thunfisch]

If you can only install an app without hassle with Docker, it's a really bad sign.

I'm not against Docker, I run a whole cluster of Docker hosts as my job, but touting it as a solution to a hard install for a _php app_ is crazy.

Besides: You're cutting a whole lot of people off because this is apparently not installable on regular shared hosting, etc. Running a Container is even less of an option for these people. And then their only option is to use their hosted version, having to trust them.

Also: Running a Docker Container again requires me to add additional config, be it via labeling (when using reverse proxy with SD, e.g. traefik), or setting up a new nginx config file for that. No benefit in reality.

I'm not against having an additional Docker Image (I like those!) but these should only be considered a option for people who are looking for a Docker image explicitly.

[mosselman]

Not all projects that I want to run locally are written in the same language (PHP for example). So setting up a small docker host in your local network and saving its config in a `docker-compose.yml` seems like a far more lightweight solution than having some PHP server that you need to update and copy-paste files to.

[tjoff]

Thank you!

So many projects seem to think a convoluted i stall is alleviated with a docker image. No! A docker image is good but it doesn't replace the need for a sensible native install.

[avip]

People who want to "just try" something, don't care about shared hosting. They care about having a one-liner that just works. And if you gonna provide such one-liner, it'd better be with docker.