I was already tired for a while that the default repo name in git was master. So I took the opportunity when updating Gitea to rename the default branch of the corresponding git repos to main.
...
This has the advantage that I don’t have to remember the port on which Gitea is running and can just type https://idoru/gitea into my browser’s address bar.
...
You need two certificates: the certificate chain to the Root CA and the certificate for gitea. I’m running an own root CA in my LAN (mostly for fun and educational purpose) and issued a cert for gitea.
...
Label files with labels to categorize issues/tickets go into <gitea-install-dir>/conf/options.
Gitea 1.19 introduced a pretty cool new label format. There is an example of a label file on the gitea GitHub page Advanced.yaml. At the time of writing the YAML example misses the three mandatory dashes ‘—’, that indicate the start of a new YAML document.
...
Repos that have been created outside gitea can be imported, or in Gitea speak adopted, and managed by Gitea. I’m using both terms import and adopt here.
...
starting gitea with another user than defined in gitea.conf results in:
... routers/init.go:74:mustInitCtx() [F] code.gitea.io/gitea/modules/git.InitFull(ctx) failed: failed to set git global config diff.algorithm, err: exit status 255 - warning: unable to access '/home/rudolf/.config/git/gitconfig': Permission denied error: could not lock config file /home/rudolf/.config/git/gitconfig: Permission denied - warning: unable to access '/home/rudolf/.config/git/gitconfig': Permission denied error: could not lock config file /home/rudolf/.config/git/gitconfig: Permission denied the fix is to run unset GIT_CONFIG_GLOBAL before running gitea.
...