Part --bind "0.0.0.0:8081" allows connection from all IPs, which is not something you should do if you don't fully understand the consequences. You have to add it if you are running it in a Docker container, but it is not recommended to do so if you are running it directly on your machine. Maybe we should probably word when exactly is this necessary.

Part --bind "0.0.0.0:8081" allows connection from all IPs, which is not something you should do if you don't fully understand the consequences. You have to add it if you are running it in a Docker container, but it is not recommended to do so if you are running it directly on your machine. Maybe we should probably word when exactly is this necessary.

Thank you for your feedback! You're absolutely right that binding to 0.0.0.0 allows connections from all IPs, which can be a security risk if not properly managed.

I've updated the documentation to clarify when this is necessary:

• Use --bind "0.0.0.0:8081" when running the server in a Docker container or in a cloud environment where external access is required.
• Use --bind "127.0.0.1:8081" when running the server directly on your local machine to restrict access to localhost only.

Additionally, I've added a warning to highlight the security implications of using 0.0.0.0 and recommended ensuring proper firewall rules or network security measures are in place when exposing the server to external networks.

Here’s the updated command with the clarification:

# For Docker or cloud environments (external access required):
gunicorn -w $((2 * $(getconf _NPROCESSORS_ONLN) + 1)) --timeout 12600 -k uvicorn.workers.UvicornWorker autogenstudio.web.app:app --bind "0.0.0.0:8081"

# For local development (restrict to localhost):
gunicorn -w $((2 * $(getconf _NPROCESSORS_ONLN) + 1)) --timeout 12600 -k uvicorn.workers.UvicornWorker autogenstudio.web.app:app --bind "127.0.0.1:8081"

Part --bind "0.0.0.0:8081" allows connection from all IPs, which is not something you should do if you don't fully understand the consequences. You have to add it if you are running it in a Docker container, but it is not recommended to do so if you are running it directly on your machine. Maybe we should probably word when exactly is this necessary.

Thank you for your feedback! You're absolutely right that binding to 0.0.0.0 allows connections from all IPs, which can be a security risk if not properly managed.

I've updated the documentation to clarify when this is necessary:

• Use --bind "0.0.0.0:8081" when running the server in a Docker container or in a cloud environment where external access is required.
• Use --bind "127.0.0.1:8081" when running the server directly on your local machine to restrict access to localhost only.

Additionally, I've added a warning to highlight the security implications of using 0.0.0.0 and recommended ensuring proper firewall rules or network security measures are in place when exposing the server to external networks.

Here’s the updated command with the clarification:

# For Docker or cloud environments (external access required):
gunicorn -w $((2 * $(getconf _NPROCESSORS_ONLN) + 1)) --timeout 12600 -k uvicorn.workers.UvicornWorker autogenstudio.web.app:app --bind "0.0.0.0:8081"

# For local development (restrict to localhost):
gunicorn -w $((2 * $(getconf _NPROCESSORS_ONLN) + 1)) --timeout 12600 -k uvicorn.workers.UvicornWorker autogenstudio.web.app:app --bind "127.0.0.1:8081"

Can you please push the latest changes?

All committers have signed the CLA.

davorrunje updated.