python-socketio | Python Socket.IO server and client | Websocket library

My expectation is that in order to "start the game" (whatever it means) you need to open the page in the browser, authorize somehow, follow the steps of the protocol upgrade mechanism, etc. to wit exactly mimic what real browser does, all the request sequence which is prior to starting the game.

You might need to correlate dynamic parameters, add HTTP Header Manager, add HTTP Cookie Manager, etc.

Here what I have done to achieve a thing similar as what you want to do :

While venv is activated and you're in project directory (where manage.py live), do the following:

• Open requirements.txt
• Delete unneeded modules from requirements.txt
• Uninstall unneeded modules with pip uninstall module
• Now run pip freeze requirements.txt
• Deactivate venv
• Then add requirements.txt to source control git add -A
• Commit your changes git commit -m "deleted unneeded modules"
• If you have existed Heroku app, connect to it with heroku git:remote -a myapp, else pass this step
• Deploy, git push heroku master

If you are unsure which modules your project need and I can't determin exactly the project's requirements but if you have basic project, you only need 3 modules which are Django, psycopg2-binary, gunicorn, so do the following for clean deploy:

• Delete venv
• Outside project directory, create new one
• Activate venv
• Install the modules you need, probably Django, psycopg2-binary, gunicorn
• Now run pip freeze requirements.txt
• Deactivate venv
• Then add requirements.txt to source control git add -A
• Commit your changes git commit -m "deleted unneeded modules"
• If you have existed Heroku app, connect to it with heroku git:remote -a myapp, else pass this step
• Deploy, git push heroku master

The python-socketio package integrates with many frameworks, including Sanic to implement all the details of the Socket.IO protocol.

And then
$ gunicorn --thread 50 app:app

If the server-side need to active emit to client side, it will need this environment. Because this command $ gunicorn --thread 50 app:app cannot support this situation.

The worked environment should be set by following.

$ pip install eventlet==0.30.2
$ gunicorn -k eventlet -w 1 app:app

The summary is that eventlet (0.32.0) is currently not compatible with Python 3.10 because it tries to patch types that have become immutable in Python 3.10.

Like with your requirements, it is good practice to be more specific with your Docker dependencies too. Today using the tag 3 for the Python Docker image will give you 3.10.0, unless it is using a cache. In the future it could be a different version. Since there is a compatibility issue with Python 3.10, use Python 3.9 - the currently latest Python 3.9 Docker tag is 3.9.7.

i.e. it should work once you change your first line of the Dockerfile to: