Make init_only and server_class config options

Robert Brewer avatarRobert Brewer created an issue

Following the architectural point of "code for programmers, config for deployers", it's become apparent to me that the init_only and server_class arguments passed to cherrypy.server.start are deployer-driven more often than developer-driven. So config entries like the following might be desirable:

server.init_only = True
server.httpserver = None

Comments (3)

  1. Christian Wyglendowski

    Either I read your mind or you read my mind. :-) I was just thinking the same thing today. What about an "embedded" server environment for fastcgi/modpython/etc setups that sets init_only to True and other such tweaks?

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.