-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Jitsi to Ansible in iocoop #295
Comments
We have 2 VMs in the SCL location, which is the best option bandwidth-wise for this. But those servers are currently in use for things like the wiki, lists, donate. The other VM we have for project stuff like parts and library is in MSP, which is bandwidth limited. I'm thinking we should spin up a new misc VM in SCL for things like Jitsi and Discourse. We could eventually migrate the parts and library there as well. |
What info do you need, if any, for making this happen? Happy to copy configuration files off the vm in space or anything else you might need for this migration. |
Use m6.noisebridge.net for hosting misc services. * Update role jnv.unattended-upgrades. * Fix `bfb` username in per-host ACLs. * Remove unknown `allyourbasepair` user. * Fix `rizend` user login. * Deploy podman to m6. * Add missing gpg package to defaults. First step for: #295 Signed-off-by: SuperQ <[email protected]>
Ok, I've cleared out (well, it was empty and not doing much) m6 and re-installed it with Debian 11 / Podman. |
Thank you. Seems we can deploy Jitsi alongside Matrix and Prometheus Grafana #297 via Ansible playbook. https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/master/README.md Perhaps we deploy https://jitsi.noisebridge.net And just leave the vm in the space as-is |
Continuing conversation from Discuss forum, I'd like to help migrate our https://jitsi.noisebridge.io setup into Ansible to solidify reproducibility. I did not set it up as-is, but can assist in migrating away from it's current home: a virtual machine on a Windows box at the space.
The text was updated successfully, but these errors were encountered: