Closed FrNecas closed 1 year ago
One related bug found when working on #124 - the time in the docker container is UTC which makes it a mess when working on local CEST system (state planning is acting "weird"). This is, however, related to #55 so I don't think there is really any point in addressing it in this PR. In the rare case that it would influence the functionality, the developer can always set the time to UTC locally for the sake of development
One related bug found when working on #124 - the time in the docker container is UTC which makes it a mess when working on local CEST system (state planning is acting "weird"). This is, however, related to #55 so I don't think there is really any point in addressing it in this PR. In the rare case that it would influence the functionality, the developer can always set the time to UTC locally for the sake of development
Considering the fact that this will definitely run in a CE(S)T environment, wouldn't it be better to force the container to use this timezone (at least until #55 is addressed)?
Setting up the app locally turned out to be a pain even for me (would probably be even harder for first time contributors). For this reason, this PR introduces a
docker-compose
configuration for setting everything up in one command.