2018-01-08 23:48:42 +01:00
|
|
|
---
|
2018-05-22 07:34:02 +02:00
|
|
|
date: "2018-05-21T15:00:00+00:00"
|
2018-01-08 23:48:42 +01:00
|
|
|
title: "Support Options"
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 05:33:41 +02:00
|
|
|
slug: "support"
|
2023-04-04 15:47:31 +02:00
|
|
|
weight: 20
|
2020-12-09 07:47:06 +01:00
|
|
|
toc: false
|
2018-01-08 23:48:42 +01:00
|
|
|
draft: false
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 05:33:41 +02:00
|
|
|
aliases:
|
|
|
|
|
- /en-us/seek-help
|
2018-01-08 23:48:42 +01:00
|
|
|
menu:
|
|
|
|
|
sidebar:
|
|
|
|
|
parent: "help"
|
|
|
|
|
name: "Support Options"
|
|
|
|
|
weight: 20
|
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.
1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.
---------
Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 05:33:41 +02:00
|
|
|
identifier: "support"
|
2018-01-08 23:48:42 +01:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Support Options
|
|
|
|
|
|
2023-06-16 08:26:32 +02:00
|
|
|
- [Paid Commercial Support](https://about.gitea.com/)
|
2019-04-13 04:46:52 +02:00
|
|
|
- [Discord](https://discord.gg/Gitea)
|
2018-05-22 07:34:02 +02:00
|
|
|
- [Discourse Forum](https://discourse.gitea.io/)
|
2018-01-08 23:48:42 +01:00
|
|
|
|
2019-04-13 04:46:52 +02:00
|
|
|
**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:
|
|
|
|
|
|
2022-06-24 04:56:46 +02:00
|
|
|
1. Your `app.ini` (with any sensitive data scrubbed as necessary).
|
|
|
|
|
2. The Gitea logs, and any other appropriate log files for the situation.
|
2022-09-07 17:58:55 +02:00
|
|
|
- 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,
|
2022-06-24 04:56:46 +02:00
|
|
|
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`).
|
2022-07-28 03:22:47 +02:00
|
|
|
|
2022-06-24 04:56:46 +02:00
|
|
|
```ini
|
2022-09-07 17:58:55 +02:00
|
|
|
; To show all SQL logs, you can also set LOG_SQL=true in the [database] section
|
2022-06-24 04:56:46 +02:00
|
|
|
[log]
|
|
|
|
|
LEVEL=debug
|
|
|
|
|
MODE=console,file
|
2022-07-28 03:22:47 +02:00
|
|
|
```
|
|
|
|
|
|
2022-06-24 04:56:46 +02:00
|
|
|
3. Any error messages you are seeing.
|
2019-04-13 04:46:52 +02:00
|
|
|
4. When possible, try to replicate the issue on [try.gitea.io](https://try.gitea.io) and include steps so that others can reproduce the issue.
|
2022-07-28 03:22:47 +02:00
|
|
|
- This will greatly improve the chance that the root of the issue can be quickly discovered and resolved.
|
2023-06-12 17:17:43 +02:00
|
|
|
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".
|
2019-04-13 04:46:52 +02:00
|
|
|
|
2018-01-08 23:48:42 +01:00
|
|
|
## Bugs
|
|
|
|
|
|
2019-03-09 22:15:45 +01:00
|
|
|
If you found a bug, please create an [issue on GitHub](https://github.com/go-gitea/gitea/issues).
|
2018-01-08 23:48:42 +01:00
|
|
|
|
|
|
|
|
## Chinese Support
|
|
|
|
|
|
2021-12-03 14:04:32 +01:00
|
|
|
Support for the Chinese language is provided at [Our discourse](https://discourse.gitea.io/c/5-category/5) or QQ Group 328432459.
|
