First of all, thanks for developing this great product!
After successfully setting up both local and public deployments of jitsi using Docker, and setting up a local development workflow for jitsi-meet (using VSCode and WSL on Windows), we’ve hit a bit of a roadblock.
My original plan was:
- build custom docker image of jitsi-meet and upload it to our company’s private docker registry
- in our deployment (based on docker-jitsi-meet), login to both the docker registry where the jitsi stack is hosted, as well as into our private registry, and modify the
docker-compose.ymlfile so that
web.imagepoints to our custom image
One uncertainty I had was that the naming confused me a little. The
jitsi/jitsi-meet repository seems to represent the “web/frontend” part, but
jitsi/docker-jitsi-meet seems to represent docker configuration for all components of the stack. Is this correct?
I have to preface this by saying that I don’t have a lot of experience with developing/building docker images; I’ve only been on the consuming end so far.
Documentation didn’t get me too far I’m afraid. My main questions are:
- I have connected our fork of jitsi-meet to a private repository on dockerhub. What infrastructure do I need to add to the fork so the image can be built on dockerhub? Should I copy over the
Makefilefrom docker-jitsi-meet/web into the fork’s root directory? My goal is to have dockerhub generate a clean, isolated image of just the jitsi-meet web frontend that I can then pull in through a dockercompose file.
- When step 1 is working, would it be enough to just point the
web.imageentry to our own image? Or would we need to configure anything else?
Please do let me know if you have any follow-up questions or if anything’s unclear and I’ll try my best to provide more details. Thanks for your time!