Ramon Blanquer

@danielsogl I would really appreciate this fixes to be released on npm :) Is there anything I can help with?

Apart from scaling I guess we would also benefit from the service discovery features in docker compose? Like... my (docker) service named "backend" can be accessed from the "frontend" one...

@david-house-harvard Thanks a lot for your reply! Yes... In the end I went down that path. I wrote about each step in detail if you are curious: https://hackernoon.com/microservices-on-fargate-part1-f26a318827a8 https://hackernoon.com/microservices-on-fargate-part2-f29c6d4d708f

Scaling services independently. Think of the classic full stack example where if you have all your containers together into one task you cannot scale them independently... > On 17 Jul...

This is also related to this: https://github.com/Unity-Technologies/UnityRenderStreaming/issues/799 The possibility of connecting this wonderful plugin with existing media servers would be great. To perhaps create a new kind of signaling class...

Sadly not @vmagalhaes. I ended up learning another tool called transloco.

@vmagalhaes yes you can craft it using what they call "scopes" https://ngneat.github.io/transloco/docs/lazy-load/scope-configuration/

I can also reproduce this issue. That's why I thought a SFU solution (either connecting to a SFU solution or writing one within URS) would alleviate the stress... But it's...

+1 on this. I don't have privileges to change the socketio version of the backend I am using so I need to use 2.x :(

> I was getting this error when trying to run with the `OPENAI_API_KEY` environment var. Switching to using `api_key_cmd` made it go away. > > If you just want to...