timeout - graceful - shutdown INTEGER Maximum number of seconds to wait for graceful shutdown. timeout - keep - alive INTEGER Close Keep - Alive connections if no new data is received within this timeout. backlog INTEGER Maximum number of connections to hold in backlog - limit - max - requests INTEGER Maximum number of requests to service before terminating the process. limit - concurrency INTEGER Maximum number of concurrent connections or tasks to allow, before issuing HTTP 503 responses. root - path TEXT Set the ASGI 'root_path' for applications submounted below a given URL path. Defaults to the $ FORWARDED_ALLOW_IPS environment variable if available, or '127.0.0.1'. forwarded - allow - ips TEXT Comma separated list of IPs to trust with proxy headers. date - header / - no - date - header Enable / Disable default Date header. server - header / - no - server - header Enable / Disable default Server header. proxy - headers / - no - proxy - headers Enable / Disable X - Forwarded - Proto, X - Forwarded - For, X - Forwarded - Port to populate remote address info. use - colors / - no - use - colors Enable / Disable colorized logging. access - log / - no - access - log Enable / Disable access log. log - config PATH Logging configuration file. env - file PATH Environment configuration file. interface Select ASGI3, ASGI2, or WSGI as the application interface. ws - max - size INTEGER WebSocket max size message in bytes - ws - ping - interval FLOAT WebSocket ping interval - ws - ping - timeout FLOAT WebSocket ping timeout - ws - per - message - deflate BOOLEAN WebSocket per - message - deflate compression - lifespan Lifespan implementation. Defaults to the $ WEB_CONCURRENCY environment variable if available, or 1. workers INTEGER Number of worker processes. reload - delay FLOAT Delay between previous and next check if application needs to be. This option has no effect unless watchfiles is installed. sw.*, ~* ' by default these defaults can be overridden with ` - reload - include `. reload - exclude TEXT Set glob patterns to exclude while watching for files. Includes '*.py' by default these defaults can be overridden with ` - reload - exclude `. reload - include TEXT Set glob patterns to include while watching for files. reload - dir PATH Set reload directories explicitly, instead of using the current working directory. fd INTEGER Bind to socket from this file descriptor. $ uvicorn - help Usage : uvicorn APP Options : - host TEXT Bind socket to this host. PyYAML will be installed to allow you to provide a.python-dotenv will be installed should you want to use the -env-file option.windows users will have colorama installed for the colored logs.the -reload flag in development mode will use watchfiles.the websocket protocol will be handled by websockets (should you want to use wsproto you'd need to install it manually) if possible.Read more about comparison with h11 here.the http protocol will be handled by httptools if possible.The built-in asyncio event loop serves as an easy-to-read reference implementation and is there for easy debugging as it's pure-python based.uvloop is a fast, drop-in replacement of the built-in asyncio event loop.the event loop uvloop will be installed and used if possible.In this context, "Cython-based" means the following: TLDR Is this standard practice and the way this should be done, to achieve separation between root and other user account? It seems like a "hack" to me.This will install uvicorn with "Cython-based" dependencies (where possible) and other "optional extras". So if you started the X server under your own account (greg) then any other user (like root) doesn't have access to it." You don't want just anybody opening windows on your screen, do you. "This has to do with access control to your X server. What was the point in granting access to the other user if they can't open the program anyway? This separating is done for security reasons, so isn't making that above modification reverting the earlier comment 'export AUTHORITY=/home/greg/.Xauthority'." Or root can take it, because it can access your files: You (greg) can grant it by means of 'xhost local:root'. "You have two ways to get this working: grant it or have root take it. And the gtk-warning cannot open display seems to relate exactly to this issue. The "no protocol specified" part seems pretty straight forward. I get the following error: no protocol specified But when I try to start wireshark as the wireshark user, using: sudo -s -u $USER wireshark I am setting up wireshark to run as non root user, a la here, that is: sudo apt-get install wireshark
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |