summaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Add option to disable ambiguous unicode characters detection (#28454) (#28499)wxiaoguang2023-12-181-0/+1
| | | | | | | | Backport #28454 (the only conflict is caused by some comments) * Close #24483 * Close #28123 * Close #23682 * Close #23149
* Update docs for DISABLE_QUERY_AUTH_TOKEN (#28485) (#28488)Giteabot2023-12-161-0/+1
| | | | | | | | Backport #28485 by @kdumontnu As described [here](https://github.com/go-gitea/gitea/pull/28390#issuecomment-1857553331). Co-authored-by: Kyle D <kdumontnu@gmail.com>
* Fix Chinese translation of config cheat sheet[API] (#28472) (#28473)Giteabot2023-12-151-4/+5
| | | | | Backport #28472 by @CaiCandong Co-authored-by: CaiCandong <50507092+CaiCandong@users.noreply.github.com>
* Fix documents for "custom/public/assets/" (#28465) (#28467)Giteabot2023-12-145-8/+8
| | | | | | | Backport #28465 by wxiaoguang Fix #28463 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Fix links in docs (#28302) (#28418)Giteabot2023-12-115-10/+6
| | | | | | | | | | | | | Backport #28302 by @yp05327 Close #28287 ## How to test it in local convert Makefile L34 into: ``` cd .tmp/upstream-docs && git clean -f && git reset --hard && git fetch origin pull/28302/head:pr28302 && git switch pr28302 ``` Co-authored-by: yp05327 <576951401@qq.com>
* Revert move installation/upgrade-from-gogs.md in 1.21 (#28235)yp053272023-11-272-0/+2
| | | https://github.com/go-gitea/gitea/pull/28233#discussion_r1405539630
* Fix links in docs (#28234) (#28238)Giteabot2023-11-273-3/+3
| | | | | | | | | | | | | Backport #28234 by @yp05327 Follow #28191 Changes: - `(doc/administration/config-cheat-sheet.md` is incorrect: ![image](https://github.com/go-gitea/gitea/assets/18380374/1c417dd7-61a0-49ba-8d50-871fd4c9bf20) - remove `../../` Co-authored-by: yp05327 <576951401@qq.com>
* Docs: Replace deprecated IS_TLS_ENABLED mailer setting in email setup ↵Giteabot2023-11-252-2/+2
| | | | | | | | | | | | | | | (#28205) (#28208) Backport #28205 by @CodeShakingSheep In the [docs for email setup](https://docs.gitea.com/administration/email-setup) `mailer.IS_TLS_ENABLED` is mentioned which was replaced by `mailer.PROTOCOL` in release 1.18.0 according to https://blog.gitea.com/release-of-1.18.0/ . This change wasn't reflected in the docs for email setup. I just replaced the deprecated mailer setting. Co-authored-by: CodeShakingSheep <19874562+CodeShakingSheep@users.noreply.github.com>
* Fix some incorrect links in docs (#28191) (#28201)Giteabot2023-11-247-7/+5
| | | | | | | | | | | | Backport #28191 by @yp05327 https://gitea.com/gitea/gitea-docusaurus/actions/runs/661/jobs/0#jobstep-9-39 I noticed that there are many warning logs in building docs. It is causing 404 in docs.gitea.com now, so we need to fix it. And there are also some other problems in v1.19 which can not be done in this PR. Co-authored-by: yp05327 <576951401@qq.com>
* Fix the description about the default setting for action in quick start ↵Giteabot2023-11-222-2/+2
| | | | | | | | | | | | document (#28160) (#28168) Backport #28160 by @yp05327 Since #27054, Actions are enabled by default. so we should also edit the document. 😃 ps: I think this should be backport to 1.21.0. Co-authored-by: yp05327 <576951401@qq.com>
* Update docs for docusaurus v3 (#28126)John Olheiser2023-11-205-10/+10
| | | Signed-off-by: jolheiser <john.olheiser@gmail.com>
* Change default size of issue/pr attachments and repo file (#27946) (#28017)Giteabot2023-11-132-4/+4
| | | | | | | | Backport #27946 by @lng2020 As title. Some attachments and file sizes can easily be larger than these limits Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Document REACTION_MAX_USER_NUM setting option (#27954) (#27959)Giteabot2023-11-081-0/+1
| | | | | | | | | | Backport #27954 by @6543 as title --- *Sponsored by Kithara Software GmbH* Co-authored-by: 6543 <m.huber@kithara.com>
* Remove `known issue` section in Gitea Actions Doc (#27930) (#27938)Giteabot2023-11-062-62/+0
| | | | | | | | | | | Backport #27930 by @lng2020 The bug has been fixed for several months in the `docker/build-push-action` The fix commit is [d8823bfaed](https://github.com/docker/build-push-action/commit/d8823bfaed2a82c6f5d4799a2f8e86173c461aba) as the Gitea Actions Doc mentioned too. Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* refactor postgres connection string building (#27723) (#27869)Giteabot2023-11-011-1/+3
| | | | | | | | | | | | Backport #27723 by @mpldr This patchset changes the connection string builder to use net.URL and the host/port parser to use the stdlib function for splitting host from port. It also adds a footnote about a potentially required portnumber for postgres UNIX sockets. Fixes: #24552 Co-authored-by: Moritz Poldrack <33086936+mpldr@users.noreply.github.com>
* doc: actions/act-runner: document running as a systemd service (#27844) (#27866)Giteabot2023-11-011-0/+34
| | | | | | | | Backport #27844 by @nodiscc This documents running `act-runner` as a systemd service under a dedicated user account. Co-authored-by: nodiscc <nodiscc@gmail.com>
* Fix wrong relative path on obtain token from command line (#27850) (#27851)Giteabot2023-10-312-1/+3
| | | | | | | Backport #27850 by @lunny Caused by #27845 Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* doc: actions/act-runner: document obtaining a runner registration token from ↵Giteabot2023-10-301-0/+6
| | | | gitea CLI (#27845) (#27848)
* Change the default branch in the agit docs (#27621) (#27623)Giteabot2023-10-152-6/+6
| | | | | | | | Backport #27621 by @lng2020 It's main now. relevant #27579 Co-authored-by: Nanguan Lin <70063547+lng2020@users.noreply.github.com>
* Increase queue length (#27555) (#27562)Giteabot2023-10-102-2/+2
| | | | | | | | | | | | | | | Backport #27555 by @wolfogre It should be OK to increase the default queue length since the default type is "level". IMO, the old default length (100) is a little too small. See https://github.com/go-gitea/gitea/issues/27540#issuecomment-1754269491 IIRC, a larger length could lead to more memory usage only when the type is "channel," but it's an obscure case. Otherwise, it's just a limit (for "level" or "redis"). Co-authored-by: Jason Song <i@wolfogre.com>
* Enable markdownlint `no-duplicate-header` (#27500) (#27506)Giteabot2023-10-074-9/+9
| | | | | | | | | | | | | | | | | | | | | Backport #27500 by @silverwind Duplicate headers in a single Markdown document are problemlematic because the auto-generated links won't be stable. Enable this rule with no exceptions which is also the default of `markdownlint`. For example: ```md # A ## Example # B ## Example ``` Docasaurus will generated `example` and `example-1` links for this. If the first heading is altered, the link `example` will unexpectedly move to the second example heading. Ref: https://github.com/go-gitea/gitea/pull/27461#discussion_r1347987659 Co-authored-by: silverwind <me@silverwind.io>
* Make Actions tasks/jobs timeouts configurable by the user (#27400) (#27402)Giteabot2023-10-031-0/+3
| | | | | | | | | | | | | | | | | | | | | Backport #27400 by @fantognazza With this PR we added the possibility to configure the Actions timeouts values for killing tasks/jobs. Particularly this enhancement is closely related to the `act_runner` configuration reported below: ``` # The timeout for a job to be finished. # Please note that the Gitea instance also has a timeout (3h by default) for the job. # So the job could be stopped by the Gitea instance if it's timeout is shorter than this. timeout: 3h ``` --- Setting the corresponding key in the INI configuration file, it is possible to let jobs run for more than 3 hours. Signed-off-by: Francesco Antognazza <francesco.antognazza@gmail.com>
* Enable production source maps for index.js, fix CSS sourcemaps (#27291) (#27295)Giteabot2023-09-272-4/+16
| | | | | | | | | | | | | | | | | Backport #27291 by @silverwind Previously, the production build never output sourcemaps. Now we emit one file for `index.js` because it is the most likely one where we need to be able to better debug reported issues like https://github.com/go-gitea/gitea/issues/27213. This will currently increase the binary size of gitea by around 700kB which is what the gzipped source map file has. Also, I fixed the CSS sourcemap generation which was broken since the introduction of lightningcss. The chinese docs are machine-translated, please correct accordingly. Co-authored-by: silverwind <me@silverwind.io>
* Update database-preparation and add note re: MariaDB (#27232) (#27236)Giteabot2023-09-251-3/+3
| | | | | | | | Backport #27232 by @techknowlogick update DB docs per feedback. https://gitea.com/gitea/gitea-docusaurus/issues/69 Co-authored-by: techknowlogick <techknowlogick@gitea.com>
* Improve actions docs related to `pull_request` event (#27126)Zettat1232023-09-202-0/+6
| | | | | | Related to #27039 The `ref` property in Gitea Actions is different from GitHub Actions. This PR improves the documentation to explain the difference.
* Remove outdated paragraphs when comparing Gitea Actions to GitHub Actions ↵delvh2023-09-202-20/+14
| | | | | | | | | (#27119) No backport needed as this new state only applies to 1.21+ --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Use fetch helpers instead of fetch (#27026)silverwind2023-09-191-1/+1
| | | | | | | | | | | | WIP because: - [x] Some calls set a `content-type` but send no body, can likely remove the header - [x] Need to check whether `charset=utf-8` has any significance on the webauthn calls, I assume not as it is the default for json content. - [x] Maybe `no-restricted-globals` is better for eslint, but will require a lot of duplication in the yaml or moving eslint config to a `.js` extension. - [x] Maybe export `request` as `fetch`, shadowing the global.
* Support `.git-blame-ignore-revs` file (#26395)KN4CK3R2023-09-162-0/+39
| | | | | | | | | | | | | | | | | Closes #26329 This PR adds the ability to ignore revisions specified in the `.git-blame-ignore-revs` file in the root of the repository. ![grafik](https://github.com/go-gitea/gitea/assets/1666336/9e91be0c-6e9c-431c-bbe9-5f80154251c8) The banner is displayed in this case. I intentionally did not add a UI way to bypass the ignore file (same behaviour as Github) but you can add `?bypass-blame-ignore=true` to the url manually. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Actions are no longer experimental, so enable them by default (#27054)Lunny Xiao2023-09-152-2/+2
| | | | This PR makes the actions enabled by default, so people will find it easier to enable actions in repository setting.
* Update brew installation documentation since gitea moved to brew core ↵Lunny Xiao2023-09-154-4/+0
| | | | | package (#27070) ref: https://gitea.com/gitea/homebrew-gitea/pulls/178
* add sparse url in cargo package guide (#26937)merlleu2023-09-132-4/+12
| | | | | | | | | | | | | | Hello, The current package guide for cargo gives you only the git index, with the HTTP Index stabilized being used as default for crates.io and being better for most use-cases. However, it's not documented that gitea supports the sparse spec, and it does not require the _crates-index git repo for the sparse api. I personally think we should push users to use the sparse instead of the git repository. (Even let users disable crates-index repos if they only want to use sparse)
* Use secure cookie for HTTPS sites (#26999)wxiaoguang2023-09-112-2/+2
| | | | | | | | | | | If the AppURL(ROOT_URL) is an HTTPS URL, then the COOKIE_SECURE's default value should be true. And, if a user visits an "http" site with "https" AppURL, they won't be able to login, and they should have been warned. The only problem is that the "language" can't be set either in such case, while I think it is not a serious problem, and it could be fixed easily if needed. ![image](https://github.com/go-gitea/gitea/assets/2114189/7bc9a859-dcc1-467d-bc7c-1dd6a10389e3)
* Add fetch wrappers, ignore network errors in actions view (#26985)silverwind2023-09-111-0/+6
| | | | | | | | | | | | | | | 1. Introduce lightweight `fetch` wrapper functions that automatically sets csfr token, content-type and use it in `RepoActionView.vue`. 2. Fix a specific issue on `RepoActionView.vue` where a fetch network error is shortly visible during page reload sometimes. It can be reproduced by F5-in in quick succession on the actions view page and was also producing a red error box on the page. Once approved, we can replace all current `fetch` uses in UI with this in another PR. --------- Co-authored-by: Giteabot <teabot@gitea.io>
* Correct the database.LOG_SQL default value in config cheat sheet (#26997)Infinoid2023-09-102-2/+2
| | | | | The default is false, fix the docs to reflect that. Fixes: #26989
* Add reverseproxy auth for API back with default disabled (#26703)Lunny Xiao2023-09-071-1/+2
| | | | | | | | | | | | | | | This feature was removed by #22219 to avoid possible CSRF attack. This PR takes reverseproxy auth for API back but with default disabled. To prevent possbile CSRF attack, the responsibility will be the reverseproxy but not Gitea itself. For those want to enable this `ENABLE_REVERSE_PROXY_AUTHENTICATION_API`, they should know what they are doing. --------- Co-authored-by: Giteabot <teabot@gitea.io>
* Update nginx recommendations (#26924)silverwind2023-09-061-0/+2
| | | | | | | | - `Connection` and `Upgrade` [needed for websockets](https://www.nginx.com/blog/websocket-nginx/) - ~~`X-Real-IP` unnecessary and duplicate with `X-Forwarded-For`. [chi checks both headers](https://github.com/go-chi/chi/blob/master/middleware/realip.go), but XFF is definitely the more "standard" one.~~
* docs: Update Profile README information (#26947)Panagiotis "Ivory" Vasilopoulos2023-09-061-2/+2
| | | Follow-up of https://github.com/go-gitea/gitea/pull/26295
* Add a documentation note for Windows Service (#26938)KazzmanK2023-09-061-0/+9
| | | | | | Service may fail to start at boot time with timeout Resolves #26934 Co-authored-by: Nikolay Kobzarev <n.kobzarev@aeronavigator.ru>
* Artifacts retention and auto clean up (#26131)FuXiaoHei2023-09-061-0/+7
| | | | | | | | | | | | | | Currently, Artifact does not have an expiration and automatic cleanup mechanism, and this feature needs to be added. It contains the following key points: - [x] add global artifact retention days option in config file. Default value is 90 days. - [x] add cron task to clean up expired artifacts. It should run once a day. - [x] support custom retention period from `retention-days: 5` in `upload-artifact@v3`. - [x] artifacts link in actions view should be non-clickable text when expired.
* Improve LDAP group config documentation, fixes #21159 (#21227)Sven Seeberg2023-09-051-4/+5
| | | | Improve the wording of the LDAP group attributes documentation and expand the examples.
* Update backup instructions to align with archive structure (#26902)JonRB2023-09-051-7/+7
| | | | Signed-off-by: JonRB <jon.roadleybattin@gmail.com> fixes https://github.com/go-gitea/gitea/issues/25878
* Update documents to fix some links (#26885)Lunny Xiao2023-09-0310-13/+13
|
* clarify aspects of the dump command (#26887)JonRB2023-09-031-2/+2
| | | | | | | | | clarify aspects of the dump command Possibly closes #26862 --------- Co-authored-by: delvh <dev.lh@web.de>
* Update docs about attachment path (#26883)CaiCandong2023-09-032-2/+2
| | | | | | | | | | | | | | | | | | This change was caused by #26271, for configuration as below: ``` [attachment] ENABLE = true PATH = data/attachments MAX_SIZE = 100 MAX_FILES = 5 ``` Before #26271, the resolved path is ${AppWorkPath}/${attachments.PATH} (such as `/var/lib/gitea/data/attachments`) After #26271, the resolved path is ${AppDataPath}/${attachments.PATH} (such as `/var/lib/gitea/data/data/attachments`) Fix https://github.com/go-gitea/gitea/issues/26864 Follow https://github.com/go-gitea/gitea/pull/26271
* Improve the "bug report" template and "support options" document (#26753)wxiaoguang2023-08-281-22/+45
| | | | | | | * `/help/support` is a better document than `/administration/logging-config` for bug reporting * Improve `support.en-us.md` * Move/add detailed contents into `Advanced Bug Report Tips` section * Merge `Chinese Support` section into `Support Options`
* Expanded minimum RSA Keylength to 3072 (#26604)mainboarder2023-08-284-4/+4
| | | | | | | | | | | | | | | German Federal Office for Information Security requests in its technical guideline BSI TR-02102-1 RSA Keylength not shorter than 3000bits starting 2024, in the year 2023 3000bits as a recommendation. Gitea should request longer RSA Keys by default in favor of security and drop old clients which do not support longer keys. https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR02102/BSI-TR-02102.pdf?__blob=publicationFile&v=9 - Page 19, Table 1.2 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Use docs.gitea.com instead of docs.gitea.io (#26739)Lunny Xiao2023-08-2725-44/+44
|
* Prefer variables over subprocesses (#26690)Thomas McWork2023-08-231-3/+3
| | | | … because it doesn't require a separate shell, spawning a process which cost unnecessary resources and takes time.
* add mfa doc (#26654)Lunny Xiao2023-08-221-0/+35
| | | | | | | | | | | | | | | copy and modified from #14572 > Whilst debating enforcing MFA within our team, I realised there isn't a lot of context to the side effects of enabling it. Most of us use Git over HTTP and would need to add a token. I plan to add another PR that adds a sentence to the UI about needing to generate a token when enabling MFA if HTTP is to be used. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io> Co-authored-by: silverwind <me@silverwind.io>
* Update minimum password length requirements (#25946)techknowlogick2023-08-211-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-25 14:34:11 +0000