Skip to content

More information about deployment? #552

@songololo

Description

@songololo

As someone new to deploying websites, I'm wondering if it would be possible to provide more information about aiohttp deployment along with some recommended setups and settings, and some recommendations for when to use what type of setup given different goals. (e.g. websockets, CPU intensive apps, etc.)

What I've found so far:

  • There is a documentation page on deployment with gunicorn.
  • There are also some comments in various issues discussions suggesting that aiohttp can be deployed directly (without gunicorn) behind nginx as a reverse proxy / load balancer.
  • Some of the example files (websocket and multiprocess examples) use os.fork() to create child processes. I'm assuming that these examples would be used as a stand-alone deployment, presumably behind nginx?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions