team-container
team-container copied to clipboard
A collection of containers to prepare a server for collaboration.
One person in Jitsi is no problem, but when a second one comes in it breaks down with the error message:  This happens every single time....
Instead of using subdomains (video.example.org, chat.example.org; cloud.example.org and www.example.org) I would prefer subdirs (www.example.org/video, www.example.org/chat, www.example.org/cloud). That seems for me clearer and more obvious. Furthermore https://spdyn.de/ is limiting the number...
The prebuild pods are working on my server, i want to add a new pod ([collabora](https://nextcloud.com/collaboraonline/)) to edit documents in nextcloud. There are many documentations how to achieve this in...
Sadly Jitsi uses Googles STUN-Servers by default. Do you know if this containerized version of Jitsi replaced them with more privacy respecting ones? For example: stun.nextcloud.com:443 stun.stunprotocol.org:3478 stun.services.mozilla.com:3478
I did pull the latest version of team-container to install Plik. Now my nextcloud instance does not run anymore. When I run: `helm upgrade nextcloud team-nextcloud/ --values values-nextcloud.yaml` i get...
I get the following error when I execute "kubectl logs nextcloud-team-nextcloud-db-75f7cd8c8f-qs2ng": Error from server (BadRequest): container "nextcloud-team-nextcloud-db" in pod "nextcloud-team-nextcloud-db-75f7cd8c8f-qs2ng" is waiting to start: trying and failing to pull image....
How about adding [PrivateBin](https://privatebin.info/)? It's very useful for quickly transmitting sensitive and/or internal data to colleagues or customers with end-to-end encryption, and supports "burn after reading" modes and expiry dates.
we want to install the teamContainer on a specific port 8444 .... port 80 and 443 is not available: i have changed the following files: ../team-setup/templates/ingres/02-service.yaml (replace 443 with 8444)...
After cloning and installing team-container "kubectl get nodes" shows the above error. `the server is currently unable to handle the request` k3s-serve seems to be listening on the specified port:...
because of #7