• 0 Posts
  • 359 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle








  • There is no way to do what teams does without significant infrastructure. Same with Slack and others.

    If you want something that just gets close to the mark, look at Jitsi. It’s about as complete as you could expect for just video/voice.

    What you may not understand about conferencing platforms is that they are dozens of different hosted services working together to provide a cohesive UE. Video, SIP, VOIP, auth, identity…these are all separate services that are deployed as microservices to get what you get. If you find the bare minimum of the services you actually need, you can probably cobble something together, but it’s not going to be a simple running of one service to get the same experience.


  • Don’t pull containers from random sources then. If you’re working with a specific project, only pull from their official images.

    Pushed images are built and verified from the maintainers, then pushed. Then you pull, each layer is verified by hash that it is the same image as was originally pushed by the maintainers.

    Whether that project protects itself from supply chain attacks is a different story, but as far as ports go, you only expose what you tell it to expose. There’s no workaround for that.




  • There are numerous automated systems for this, and almost every platform you use will have their own. Infiscal doesn’t seem bad, but I haven’t used it.

    I always suggest engineers just use whatever is closest to their stacks instead of implementing something, UNLESS it’s going to cost a lot more money (looking at you, AWS).

    Bitwarden/Vaultwarden+BWcli is also another workaround if you’re just using it for small projects.

    Etcd can do value encryption, and Redia even, but you should really be looking at something that has solid RBAC, or ZTC rotation.