colegatron

@hickersonj did you managed to get it working? Also I am curious if there is anyway to specify in the chart which devices are available on EACH node, since the...

Finally the best solution is to do not use devices in the Linstor configuration. For various reasons, in fact; It is not easy to handle in the chart (or standard...

Don't use .env, everything is hardcoded in the docker-compose for this deploy. Having a look to /data/config there is something curious. /data/config and /data/modules were created Jan28 but /data/storage was...

Retaking this issue after having a different one today :-) (#44) Still having the versions discrepancy: Image running is tiredofit/freescout:1.12.3 but inside .freescout-version I find: ``` $ cat .freescout-version 1.6.7...

This is "only" important because I have to upgrade the API module and it asks for Freescout >=1.6.14, everything else seems to work properly.

Ok, so it is working fine as I guessed. The only limitation is that despite I am running the 1.12.3 version of Freescout, when I try to upgrade the API...

Ops. I was wrong. As far as I understand the upgrade is just update the image: in the docker-compose and then docker-compose down; docker-compose up. The The docker image is...

Finally I moved everything into named volumes and chowned nginx:www-data everything on them. When I tried image tiredofit/freescout:1.14.1 for first time app didn't start and got an error about a...

The rule usually is not have in sync docker images with app version. That's almost impossible I think. :-)

So recapping about the 'upgrade process' (that could be nice to have on the README): 1. Ensure you have upgraded all your modules before proceeding with application upgrade. 2. Ensure...