aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content
Commit message (Collapse)AuthorAgeFilesLines
* Update comparison page with RhodeCode CE & EE (#27329)Marcin Kuźmiński2023-09-291-99/+99
| | | Update RhodeCode features and add EE version
* Fix chinese translation (#27296)Lunny Xiao2023-09-271-5/+5
| | | | Fix translation from #27291 Source Map will be kept as English in Chinese usage habit.
* Enable production source maps for index.js, fix CSS sourcemaps (#27291)silverwind2023-09-262-4/+16
| | | | | | | | | | | 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.
* Update database-preparation and add note re: MariaDB (#27232)techknowlogick2023-09-241-3/+3
| | | | update DB docs per feedback. https://gitea.com/gitea/gitea-docusaurus/issues/69
* 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-161-0/+38
| | | | | | | | | | | | | | | | | 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
|
* docs: template variables (#26547)lonix12023-08-191-2/+12
| | | | | | Explanation for using gitea's variables in `.tmpl` files. Thanks to @wxiaoguang for advising me on [discord](https://discord.com/channels/322538954119184384/561007778139734027/1141217820441587722).
* Update zh-cn documentation (#26406)CaiCandong2023-08-1411-443/+1513
|
* Rename `Sync2` -> `Sync` (#26479)delvh2023-08-134-4/+4
| | | | | | | | | The xorm `Sync2` has already been deprecated in favor of `Sync`, so let's do the same inside the Gitea codebase. Command used to replace everything: ```sh for i in $(ag Sync2 --files-with-matches); do vim $i -c ':%sno/Sync2/Sync/g' -c ':wq'; done ```
* Add matrix to support (#26382)John Olheiser2023-08-121-0/+2
| | | | | | | | | | | | | 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>
* Update index doc (#26455)CaiCandong2023-08-122-464/+40
| | | | | | In the previous feature description, numerous functionalities of Gitea were listed, which appeared redundant and failed to highlight the unique characteristics of Gitea. Therefore, I have rewritten this section based on the description provided on the official Gitea website
* Update upgrade documentation to add a check for deprecated configurations ↵Lunny Xiao2023-08-112-8/+25
| | | | | | | | | | (#26451) fix https://github.com/go-gitea/gitea/issues/25995#issuecomment-1674096710 --------- Co-authored-by: silverwind <me@silverwind.io>
* Pre-register OAuth2 applications for git credential helpers (#26291)Denys Konovalov2023-08-092-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | This PR is an extended implementation of #25189 and builds upon the proposal by @hickford in #25653, utilizing some ideas proposed internally by @wxiaoguang. Mainly, this PR consists of a mechanism to pre-register OAuth2 applications on startup, which can be enabled or disabled by modifying the `[oauth2].DEFAULT_APPLICATIONS` parameter in app.ini. The OAuth2 applications registered this way are being marked as "locked" and neither be deleted nor edited over UI to prevent confusing/unexpected behavior. Instead, they're being removed if no longer enabled in config. ![grafik](https://github.com/go-gitea/gitea/assets/47871822/81a78b1c-4b68-40a7-9e99-c272ebb8f62e) The implemented mechanism can also be used to pre-register other OAuth2 applications in the future, if wanted. Co-authored-by: hickford <mirth.hickford@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> --------- Co-authored-by: M Hickford <mirth.hickford@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* [docs] Add missing backtick in quickstart.zh-cn.md (#26349)Track32023-08-061-1/+1
| | | | | | Added missing backtick in quickstart.zh-cn.md docs so inline code can render properly. Co-authored-by: Giteabot <teabot@gitea.io>
* Remove backslashed newlines on markdown (#26344)Lunny Xiao2023-08-051-2/+2
| | | Fix https://gitea.com/gitea/gitea-docusaurus/issues/56
* Fix typos and grammer problems for actions documentation (#26328)sillyguodong2023-08-042-16/+19
| | | | follow #26317 fix typos and adjust grammer problems.
* Update documentation for 1.21 actions (#26317)sillyguodong2023-08-042-4/+60
| | | | | As title. Close #26309 Related to #24724, #24806
* Update Gmail example (#26302)Bård Aase2023-08-031-2/+1
| | | | The `IS_TLS_ENABLED` option in the `mailer` section is deprecated. This is specified by setting `PROTOCOL=smtps`
* Clarify the logger's MODE config option (#26267)wxiaoguang2023-08-011-0/+3
| | | | | | | 1. Fix the wrong document (add the missing `MODE=`) 2. Add a more friendly log message to tell users to add `MODE=` in their config Co-authored-by: Giteabot <teabot@gitea.io>
* Update Arch linux URL from community to extra (#26273)minijaws2023-08-011-1/+1
| | | | Arch linux package link has changed from the community repo to the extra repo. The link has been updated.
* Mention `devtest` in frontend contributing guidelines (#26249)Denys Konovalov2023-07-311-0/+4
| | | | | Our `devtest` page contains some good UI examples which should be taken as example when working on Gitea UI. Mention it in our frontend contributing guidelines to for new contributors to know about it.
* Add 'Show on a map' button to Location in profile, fix layout (#26214)Panagiotis "Ivory" Vasilopoulos2023-07-311-0/+1
| | | | | | | | | | | Not too important, but I think that it'd be a pretty neat touch. Also fixes some layout bugs introduced by a previous PR. --------- Co-authored-by: Gusted <postmaster@gusted.xyz> Co-authored-by: Caesar Schinas <caesar@caesarschinas.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Calculate MAX_WORKERS default value by CPU number (#26177)wxiaoguang2023-07-271-1/+1
| | | | | | To avoid consuming user's 100% CPU, limit the default value of MAX_WORKERS Fix #26063 (the CPU 100% problem mentioned in it)
* Update email-setup.en-us.md (#26068)Felix Victor2023-07-266-15/+10
| | | | | | | | The setting `MAILER_TYPE` is deprecated. According to the config cheat sheet, it should be `PROTOCOL`. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Update Chinese documents (#26139)Upstream80222023-07-263-39/+113
| | | Update part of the documents, translate English to Chinese.
* Docusaurus-ify (#26051)John Olheiser2023-07-26260-1330/+785
| | | | | | | | | | | | | | 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>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-24 12:19:30 +0000