You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently composer is installed in the Dockerfile and called from the container's run.sh script. There are a few problems with this:
It assumes you want the container to manage vendors.
It goes against the philosophy of separating tools to manage code from code itself.
It causes a sometimes significant delay during startup.
I'm bringing this up because the point of Docker is to run an app with the user not having to worry about external deps. If we drop composer, we'd have to expect the user to have a working Elgg installation means the user either needs to download a release of Elgg that's already composed, or have composer and its reqs installed.
The text was updated successfully, but these errors were encountered:
Currently composer is installed in the Dockerfile and called from the container's run.sh script. There are a few problems with this:
I'm bringing this up because the point of Docker is to run an app with the user not having to worry about external deps. If we drop composer, we'd have to expect the user to have a working Elgg installation means the user either needs to download a release of Elgg that's already composed, or have composer and its reqs installed.
The text was updated successfully, but these errors were encountered: