Is it possible to configure the Apache Logs in Wordpress (Developer)?

[Lonkle]

Title says it all. Specifically the types of log / notices being sent. Just getting tired of the Cloudron Healthcheck Access service getting logged when I'm trying to log more important things (specifically PHP notices and errors only).

[Lonkle]

I'm trying to basically throw the apache access_logs into dev/null unless I really need them one day and I'll comment it out.

[Lonkle]

So far I've found no documentation to do so which is weird cause it's not that uncommong, access logs and error logs are separate to begin with so I just need to take access_log and send it to dev/null - I mean, there is an apache folder at the root of Wordpress (Developer), and it's accepting new commands - I just have to figure out the command to throw out access logs since I can't "comment it out" at the base .conf I'm guessing is used in addition to the one in /app/data/apache/

[Lonkle]

Really thought this was gonna work:

SetEnvIf Request_URI "^/wp-includes/version.php$" dontlog
CustomLog /dev/stdout combined env=!dontlog

since that's the specific URL the healthcheck uses so I tried to make it just not log that path. Failed again, next test.

Note: Obviously the healtcheck is important what the status isn't 200 OK, but so distracting in the logs showing up every 10 seconds or so.

[Lonkle]

I couldn't even stop all logging via:

ErrorLog /dev/null
CustomLog /dev/null combined

so this must be something I can only solve by installing my own LAMP because the log .conf are out of my reach in the Wordpress (Developer) installation. But I don't want to miss out on updates, and LDAP.

[girish]

Currently, you cannot change this, no. You have to use the LAMP app if you want to change the apache configs. In the LAMP app, there is an app.conf which gives you control over logging.

[Lonkle]

@girish said in Is it possible to configure the Apache Logs in Wordpress (Developer)?:

Currently, you cannot change this, no. You have to use the LAMP app if you want to change the apache configs. In the LAMP app, there is an app.conf which gives you control over logging.

You'd expressed interest in more fine-control over logging in another thread. If that's still true, I'll deal with the Apache over-Logging for now looking forward to a time where we figure out a solution for a way to best configure logs for the end-user.

Going to LAMP would just feel like I'd be contributing less and less to the Wordpress (Developer) and (Managed) codebase(s) and that's my real goal. To make Wordpress (Developer) the best it can be in Cloudron.

So maybe, one day, those access logs will be configurable.