New Docker image pushed, Hashtopolis 0.13

[Gitoffomalawn]

New Docker image pushed, Hashtopolis has been updated as well, please try it out

The new image works just fine.

However, updating from 0.12 to 0.13 by removing the container and spinning up a new one using the new image doesn't. You have to throw everything away in order to do that, though I don't understand why. Removing the container and spinning up a new one on top of the persistent volumes with a new image results in a blank webpage. Spinning up a completely new instance works.

[kpeiruza]

Looks like an issue with the upgrade of hashtopolis... It's been a while since the last docker was pushed... El vie, 5 may 2023 12:49, Gitoffomalawn ***@***.***> escribió:

…

New Docker image pushed, Hashtopolis has been updated as well, please try it out The new image works just fine. However, updating from 0.12 to 0.13 by removing the container a spinning up a new one using the new image doesn't. You have to throw everything away in order to do that, though I don't understand why. Removing the container and spinning up a new one on top of the persistent volumes with a new image results in a blank webpage. Spinning up a completely new instance works. — Reply to this email directly, view it on GitHub <#8>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADI5TYSFVWUZIUY7QCNQL7LXETLKFANCNFSM6AAAAAAXW6MRXI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Gitoffomalawn]

Did some more testing: even switching between images with the same Hashtopolis version (like kpeiruza/hashtopolis and the self-built image from the Dockerfile) doesn't work. Webpage ends up blank.

This probably means something is getting overwritten that shouldn't be.

[kpeiruza]

Please, provide more feedback, I've tried several docker compose up & down and it still works.

This Hashtopolis has no extra config at all, maybe that's the problem.

Provide the weblogs and/or some extra info about the PHP's docker.

Thanks!