On 03/22/2017 04:44 PM, Long Vu wrote:
Just FYI, I wasn't doing any "upgrade".
That instance started out as Kallithea 0.1 that I installed manually.
Then for 0.3, I used this Docker image
https://hub.docker.com/r/atnurgaliev/kallithea/.
Then for 0.3.2, it's the same Docker image but newer version.
Upgrade for me was, stop the old container with 0.3 image and start
the new container with 0.3.2 image, without any change to the config /
DB.
The previous upgrade from 0.1 to 0.3, from memory, was just about
finding how to volume mount the config and data into the container at
the location the image wants it. I probably update something in the
config but did not change anything for the data.
So if 0.1 to 0.3 I messed up something, then from 0.3 to 0.3.2 I
literally simply start the new container and the bug magically fix
itself, is that expected?
Was I supposed to run some upgrade script? Or do something other than
just starting the new container? It would be good to know for the
next time.
Assuming the templates were updated correctly and matched the controller
code, I guess it might have been the cached temporary compiled templates
that might have been wrong. Usually, they are updated automatically ...
but perhaps not if changing back and forth and the timestamps do the same.
/Mads
_______________________________________________
kallithea-general mailing list
[email protected]
https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
