You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we may have four wsgi scripts serve for different purposes:
WSGIScriptAlias /live .../checkerweb.wsgi for showing released version of CF
WSGIScriptAlias /live-dev .../checkerweb-dev.wsgi for showing development version of CF
WSGIScriptAlias /rise4fun .../checkerweb-rise4fun.wsgi for rise4fun integration
WSGIScriptAlias /rise4run-dev .../checkerweb-rise4fun-dev.wsgi for rise4fun integration development
All of above wsgi scripts delegate to the same virtual host listening on port 80 because we currently only have 80 port avaliable for public access, which means these wsgi scripts will also have to share the same apache log files (error log and access log) because apache only allocate one set of log files per virtual host.
Thus, we might need to customise our log format in order to distinguish logs of these wsgi scripts.
Now we may have four wsgi scripts serve for different purposes:
All of above wsgi scripts delegate to the same virtual host listening on port 80 because we currently only have 80 port avaliable for public access, which means these wsgi scripts will also have to share the same apache log files (error log and access log) because apache only allocate one set of log files per virtual host.
Thus, we might need to customise our log format in order to distinguish logs of these wsgi scripts.
Following links might be helpful (not carefully read about it, but leave here for possible future use):
http://httpd.apache.org/docs/2.0/vhosts/fd-limits.html#splitlogs
http://httpd.apache.org/docs/2.0/mod/mod_log_config.html#logformat
http://httpd.apache.org/docs/2.0/programs/other.html
The text was updated successfully, but these errors were encountered: