765

efficient game design rule (lemmy.blahaj.zone)

submitted 3 months ago by nicknonya to c/196

47 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] teejay@lemmy.world 5 points 3 months ago

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

[-] pixeltree 4 points 3 months ago

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