Hi Dan, About the logs in Webtools it's also limited to "OFBiz logs". I mean you can't see the access_logs. They are sometime very useful too.
So yes I agree this would be something we could do. Jacques Le 29/02/2024 à 16:15, Daniel Watford a écrit :
Hello, I was just checking the demo-stable logs - accessible on ofbiz-vm1 at /home/ofbizdocker/demo-stable/logs - and found plenty of interesting stack traces that would be good candidates for investigation. Given that the demo sites use well known administrator passwords and should not contain any sensitive information, how would the project's members feel about making these logs automatically accessible to any interested parties? If it is deemed appropriate to make the logs publicly accessible, we then need to figure out how we could technically do so. One approach I can think of is to add some Alias directives ( https://httpd.apache.org/docs/current/mod/mod_alias.html#alias) to the Apache HTTP Server configuration to map relevant paths to the logs directory of each demo site. For example, to the demo-trunk <VirtualHost> configuration, we could add: Alias "/logs" "/home/ofbizdocker/demo-trunk/logs" Similarly, to the demo-stable <VirtualHost> configuration we would add: Alias "/logs" "/home/ofbizdocker/demo-stable/logs" We would then configure directory listings in Apache HTTP Server for those log directory locations allowing access via a web browser. There is some pre-existing functionality in Web Tools to access logs, but it does require interaction through the OFBiz UI. The ability to retrieve demo-site logs via an unauthenticated HTTP(S) get request might offer some opportunities to automatically scan for a particular class of error and might make it easier for ofbiz developers to check on the demo logs from time to time. Thanks, Dan.
