Don't use Plack::Loader::SyncWitS3 when OTOBO_SYNC_WITH_S3=0 is set

[bschmalhofer]

When

OTOBO_SYNC_WITH_S3=0

is set in .env then plackup uses the loader Plack::Loader::SyncWitS3. This because of a check in bin/docker/entrypoint.sh ,

# For production use Gazelle, which is implemented in C.
# The special loader Plack::Loader::SyncWithS3 checks for updates in S3.
if [[ -z "$OTOBO_SYNC_WITH_S3" ]]; then
    exec plackup --server Gazelle --env deployment --port 5000 bin/psgi-bin/otobo.psgi
else
    exec plackup --server Gazelle --env deployment --port 5000 -I /opt/otobo -I /opt/otobo/Kernel/cpan-lib --loader SyncWithS3  bin/psgi-bin/otobo.psgi
fi

It is not obvious why this hasn't been noticed before. A possibility is that the loader SyncWithS3 was always used but happened to work even when S3 was not activated.

[bschmalhofer]

The service web now starts up again just fine. Test suite looks good. Closing this issue.