You are viewing a single thread.
View all comments View context
5 points

Essentially, when your log file reaches a configured size, it should create a new one and start writing into that, deleting archiving the oldest

FTFY

permalink
report
parent
reply
4 points

Sure! Best practices vary to your application. I’m a dev, so I’m used to configuring stuff for local env use. In prod, archiving is definitely nice so you can track back even through heavy logging. Though, tbh, if you’re applications getting used by that many people a db logging system is probably just straight better

permalink
report
parent
reply