Upgrade to Resonant v0.51.0

[brianhelba]

No description provided.

[cloudflare-workers-and-pages]

Deploying bats-ai with    Cloudflare Pages

Latest commit:	206b954
Status:	✅  Deploy successful!
Preview URL:	https://409d8602.bats-ai.pages.dev
Branch Preview URL:	https://upgrade-resonant.bats-ai.pages.dev

View logs

[BryonLewis]

Tested the new settings including the rabbitmq upgade and it worked in my classic dev style (using docker compose up).

Seemed to work in dev containers as well

I may have still had an issue launching the task and having direct access to the ports (but if I manually started from the terminal I was able to get client/django access. I will debug further but I don't see it as a blocker for this).

[brianhelba]

I may have still had an issue launching the task and having direct access to the ports

@BryonLewis I'm not understanding this, but let's remember to discuss it.

[BryonLewis]

I may have still had an issue launching the task and having direct access to the ports

@BryonLewis I'm not understanding this, but let's remember to discuss it.

I launch the task for starting Django + Vite + Celery and localhost:8080 and localhost:8000/admin (Django Admin) in my browser don't seem to have the proper port forwarding/tunneling or whatever mechanism dev containers are using to expose that on my system. Almost like it isn't exposed outside of the container. I don't know if this is a system setting on my end or something else that is causing it. When I do launch vite (npm run vite) manually instead of localhost:8080 it uses 127.0.0.1:8080 and then I have access. Same with django if I manually run ./manage.py runserver