this post was submitted on 19 Sep 2024

745 points (97.8% liked)

196

16430 readers

2490 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago

MODERATORS

moss@lemmy.blahaj.zone

greembow@lemmy.blahaj.zone

moss@lemmy.world

queue@beehaw.org

funky_rodent@lemmy.blahaj.zone

PeachyMcPeachface@lemmy.blahaj.zone

threegnomes@lemmy.blahaj.zone

greembow@lemmy.world

remotelove@lemmy.ca

Roflmasterbigpimp@feddit.de

qaz@lemmy.world

A_Very_Big_Fan@lemm.ee

qaz@lemmy.blahaj.zone

A_Very_Big_Fan@lemmy.world

qaz@lemmy.dbzer0.com

qaz@sh.itjust.works

qaz@lemmy.sdf.org

745

efficient game design rule (lemmy.blahaj.zone)

submitted 1 month ago by nicknonya@lemmy.blahaj.zone to c/196@lemmy.blahaj.zone

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 1 month ago (1 children)

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@lemmy.blahaj.zone 4 points 1 month 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