You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* upstream/main:
Fix typo in act-runner file (go-gitea#24652)
RSS icon fixes (go-gitea#24476)
Notification list enhancements, fix striped tables on dark theme (go-gitea#24639)
Improve "goto issue by number" button (go-gitea#24577)
Increase default LFS auth timeout from 20m to 24h (go-gitea#24628)
Fix typo in the swift package documentation (go-gitea#24637)
Fix broken links in documents (go-gitea#24630)
Improve updating Actions tasks (go-gitea#24600)
Modify luminance calculation and extract related functions into single files (go-gitea#24586)
Do not send "registration success email" for external auth sources (go-gitea#24632)
Fix typo in Actions demo file (go-gitea#24631)
Review fixes and enhancements (go-gitea#24526)
Remove fluid on compare diff page (go-gitea#24627)
Make the actions control button look like an actual button (go-gitea#24611)
Add a tooltip to the job rerun button (go-gitea#24617)
Improve reverse-proxy document and fix nginx config bug (go-gitea#24616)
Copy file name to clipboardexpand all lines: docs/content/doc/actions/comparison.en-us.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ The missing host will be filled with `https://gitea.com` if you don't configure
132
132
That means `uses: actions/checkout@v3` will download the action from [gitea.com/actions/checkout](https://gitea.com/actions/checkout), instead of [github.com/actions/checkout](https://github.com/actions/checkout).
133
133
134
134
As mentioned, it's configurable.
135
-
If you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. See [Configuration Cheat Sheet](({{ < relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" > }})).
135
+
If you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. See [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" >}}).
Copy file name to clipboardexpand all lines: docs/content/doc/actions/quickstart.en-us.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This page will guide you through the process of using Gitea Actions.
24
24
## Set up Gitea
25
25
26
26
First of all, you need a Gitea instance.
27
-
You can follow the [documentation]({{< relref "doc/installation/from-package.en-us.md" >}}) to set up a new instance or upgrade your existing one.
27
+
You can follow the [documentation]({{< relref "doc/installation/from-package.en-us.md" >}}) to set up a new instance or upgrade your existing one.
28
28
It doesn't matter how you install or run Gitea, as long as its version is 1.19.0 or higher.
29
29
30
30
Actions are disabled by default, so you need to add the following to the configuration file to enable it:
@@ -34,7 +34,7 @@ Actions are disabled by default, so you need to add the following to the configu
34
34
ENABLED=true
35
35
```
36
36
37
-
If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" >}}).
37
+
If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" >}}).
38
38
39
39
### Set up runner
40
40
@@ -85,7 +85,7 @@ And you can see the new runner in the management page:
You can find more information by visiting [Act runner]({{< relref "doc/actions/act-runner.en-us.md" >}}).
88
+
You can find more information by visiting [Act runner]({{< relref "doc/actions/act-runner.en-us.md" >}}).
89
89
90
90
### Use Actions
91
91
@@ -119,7 +119,7 @@ jobs:
119
119
- name: List files in the repository
120
120
run: |
121
121
ls ${{ gitea.workspace }}
122
-
- run: echo "🍏 This job's status is ${{ gitea.status }}."
122
+
- run: echo "🍏 This job's status is ${{ job.status }}."
123
123
```
124
124
125
125
You can upload it as a file with the extension `.yaml` in the directory `.gitea/workflows/` of the repository, for example `.gitea/workflows/demo.yaml`.
@@ -129,7 +129,7 @@ That is because Gitea Actions is designed to be compatible with GitHub Actions
129
129
Be careful, the demo file contains some emojis.
130
130
Please make sure your database supports them, especially when using MySQL.
131
131
If the charset is not `utf8mb4`, errors will occur, such as `Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`.
132
-
See [Database Preparation]( {{ < relref "doc/installation/database-preparation.en-us.md#mysql" >}}) for more information.
132
+
See [Database Preparation]({{< relref "doc/installation/database-preparation.en-us.md#mysql" >}}) for more information.
133
133
134
134
Alternatively, you can remove all emojis from the demo file and try again.
Copy file name to clipboardexpand all lines: docs/content/doc/administration/reverse-proxies.en-us.md
+29-17
Original file line number
Diff line number
Diff line change
@@ -25,12 +25,13 @@ menu:
25
25
26
26
If you want Nginx to serve your Gitea instance, add the following `server` section to the `http` section of `nginx.conf`:
27
27
28
-
```apacheconf
28
+
```
29
29
server {
30
30
listen 80;
31
31
server_name git.example.com;
32
32
33
33
location / {
34
+
client_max_body_size 512M;
34
35
proxy_pass http://localhost:3000;
35
36
proxy_set_header Host $host;
36
37
proxy_set_header X-Real-IP $remote_addr;
@@ -40,23 +41,32 @@ server {
40
41
}
41
42
```
42
43
44
+
### Resolving Error: 413 Request Entity Too Large
45
+
46
+
This error indicates nginx is configured to restrict the file upload size,
47
+
it affects attachment uploading, form posting, package uploading and LFS pushing, etc.
48
+
You can fine tune the `client_max_body_size` option according to [nginx document](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size).
49
+
43
50
## Nginx with a sub-path
44
51
45
52
In case you already have a site, and you want Gitea to share the domain name, you can setup Nginx to serve Gitea under a sub-path by adding the following `server` section inside the `http` section of `nginx.conf`:
# other common HTTP headers, see the "Nginx" config section above
69
+
proxy_set_header ...
60
70
}
61
71
}
62
72
```
@@ -132,14 +142,6 @@ server {
132
142
}
133
143
```
134
144
135
-
## Resolving Error: 413 Request Entity Too Large
136
-
137
-
This error indicates nginx is configured to restrict the file upload size.
138
-
139
-
In your nginx config file containing your Gitea proxy directive, find the `location { ... }` block for Gitea and add the line
140
-
`client_max_body_size 16M;` to set this limit to 16 megabytes or any other number of choice.
141
-
If you use Git LFS, this will also limit the size of the largest file you will be able to push.
142
-
143
145
## Apache HTTPD
144
146
145
147
If you want Apache HTTPD to serve your Gitea instance, you can add the following to your Apache HTTPD configuration (usually located at `/etc/apache2/httpd.conf` in Ubuntu):
@@ -387,3 +389,13 @@ gitea:
387
389
This config assumes that you are handling HTTPS on the traefik side and using HTTP between Gitea and traefik.
388
390
389
391
Then you **MUST** set something like `[server] ROOT_URL = http://example.com/gitea/` correctly in your configuration.
392
+
393
+
## General sub-path configuration
394
+
395
+
Usually it's not recommended to put Gitea in a sub-path, it's not widely used and may have some issues in rare cases.
396
+
397
+
If you really need to do so, to make Gitea works with sub-path (eg: `http://example.com/gitea/`), here are the requirements:
398
+
399
+
1. Set `[server] ROOT_URL = http://example.com/gitea/` in your `app.ini` file.
400
+
2. Make the reverse-proxy pass `http://example.com/gitea/foo` to `http://gitea-server:3000/foo`.
401
+
3. Make sure the reverse-proxy not decode the URI, the request `http://example.com/gitea/a%2Fb` should be passed as `http://gitea-server:3000/a%2Fb`.
Copy file name to clipboardexpand all lines: docs/content/doc/usage/push.zh-tw.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Push to create is a feature that allows you to push to a repository that does no
54
54
55
55
## Enabling Push To Create
56
56
57
-
In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.zh-tw.md#repository-repository" >}}).
57
+
In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.zh-tw.md#repository-repository" >}}).
0 commit comments