fix: use DOCKER_HUB_USERNAME instead of default ecamp for varnish image

[usu]

I enabled API_CACHE_ENABLED on Github dev environment and on feature-branch environment.

Varnish didn't deploy properly, though. Reason was, that it looked for the image at docker.io/ecamp/ecamp3-varnish, however we're publishing the images at docker.io/ecamp3travis/ecamp3-varnish.

Does anyone remember, whether there was a specific reason why we switched from ecamp to ecamp3travis. We last published on ecamp in March 2023. ecamp is marked as a "community organization", while ecamp3travis seems to be a normal "community user".

[BacLuc]

I enabled API_CACHE_ENABLED on Github dev environment and on feature-branch environment.

Varnish didn't deploy properly, though. Reason was, that it looked for the image at docker.io/ecamp/ecamp3-varnish, however we're publishing the images at docker.io/ecamp3travis/ecamp3-varnish.

Does anyone remember, whether there was a specific reason why we switched from ecamp to ecamp3travis. We last published on ecamp in March 2023. ecamp is marked as a "community organization", while ecamp3travis seems to be a normal "community user".

as i recall, ecamp3travis is our DOCKER_HUB_USERNAME.
I never had access to the ecamp organisation on docker hub.
And we discussed it lately i think, and there were some restrictions about the size of the organisation.

[BacLuc]

It may be that after this commit: 6408263#diff-752f91fa9cecb6e8ac18316542fe6b6c0ab1b3899119e6252769d79bd30ec292R60

I (or someone else) changed DOCKER_HUB_USERNAME