No webserver access logs #2

New Issue

jlobbes · 2022-12-01T00:33:32Z

jlobbes commented

2022-12-01 00:33:32 +00:00

Currently, no web server access logs are being produced.
The access logs should be printed to stdout and/or to a file.

Inspiration on how to set that up can be found here and here.

Further reading, if interested, is here.

Currently, no web server access logs are being produced. The access logs should be printed to `stdout` and/or to a file. Inspiration on how to set that up can be found [here](https://stackoverflow.com/questions/52372187/logging-with-command-line-waitress-serve) and [here](https://gist.github.com/alexaleluia12/e40f1dfa4ce598c2e958611f67d28966). Further reading, if interested, is [here](https://leftasexercise.com/2020/01/24/wsgi-middleware-pastedeploy-and-all-that/).

jlobbes added the

high priority

improvement

labels 2022-12-01 00:49:01 +00:00

jlobbes commented

2022-12-01 19:15:02 +00:00

Fixed in f501acf839.

Request logs now get printed to stdout in the container.
An option to log to file is now available in the instance config.

Fixed in https://git.skyforest.net/jlobbes/lumi2/commit/f501acf8393bf3ded20488d68c4de6dad4803170. Request logs now get printed to stdout in the container. An option to log to file is now available in the instance config.

jlobbes closed this issue

2022-12-01 19:15:02 +00:00

jlobbes removed the

high priority

label 2022-12-01 19:15:16 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jlobbes/lumi2#2