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
Bug description
I am running Firefly III version 4.7.5
I noticed that composer.lock is ignored when copying files to the docker container, prior to running composer install. It is however saved to version control. Correct me if I'm wrong, but this means that people installing Firefly III on a self-hosted server following the procedure with composer create-project will end up with the versions in the composer.lock file while those using Docker ends up with whatever is resolved by composer install with no lock file when building the container.
If that is so, then you end up with users running the same version of Firefly III with potentially different vendor versions.
The text was updated successfully, but these errors were encountered:
chrif
changed the title
composer.lock should not be ignored in .dockerignore
composer.lock should not be ignored in .dockerignore
Jul 8, 2018
Bug description
I am running Firefly III version 4.7.5
I noticed that
composer.lock
is ignored when copying files to the docker container, prior to runningcomposer install
. It is however saved to version control. Correct me if I'm wrong, but this means that people installing Firefly III on a self-hosted server following the procedure withcomposer create-project
will end up with the versions in thecomposer.lock
file while those using Docker ends up with whatever is resolved bycomposer install
with no lock file when building the container.If that is so, then you end up with users running the same version of Firefly III with potentially different vendor versions.
The text was updated successfully, but these errors were encountered: