[timetagger] missconfiguration of container/image since a couple of versions about charts

[Ornias1993]

/usr/local/bin/python: No module named timetagger
Is caused by timetagger itself directly, I doubt this is a helm-chart issue, are you sure that the container even works at all?

[shadofall]

values as it at 0 for run as. questions has it as 568. forcing 0 0 now to see if it works

[Ornias1993]

good call @shadofall

[shadofall]

deployed with run as root, nothing strange in logs.

[shadofall]

noroot container is also available. also looks like they've removed tg_user and tg_pass instead opting for a single env with user/hash

so not sure if the the tg_user/pass values are still recognized or not.

https://github.com/almarklein/timetagger?tab=readme-ov-file#authentication-using-credentials
as well as a proxy auth.
https://github.com/almarklein/timetagger?tab=readme-ov-file#authentication-using-credentials

i can make the container swap easy enough. how do you want to address the credential options? just document the choices? and let the user add the env based on the auth they want? @Ornias1993

[Ornias1993]

just make a breaking change and move to the new system, otherwise we might have the same issue all-over-again in the future