Difficult to create Apache configuration with piped logs #4709
Description
Apache HTTPD supports piped logs to allow for writing logs directly to another process via a pipe rather than a file. In addition to being able directly send logs to some log storage system, this can also be useful for avoiding the need to restart Apache which is necessary for rotating the directly-written logs, which can cause issues with busy systems with many long-lived websockets.
The ood-portal-generator inherently adds the @logroot value to the log path, and even if it is an empty string the log_filename method will insert a forward slash, making it impossible to set piped logs via the portal generator. It is currently necessary to skip the creation of log directives and to set up log directives explicitly another way. By special-casing an accesslog/errorlog value that starts with | this can detect this piped log setup and allow configuration with the current portal mechanisms.