aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content
Commit message (Collapse)AuthorAgeFilesLines
* switch destination directory for apt signing keys (#28639)Denys Konovalov2023-12-282-6/+6
| | | | | | | | | | | | | | | According to [Debian docs](https://wiki.debian.org/DebianRepository/UseThirdParty): > The certificate MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded by apt-key add. > ... > If future updates to the certificate will be managed by an apt/dpkg package as recommended below, then it SHOULD be downloaded into /usr/share/keyrings using the same filename that will be provided by the package. If it will be managed locally , it SHOULD be downloaded into /etc/apt/keyrings instead. > ... > A sources.list entry SHOULD have the signed-by option set.
* Extend description for ARTIFACT_RETENTION_DAYS (#28626)Gerd Katzenbeisser2023-12-281-1/+1
| | | | Make it clear that this value is just a default value and that every artifact can have it's own value.
* Update repo-mirror.en-us.md (#28612)Volodymyr Stelmashchuk2023-12-271-1/+1
| | | | | Add small changes to the doc. The workflow scope require for push code to github mirror in case the project use the github action compatibility ui.
* Refactor CORS handler (#28587)wxiaoguang2023-12-252-5/+1
| | | | | | | | | | | The CORS code has been unmaintained for long time, and the behavior is not correct. This PR tries to improve it. The key point is written as comment in code. And add more tests. Fix #28515 Fix #27642 Fix #17098
* Make offline mode as default to no connect external avatar service by ↵Lunny Xiao2023-12-212-2/+2
| | | | | | | default (#28548) To keep user's privacy, make offline mode as true by default. Users can still change it from installation ui and app.ini
* feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 ↵Rui Chen2023-12-2112-27/+27
| | | | | | | | | | | | | | runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
* Update actions document about comparsion as Github Actions (#28560)Lunny Xiao2023-12-202-0/+16
|
* Always enable caches (#28527)Lunny Xiao2023-12-192-4/+0
| | | | | | | | | Nowadays, cache will be used on almost everywhere of Gitea and it cannot be disabled, otherwise some features will become unaviable. Then I think we can just remove the option for cache enable. That means cache cannot be disabled. But of course, we can still use cache configuration to set how should Gitea use the cache.
* Add option to disable ambiguous unicode characters detection (#28454)wxiaoguang2023-12-171-0/+1
| | | | | | | | * Close #24483 * Close #28123 * Close #23682 * Close #23149 (maybe more)
* Update docs for DISABLE_QUERY_AUTH_TOKEN (#28485)Kyle D2023-12-151-0/+1
| | | | As described [here](https://github.com/go-gitea/gitea/pull/28390#issuecomment-1857553331).
* Improve CLI code and descriptions (#28482)wxiaoguang2023-12-152-6/+5
| | | | | | | | | | * Close #28444 * Actually, it doesn't need to use that trick because it looks like it is not necessary, no user really needs it * Remove the hidden (legacy) "doctor" subcommand and update documents * Fix "actions" usage ![image](https://github.com/go-gitea/gitea/assets/2114189/3c2b34a7-4f92-4a6c-96fd-9505e413d4ec)
* Fix Chinese translation of config cheat sheet[API] (#28472)CaiCandong2023-12-151-4/+5
|
* Fix documents for "custom/public/assets/" (#28465)wxiaoguang2023-12-145-8/+8
| | | Fix #28463
* docs: Update group membership fields to match application. (#28175)David Hulick2023-12-131-9/+9
| | | | | | | | Several fields in the "Verify group membership in LDAP" docs were confusingly titled when compared to the actual fields in the application, this change rectifies that by matching the docs to the fields already present in gitea. Signed-off-by: David Hulick <dave.hulick@gmail.com>
* Fix links in docs (#28302)yp053272023-12-015-10/+6
| | | | | | | | | 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 ```
* Fix links in docs (#28234)yp053272023-11-273-3/+3
| | | | | | | | | 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 `../../`
* Docs: Replace deprecated IS_TLS_ENABLED mailer setting in email setup (#28205)CodeShakingSheep2023-11-252-2/+2
| | | | | | | | | 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.
* Fix some incorrect links in docs (#28191)yp053272023-11-247-7/+5
| | | | | | | | | 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. ps: Are there any good methods to test this in local?
* Fix the description about the default setting for action in quick start ↵yp053272023-11-222-2/+2
| | | | | | | | document (#28160) 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.
* Update docs for docusaurus v3 (#28125)John Olheiser2023-11-205-10/+10
| | | | | Updates the docs for usage with docusaurus v3 Signed-off-by: jolheiser <john.olheiser@gmail.com>
* add skip ci functionality (#28075)Denys Konovalov2023-11-181-0/+1
| | | | | | | | | | | | Adds the possibility to skip workflow execution if the commit message contains a string like [skip ci] or similar. The default strings are the same as on GitHub, users can also set custom ones in app.ini Reference: https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs Close #28020
* Change default size of issue/pr attachments and repo file (#27946)Nanguan Lin2023-11-132-4/+4
| | | | As title. Some attachments and file sizes can easily be larger than these limits
* Add Profile Readme for Organisations (#27955)65432023-11-091-1/+2
| | | | | | | | | | | | | | | | | https://blog.gitea.com/release-of-1.20.0/#-user-profile-readme-23260 (#23260) did introduce Profile Readme for Users. This makes it usable for Organisations: ![image](https://github.com/go-gitea/gitea/assets/24977596/464ab58b-a952-414b-8a34-6deaeb4f7d35) --- *Sponsored by Kithara Software GmbH* --------- Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
* Allow to set explore page default sort (#27951)65432023-11-091-1/+2
| | | | | | | as title --- *Sponsored by Kithara Software GmbH*
* Document REACTION_MAX_USER_NUM setting option (#27954)65432023-11-081-0/+1
| | | | | | | | https://github.com/go-gitea/gitea/blob/4a0103fa293cc42075d4a9c10ca4dffa9c2d3a40/modules/setting/ui.go#L24 https://github.com/go-gitea/gitea/blob/4a0103fa293cc42075d4a9c10ca4dffa9c2d3a40/modules/setting/ui.go#L77 --- *Sponsored by Kithara Software GmbH*
* Remove `known issue` section in Gitea Actions Doc (#27930)Nanguan Lin2023-11-062-62/+0
| | | | | | | 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.
* 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>
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-11 20:10:34 +0000