<@U02FZDEUUH0> heyo! :wave:
# docker
w
@Colin - Krumware heyo! 👋
p
glad to see you here
w
all ready to do some testing whenever there are builds ready. I suppose just give me a mention whenever 🙂
c
Yo!
I don't have much exposure to portainer, but we do a tonnn of work in kubernetes and other orchestrators
w
that's fair, as soon as their a image tag that needs testing then just send it over with a @ and I'll try and do whatever you ask for with it
since yeah, the only thing stopping us right now from deploying cal in Docker is the fact that the image has to be built to work "properly"
c
The big key for you on portainer is the runtime configurability of the WEB_APP_URL correct?
w
yeah. If all variables could be set at runtime instead of at build, then deploying in for example Docker swarm via Portainer would be way easier as we do the configuration on one machine with the calendso/calendso image and it would just work everywhere else once deployed
c
we do have some restrictions in the core codebase that we need to work around, but that's good confirmation. Does portainer give you any built-in image build-push-store functionality?
w
It has the functionality to build images, yes, but it would then have to build the image for each node if you're a Docker Swarm user—it sadly won't sync across all machines just like that once built
c
Dang, that's annoying. Not useful at all haha
Ok great insight, thank you!
w
No problem 🙂