[1.20.2]
Update gogs to 0.13.2
Full Changelog
Security: Path Traversal in file editing UI. GHSA-r7j8-5h9c-f6fx
Security: Path Traversal in file update API. GHSA-qf5v-rp47-55gg
Security: Argument Injection in the built-in SSH server. GHSA-vm62-9jw3-c8w3
Security: Deletion of internal files. GHSA-ccqv-43vm-4f3w
Security: Argument Injection during changes preview. GHSA-9pp6-wq8c-3w2c
Security: Argument Injection when tagging new releases. GHSA-m27m-h5gj-wwmg
Use the non-deprecated section name [email] during installation for email settings. #7704
Use the non-deprecated section name [email] PASSWORD during installation for email password. #7807
Make purple template label color to actually use the hexcode of purple. #7722
@girish Thank you, that worked. Though now I'm realizing that I'm not sure if this migration process will work, because the Gogs version we are running is newer than the upgrade process allows:( But glad we can now run these commands.
@girish said in Questions about Cloudron Gogs Config File Settings:
It seems the config docs (https://gogs.io/docs/advanced/configuration_cheat_sheet) is now broken.
source still available https://github.com/gogs/docs/blob/b3379ec57b24f2a9a079c0cd9fede86fec6e3a99/en-US/advanced/configuration_cheat_sheet.md
@b1nar10 if there is also hook support in gogs, then this could be helpful to you. It's how I'm mirroring repos from my gitea to GitHub.
https://blog.9wd.eu/posts/git-mirror/
(what @arshsahzad said) but the username/password appears in a popup dialog immediately after install. But if you dismissed it by mistake, you can find this from the first time setup instructions:
[image: 1619027553859-8af992fd-949b-4f46-8afa-31784a9c22bb-image.png]