working with docker we have to alter the image adding packages and this defeats easy rebuilds and portability.
the main issue is, I have e.g. ffmpeg or any other package required for mobile, but these are on strange paths on NAS OS.
for this there is a "docker" way to deal with it, which is run commands after container start, but is not really nice and requires constant maintenance of the command on top of the issue resolution of related packages in piwigo.
I suggest that the external packages are moved to a separate directory than config, because config is also mounted in docker but managed by piwigo itself mostly.
the whole point is e.g. I have ffpeg in /here/there/ffmpeg on host, and I would like to map the volume like /here/there:/external_pkgs/ffmpeg
this also allows me to put another docker container in a single docker-compose.yml and make sure every external app complies with piwigo requirements and it will be easy to downgrade or upgrade them just when necessary and not by mistake.
working with docker we have to alter the image adding packages and this defeats easy rebuilds and portability.
the main issue is, I have e.g. ffmpeg or any other package required for mobile, but these are on strange paths on NAS OS.
for this there is a "docker" way to deal with it, which is run commands after container start, but is not really nice and requires constant maintenance of the command on top of the issue resolution of related packages in piwigo.
I suggest that the external packages are moved to a separate directory than config, because config is also mounted in docker but managed by piwigo itself mostly.
the whole point is e.g. I have ffpeg in /here/there/ffmpeg on host, and I would like to map the volume like /here/there:/external_pkgs/ffmpeg
this also allows me to put another docker container in a single docker-compose.yml and make sure every external app complies with piwigo requirements and it will be easy to downgrade or upgrade them just when necessary and not by mistake.
<!-- github-sync-id:1437330685 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
working with docker we have to alter the image adding packages and this defeats easy rebuilds and portability.
the main issue is, I have e.g. ffmpeg or any other package required for mobile, but these are on strange paths on NAS OS.
for this there is a "docker" way to deal with it, which is run commands after container start, but is not really nice and requires constant maintenance of the command on top of the issue resolution of related packages in piwigo.
I suggest that the external packages are moved to a separate directory than config, because config is also mounted in docker but managed by piwigo itself mostly.
the whole point is e.g. I have ffpeg in /here/there/ffmpeg on host, and I would like to map the volume like /here/there:/external_pkgs/ffmpeg
this also allows me to put another docker container in a single docker-compose.yml and make sure every external app complies with piwigo requirements and it will be easy to downgrade or upgrade them just when necessary and not by mistake.