this post was submitted on 19 Sep 2024

647 points (97.6% liked)

196

16238 readers

1703 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

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

[email protected]

647

efficient game design rule (lemmy.blahaj.zone)

submitted 20 hours ago by [email protected] to c/[email protected]

38 comments fedilink hide all child comments

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

[–] teejay 5 points 16 hours 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

[–] [email protected] 3 points 12 hours 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