4 Replies
debian/bookworm
have erl_crash.dump but basically says the same. Happy to share it here, if needed. Any help appreciated!
copied code from video_room example in web_rtc_engine project and adapted into a phoenix project. It works properly when running locally on OSX, but when we attempt deployment into a debian/bookworm fly machine it fails to start the application.
Removing the start_link code for ExDTLS still makes the VM crash on startup, which is super weird.
Turns out version 1.4.1 of Bundlex had Mix in a runtime function.
Hello! Sorry for a late response - indeed, I believe that the appropriate bugfix was introduced here: https://github.com/membraneframework/bundlex/releases/tag/v1.4.3 so starting from Bundlex v1.4.3 it shouldn't be a problem anymore
GitHub
Release v1.4.3 · membraneframework/bundlex
What's Changed
Ensure not to call Mix.target in runtime by @mat-hek in #119
Full Changelog: v1.4.2...v1.4.3
unrelated but still, have you ever deployed anything to fly.io?
I'm getting only the audio track coming through
i fixed the port range as 50000-50000 to have a single port by default and added that on the services port in the fly.toml config
do different tracks use different ports, now that i think of it?
had to bind to fly-global-services in my integrated_turn_options, for future reference
damn, had it going until i needed to cluster the machine
now it doesn't work again
audio still goes through, though
Hi, we have attempted deploying our Jellyfish Media Server, with some troubles and in the end it wasn't working all of the time. You can read about attempt in the docs: https://jellyfish-dev.github.io/jellyfish-docs/next/deploying/fly_io
Fly.io (experimental) | Jellyfish
This deployment guide is experimental and may not reliably work each time or for every user.