forked from NYANDEV/forgejo
2eb456dde2
This PR adds our matrix space to the support options and alphabetizes the list. I also considered adding our Mastodon, however that isn't as suitable as the other options because it's just whoever has access to the account vs a community chat/forum. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>
2.2 KiB
2.2 KiB
date | title | slug | sidebar_position | toc | draft | aliases | menu | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2018-05-21T15:00:00+00:00 | Support Options | support | 20 | false | false |
|
|
Support Options
- Paid Commercial Support
- Discord
- Discourse Forum
- Matrix
- NOTE: Most of the Matrix channels are bridged with their counterpart in Discord and may experience some degree of flakiness with the bridge process.
NOTE: When asking for support, it may be a good idea to have the following available so that the person helping has all the info they need:
-
Your
app.ini
(with any sensitive data scrubbed as necessary). -
The Gitea logs, and any other appropriate log files for the situation.
- When using systemd, use
journalctl --lines 1000 --unit gitea
to collect logs. - When using docker, use
docker logs --tail 1000 <gitea-container>
to collect logs. - By default, the logs are outputted to console. If you need to collect logs from files,
you could copy the following config into your
app.ini
(remove all other[log]
sections), then you can find the*.log
files in Gitea's log directory (default:%(GITEA_WORK_DIR)/log
).
; To show all SQL logs, you can also set LOG_SQL=true in the [database] section [log] LEVEL=debug MODE=console,file
- When using systemd, use
-
Any error messages you are seeing.
-
When possible, try to replicate the issue on try.gitea.io and include steps so that others can reproduce the issue.
- This will greatly improve the chance that the root of the issue can be quickly discovered and resolved.
-
If you encounter slow/hanging/deadlock problems, please report the stack trace when the problem occurs. Go to the "Site Admin" -> "Monitoring" -> "Stacktrace" -> "Download diagnosis report".
Bugs
If you found a bug, please create an issue on GitHub.
Chinese Support
Support for the Chinese language is provided at Our discourse or QQ Group 328432459.