UI: this.transports.shift is not a function

[LordMike]

This is a UI issue observed with the latest tag, which runs version 0.8.28. 0.8.28 is also a tag which is slightly confusing :|

See jhuckaby/Cronicle#168

Tag 0.8.28 does not exhibit this behaviour.

[belsander]

latest uses a different install method. This tag has been created to facilitate auto builds for Docker images in case new releases of Cronicle happen.

For the issue, I can indeed confirm that latest is broken. 0.8.28 does not have this issue. I'll have a look tomorrow what is going wrong in latest

[raymatos]

was this resovled?

[bluet]

I think I got a fix for the issue in PR #23 .
If anyone's in urgent please check https://github.com/bluet/docker-cronicle and https://hub.docker.com/r/bluet/cronicle

Also I've created another version which supports run each jobs in their own docker container here https://github.com/bluet/docker-cronicle-docker and https://hub.docker.com/r/bluet/cronicle-docker

Hope it helps before @belsander 's review.

[wackazong]

This is because the JSON property socket_io_transports is set to a string and not to a JSON array. You need a different method to set it, I use jq.

[bluet]

is this related? #15

[shmakes]

Any hope of a fix in this repo?
@wackazong Could you expand a bit on your proposed fix?
Thanks.

[wackazong]

The JSON property socket_io_transports ist set to a string in /opt/cronicle/conf/config.json using a special environment variable syntax. This is explicitly disallowed in the Cronicle docs. It simply cannot be done using the method that is used in the Docker file. So there is no easy fix. The Cronicle docs state:

Almost every configuration property can be overridden using this environment variable syntax. The only exceptions are things like arrays, e.g. log_columns and socket_io_transports.

Therefore the config parameter socket_io_transports cannot be set to an array using the environment variable syntax. Either remove it to leave it at the default or set it using another way, e.g. jq.

Normally it should be fine to just remove it. I will submit a pull request to this repo to remove it as it will not work setting it this way.