Closed trickert76 closed 3 years ago
sorry, for my unresponsiveness! :/ I'm currently quite busy with other work why my participation regarding BBB is currently reduced to a minimum... I will come back on this soon!
Did you forget to include conf/setup/docker-compose.init.yml
in the commit? I can't seem to find it.
(Also, +1 for this approach)
You're right. My problem is, that I've switched to another workstation and the old one is reinitialized. I though - everything is checked in... I can't find the file.
But I think, it should only contain two lines (version+service) as some kind of header. I'l try to add it tomorrow. Also I can remove on the conflicts.
heyho :)
./scripts/upgrade
within v2.2 doesn't break anything.
v2.3.x
cat
-ing files can't be the best option possible... :D Isn't there any templating engine which supports conditional blocks without much dependencies? we even could use something like jinja2docker during the setup.the approach from https://github.com/alangecker/bigbluebutton-docker/pull/71#issuecomment-777506431 is now merged, so I consider this PR now as obsolete.
thanks for the impulsions @trickert76 ! :)
As mentioned in #42 there is the option to use docker-compose as it is. Because you already use a lot of environment variable, all of them can be stored in the .env file and a docker-compose.override.yml can be created.
The main adventage is, that a user can normally call
docker-compose
as it is and can use bash completion etc.