Ticket #480 (defect)
Opened 3 years ago
Last modified 3 years ago
Make init_only and server_class config options
Status: closed (fixed)
| Reported by: | fumanchu | Assigned to: | rdelon |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | CherryPy code | Keywords: | |
| Cc: |
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:
[global] server.init_only = True server.httpserver = None
Change History
03/07/06 20:22:18: Modified by dowski
03/10/06 06:41:19: Modified by dowski
- status changed from new to closed.
- resolution set to fixed.
Implemented in [1004].
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?