[chrisweekly]

It's not just an implementation detail! The whole idea is to locally run / manage / extend a system for personal data. I don't want to put PHP at the heart of my private infrastructure. Any such system needs to resonate with the tools and technologies I use and/or want to embrace.

[BorisMelnik]

Isn't this more of a proof of concept. I'm pretty sure if it were adopted it would be scrapped and started from scratch anyway.

[kordlessagain]

$ find ./ |grep .php |wc

433 (number of files in project with .php extension)

> Isn't this more of a proof of concept.

Was that a question, or a statement of fact?

[deanclatworthy]

Or use docker, and then it’s independent of your host environment. This should be a safe environment for people to showcase their work, and your comment was not constructive.

[haswell]

It’s completely fair to share one’s reasons behind why a project isn’t for them. Docker doesn’t change any of the fundamental concerns with a PHP based project. It might reduce the amount of direct exposure required, but for a piece of software that is meant to become the virtual center of your life, it’s still completely fair to be unconvinced.

I’d argue that Docker just shifts the problem slightly, while introducing a new set of challenges. It’s unclear if the net benefit is even a positive number.

Even if one doesn’t intend to contribute to the core project, it’s going to be necessary to get a bit intimate with the stack over time: upgrades, the inevitable bug that requires some troubleshooting, etc.

I found the parent comment both reasonable and constructive.

You may not have the same concerns, and that’s perfectly ok.

[dariuszW]

Yeah i know You mean, in my case this is fine as this is the stack that I work with.

That's normal, i know some ppl that use Node as Core, some Java as core, each one takes his own stack i guess.

[angrais]

How does Docker shift the problem and what new challenges does it introduce?