LAMP & LAPP (and all LAMP/LAPP based apps) use `other_vhosts_access.log` by default instead of `access.log`

[JedMeister]

This is more of a nice to have rather than a significant issue. And FWIW I recall seeing this before, but never noted it as an issue.

On our LAMP/LAPP (and LAMP/LAPP based) appliances, by default Apache logs all access events to other_vhosts_access.log (/var/log/apache2/other_vhosts_access.log) and the access.log remains empty.

It would be much better if the main site instead logged access events to access.log (/var/log/apache2/access.log). Then any secondary sites could log to the other_vhosts_access.log - as I assume is intended.

As something of an aside, systemd (i.e. the journal) only picks up the Apache error events (so only events from the error log show up there). TBH I'm not necessarily sure if it's a good idea, but perhaps we could consider also logging access events to the journal?

I mention that as often PHP app related issues show up as an access event, rather than an Apache error.

Having said that, I guess that would be resolved assuming we implement https://github.com/turnkeylinux/tracker/issues/1889. I assume then the PHP related issues would show up in the journal related to php-fpm? That would need to be double checked but it seems like a logical thing (to me at least :grin:).