aboutsummaryrefslogtreecommitdiffstats
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
...
* refactor postgres connection string building (#27723)Moritz Poldrack2023-11-011-1/+3
| | | | | | | | 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
* doc: actions/act-runner: document running as a systemd service (#27844)nodiscc2023-11-011-0/+34
| | | | This documents running `act-runner` as a systemd service under a dedicated user account.
* Fix wrong relative path on obtain token from command line (#27850)Lunny Xiao2023-10-302-1/+3
| | | Caused by #27845
* doc: actions/act-runner: document obtaining a runner registration token from ↵nodiscc2023-10-301-0/+6
| | | | gitea CLI (#27845)
* Fix an indentation in the Chinese documentation of Act Runner (#27730)HoshinoRei2023-10-221-6/+6
| | | | | | In the [English document](https://docs.gitea.com/1.21/usage/actions/act-runner#configuring-cache-when-starting-a-runner-using-docker-image), there is indentation here, but there is no indentation in the Chinese document.
* [docs] Add note that PROTOCOL config is case-sensitive (#25685)MiloCubed2023-10-191-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See [issue on gitea.com](https://gitea.com/gitea/gitea-docusaurus/issues/38), copied below for convenience: > Hello, may I first confirm that the app.ini PROTOCOL config is case sensitive (must be lowercase)? > > If so, I'd like to suggest for it to be highlighted in the [HTTPS Setup](https://docs.gitea.com/administration/https-setup#using-the-built-in-server) page. > Perhaps something like: > For the PROTOCOL=https field, make sure https is lowercase. Writing PROTOCOL=HTTPS may result in a SSL_ERROR_RX_RECORD_TOO_LONG error on Firefox or ERR_SSL_PROTOCOL_ERROR on Chrome and Edge. > > Background > At first I carelessly wrote PROTOCOL=HTTPS in my app.ini, and Firefox didn't allow me to connect because: > Secure Connection Failed > An error occurred during a connection to gitea.local.lan. SSL received a record that exceeded the maximum permissible length. > Error code: SSL_ERROR_RX_RECORD_TOO_LONG > I spent maybe half an hour troubleshooting my certs, ports, and other configs before backtracking to the start and realizing the capitalization difference there 😅. When I changed that config to lowercase, it worked. For this PR I added the note in the Config Cheat Sheet page and fixed the links to it from the HTTPS Setup page. Was originally thinking to put the note in the HTTPS Setup page itself, but since there are 2 sections referencing the PROTOCOL config, I was thinking it'd be neater and more concise to put it in the Config Cheat Sheet page instead. Especially since both sections already link to it, and I actually tried to check that link quite early on in my troubleshooting (but didn't pay much attention to it since the link was broken). ## Before/After screenshots as per [this repo's docs](https://github.com/go-gitea/gitea/tree/main/docs) Before - links ![image](https://github.com/go-gitea/gitea/assets/135522693/e0745077-f6a9-4178-aa78-2155ccb58fd6) Note: For this the links weren't broken, the links fix is because they were broken on gitea.com's docs (see below). After - links ![image](https://github.com/go-gitea/gitea/assets/135522693/748b3759-aa13-4ad0-9811-c6664b6cdd35) Before - config cheat sheet ![image](https://github.com/go-gitea/gitea/assets/135522693/4ff2e4e6-3528-4cea-a7a6-64a75854eb99) After - config cheat sheet ![image](https://github.com/go-gitea/gitea/assets/135522693/c8e07ab6-5a26-4582-a4d0-b83d1f11a30e) ## Before/After screenshots as per [gitea.com's docs](https://gitea.com/gitea/gitea-docusaurus) Before - links ![image](https://github.com/go-gitea/gitea/assets/135522693/4d26ea67-b987-4b91-810b-c53852a13078) After - links ![image](https://github.com/go-gitea/gitea/assets/135522693/24d02907-7f9e-4228-a190-7696623c00f7) Before - config cheat sheet ![image](https://github.com/go-gitea/gitea/assets/135522693/978eedfd-ce05-488d-ab54-9d7f3c9f233d) After - config cheat sheet ![image](https://github.com/go-gitea/gitea/assets/135522693/12d22566-a2b0-45ec-8302-a88eae9365d8)
* Typos fixed in documentation files (#27687)SandeshPyakurel2023-10-192-4/+4
| | | Typos fixed in multiple docs files.
* Update agit-support.en-us.md (#27652)Sandro Santilli2023-10-171-6/+9
| | | | | Clarify Agit PR creation documentation See https://github.com/go-gitea/gitea/issues/27579
* Change the default branch in the agit docs (#27621)Nanguan Lin2023-10-142-6/+6
|
* Enhanced auth token / remember me (#27606)KN4CK3R2023-10-142-2/+0
| | | | | | | | | | | | | | | | | Closes #27455 > The mechanism responsible for long-term authentication (the 'remember me' cookie) uses a weak construction technique. It will hash the user's hashed password and the rands value; it will then call the secure cookie code, which will encrypt the user's name with the computed hash. If one were able to dump the database, they could extract those two values to rebuild that cookie and impersonate a user. That vulnerability exists from the date the dump was obtained until a user changed their password. > > To fix this security issue, the cookie could be created and verified using a different technique such as the one explained at https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#secure-remember-me-cookies. The PR removes the now obsolete setting `COOKIE_USERNAME`.
* rm outdated docs from some languages (#27530)techknowlogick2023-10-1347-2068/+0
| | | related to #27499
* Fix the robots.txt pathLunny Xiao2023-10-112-2/+2
|
* Make actions default enabled for newly created repository if global ↵Lunny Xiao2023-10-102-2/+2
| | | | configuraion enabled (#27482)
* Fix the wrong HTTP response status code for duplicate packages (#27480)Nanguan Lin2023-10-109-3/+49
| | | | | | | | fix #27470 (hope there is nothing missing 😢 ) --------- Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Increase queue length (#27555)Jason Song2023-10-102-2/+2
|
* Improve docs about register/run as a service (#27461)Nanguan Lin2023-10-092-13/+14
| | | As title
* Add docs section for sub-paths with the container registry (#27505)KN4CK3R2023-10-091-0/+6
| | | | | | | | | | Fixes #21092 suggested by https://github.com/go-gitea/gitea/issues/21092#issuecomment-1749965397 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
* Pre-register OAuth application for tea (#27509)M Hickford2023-10-083-2/+3
| | | | | | It remains to implement OAuth login in tea https://gitea.com/gitea/tea/issues/598 Fixes #27510
* Enable markdownlint `no-duplicate-header` (#27500)silverwind2023-10-074-9/+9
| | | | | | | | | | | | | | | | | 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
* Rename the default themes to gitea-light, gitea-dark, gitea-auto (#27419)silverwind2023-10-066-10/+12
| | | | | | | | | | | | | | | | | | | | | | | | | Part of https://github.com/go-gitea/gitea/issues/27097: - `gitea` theme is renamed to `gitea-light` - `arc-green` theme is renamed to `gitea-dark` - `auto` theme is renamed to `gitea-auto` I put both themes in separate CSS files, removing all colors from the base CSS. Existing users will be migrated to the new theme names. The dark theme recolor will follow in a separate PR. ## :warning: BREAKING :warning: 1. If there are existing custom themes with the names `gitea-light` or `gitea-dark`, rename them before this upgrade and update the `theme` column in the `user` table for each affected user. 2. The theme in `<html>` has moved from `class="theme-name"` to `data-theme="name"`, existing customizations that depend on should be updated. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>
* Rephrase template documentation to be more clear about .gitea/template (#27450)Andrew Imeson2023-10-061-5/+8
| | | | | | | Closes #27336 --------- Co-authored-by: silverwind <me@silverwind.io>
* Fix `Installation from package` doc (#27459)Nanguan Lin2023-10-051-12/+15
| | | | Fix the title size and add notes to the Gitea snap package. Related issue #27424, #27423, #27422, #27420
* Require MySQL 8.0, PostgreSQL 12, MSSQL 2012 (#27337)silverwind2023-10-032-2/+4
| | | | | | | | | | | | | | | | | | | | | | | - MySQL 5.7 support and testing is dropped - MySQL tests now execute against 8.1, up from 5.7 and 8.0 - PostgreSQL 10 and 11 support ist dropped - PostgreSQL tests now execute against 16, up from 15 - MSSQL 2008 support is dropped - MSSQL tests now run against locked 2022 version Fixes: https://github.com/go-gitea/gitea/issues/25657 Ref: https://endoflife.date/mysql Ref: https://endoflife.date/postgresql Ref: https://endoflife.date/mssqlserver ## :warning: BREAKING :warning: Support for MySQL 5.7, PostgreSQL 10 and 11, and MSSQL 2008 is dropped. You are encouraged to upgrade to supported versions. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.com>
* Make Actions tasks/jobs timeouts configurable by the user (#27400)Francesco Antognazza2023-10-021-0/+3
| | | | | | | | | | | | | | | | | | | 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>
* Remove upgrade from Gogs doc because the diverse has been 7 years and the ↵Lunny Xiao2023-10-024-405/+0
| | | | | code base changed totally (#27387) The documentation becomes no help since that but make people confusing.
* Fix incorrect Chinese translation of linked-references.zh-cn.md (#27382)Ayaka2023-10-021-1/+1
| | | | | | --- The original text "To address this" should be translated to "为了解决这个问题". "工单" looks like corresponds to "issue".
* 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-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
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-24 05:40:13 +0000