[Contrib] Logrotate

[bagasme]

This PR adds sample logrotate configuration and corresponding docs entry.

[zeripath]

You know there is built in log rotation? It's slightly different from logrotate but it is there.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@20f6acc). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #9866   +/-   ##
=========================================
  Coverage          ?   42.28%           
=========================================
  Files             ?      605           
  Lines             ?    79248           
  Branches          ?        0           
=========================================
  Hits              ?    33507           
  Misses            ?    41612           
  Partials          ?     4129

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 20f6acc...115ca5d. Read the comment docs.

[bagasme]

Don't merge until #9869 feature is available, to let users choose between Gitea's implementation or external tools.

[zeripath]

Please see: https://docs.gitea.io/en-us/config-cheat-sheet/#file-log-mode-log-file-log-file-or-mode-file

[bagasme]

@zeripath Aha! I overlooked it.

[techknowlogick]

I'm unsure of merging this PR as-is, as it is pretty generic and other guides on configuring logrotate might be better. Especially since it would need customization based on the specific user setup (some downstream linux distributions have different settings than what is defined on the "install from source page"), and due to that I suspect this may add to confusion about configuration.

Maybe a quick "Gitea includes log rotation built-in, but if you want to use logrotate here is the setting you need to disable" (or something along those lines) and you can put it on the logging page: https://docs.gitea.io/en-us/logging-configuration/

[bagasme]

@techknowlogick For your suggestion I will address on another PR.

[silverwind]

This restart is unnecessary, it's probably enough to enable copytruncate and remove both the postrotate and create options.

[bagasme]

No no no,

Many application use restart-after-logrotate technique, and Gitea should too.

[silverwind]

That is a recipe for disaster. What if the application fails to restart? You certainly don't want logrotate to be able to cause a service outage.

[bagasme]

@silverwind hmm... logrotate should be blamed

[techknowlogick]

Closing per #9930