fedi/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-20 23:49:23 +00:00
Code Issues Packages Projects Releases Wiki Activity
forgejo/docs/content/help/support.en-us.md
John Olheiser bd4c7ce578
Docusaurus-ify (#26051) 
This PR cleans up the docs in a way to make them simpler to ingest by
our [docs repo](https://gitea.com/gitea/gitea-docusaurus).

1. It includes all of the sed invocations our ingestion did, removing
the need to do it at build time.
2. It replaces the shortcode variable replacement method with
`@variable@` style, simply for easier sed invocations when required.
3. It removes unused files and moves the docs up a level as cleanup.

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-07-26 04:53:13 +00:00

2 KiB
Raw Blame History

date title slug sidebar_position toc draft aliases menu
2018-05-21T15:00:00+00:00 Support Options support 20 false false
/en-us/seek-help
sidebar
parent name sidebar_position identifier
help Support Options 20 support

Support Options

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:

  1. Your app.ini (with any sensitive data scrubbed as necessary).

  2. 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

  3. Any error messages you are seeing.

  4. 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.

  5. 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.