loading up the forgejo repo on tangled to test page performance
Docusaurus-ify (#26051)
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>
authored by
John Olheiser
and committed by
GitHub
bd4c7ce5
5dc37ef9
+1147
-2510
+1
-1
.github/workflows/pull-compliance.yml
+1
-1
.github/workflows/pull-compliance.yml
+6
-13
Makefile
+6
-13
Makefile
···
197
197
@echo " - clean delete backend and integration files"
198
198
@echo " - clean-all delete backend, frontend and integration files"
199
199
@echo " - deps install dependencies"
200
-
@echo " - deps-docs install docs dependencies"
201
200
@echo " - deps-frontend install frontend dependencies"
202
201
@echo " - deps-backend install backend dependencies"
203
202
@echo " - deps-tools install tool dependencies"
···
373
372
374
373
.PHONY: lint-js
375
374
lint-js: node_modules
376
-
npx eslint --color --max-warnings=0 --ext js,vue web_src/js build *.config.js docs/assets/js tests/e2e
375
+
npx eslint --color --max-warnings=0 --ext js,vue web_src/js build *.config.js tests/e2e
377
376
378
377
.PHONY: lint-js-fix
379
378
lint-js-fix: node_modules
380
-
npx eslint --color --max-warnings=0 --ext js,vue web_src/js build *.config.js docs/assets/js tests/e2e --fix
379
+
npx eslint --color --max-warnings=0 --ext js,vue web_src/js build *.config.js tests/e2e --fix
381
380
382
381
.PHONY: lint-css
383
382
lint-css: node_modules
···
879
878
880
879
.PHONY: release-docs
881
880
release-docs: | $(DIST_DIRS) docs
882
-
tar -czf $(DIST)/release/gitea-docs-$(VERSION).tar.gz -C ./docs/public .
881
+
tar -czf $(DIST)/release/gitea-docs-$(VERSION).tar.gz -C ./docs .
883
882
884
883
.PHONY: docs
885
-
docs: deps-docs
886
-
cd docs; make trans-copy clean build-offline;
887
-
888
-
.PHONY: deps-docs
889
-
deps-docs:
890
-
@hash hugo > /dev/null 2>&1; if [ $$? -ne 0 ]; then \
891
-
curl -sL https://github.com/gohugoio/hugo/releases/download/v$(HUGO_VERSION)/hugo_$(HUGO_VERSION)_Linux-64bit.tar.gz | tar zxf - -C /tmp && mkdir -p ~/go/bin && mv /tmp/hugo ~/go/bin/hugo && chmod +x ~/go/bin/hugo; \
892
-
fi
884
+
docs:
885
+
cd docs; bash scripts/trans-copy.sh;
893
886
894
887
.PHONY: deps
895
-
deps: deps-frontend deps-backend deps-tools deps-docs deps-py
888
+
deps: deps-frontend deps-backend deps-tools deps-py
896
889
897
890
.PHONY: deps-py
898
891
deps-py: .venv
-36
docs/Makefile
-36
docs/Makefile
···
1
-
THEME := themes/gitea
2
-
PUBLIC := public
3
-
ARCHIVE := https://dl.gitea.com/theme/main.tar.gz
4
-
5
-
HUGO_PACKAGE := github.com/gohugoio/hugo@v0.111.3
6
-
7
-
.PHONY: all
8
-
all: build
9
-
10
-
.PHONY: clean
11
-
clean:
12
-
rm -rf $(PUBLIC) $(THEME)
13
-
14
-
.PHONY: trans-copy
15
-
trans-copy:
16
-
bash scripts/trans-copy.sh
17
-
18
-
.PHONY: server
19
-
server: $(THEME)
20
-
go run $(HUGO_PACKAGE) server
21
-
22
-
.PHONY: build
23
-
build: $(THEME)
24
-
go run $(HUGO_PACKAGE) --cleanDestinationDir
25
-
26
-
.PHONY: build-offline
27
-
build-offline: $(THEME)
28
-
go run $(HUGO_PACKAGE) --baseURL="/" --cleanDestinationDir
29
-
30
-
.PHONY: update
31
-
update: $(THEME)
32
-
33
-
$(THEME): $(THEME)/theme.toml
34
-
$(THEME)/theme.toml:
35
-
mkdir -p $$(dirname $@)
36
-
curl -L -s $(ARCHIVE) | tar xz -C $$(dirname $@)
+1
-30
docs/README.md
+1
-30
docs/README.md
···
3
3
[](https://discord.gg/Gitea)
4
4
[](http://microbadger.com/images/gitea/docs "Get your own image badge on microbadger.com")
5
5
6
-
## Hosting
7
-
8
-
These pages are hosted using [netlifycms](https://www.netlifycms.org/) and get
9
-
automatically updated on every push to the `master` branch.
10
-
11
-
## Install
12
-
13
-
These pages use the [Hugo](https://gohugo.io/) static site generator.
14
-
If you are planning to contribute you'll want to download and install Hugo on
15
-
your local machine.
16
-
17
-
The installation of Hugo is out of the scope of this document, so please take
18
-
the [official install instructions](https://gohugo.io/installation/) to
19
-
get Hugo up and running.
20
-
21
-
## Development
22
-
23
-
To generate the website and serve it on [localhost:1313](http://localhost:1313)
24
-
just execute this command and stop it with `Ctrl+C`:
25
-
26
-
```
27
-
make server
28
-
```
29
-
30
-
When you are done with your changes just create a pull request, after merging
31
-
the pull request the website will be updated automatically.
32
-
33
-
## Contributing
34
-
35
-
Fork -> Patch -> Push -> Pull Request
6
+
These docs are ingested by our [docs repo](https://gitea.com/gitea/gitea-docusaurus).
36
7
37
8
## Authors
38
9
+1
-21
docs/README_ZH.md
+1
-21
docs/README_ZH.md
···
4
4
[](https://discord.gg/Gitea)
5
5
[](http://microbadger.com/images/gitea/docs "Get your own image badge on microbadger.com")
6
6
7
-
## 关于托管方式
8
-
9
-
本页面托管在我们 Docker 容器内的基础设施上， 它会在每次推送到 `master` 分支的时候自动更新，如果你想自己管理这个页面，你可以从我们的 Docker 镜像 [gitea/docs](https://hub.docker.com/r/gitea/docs/) 中获取它。
10
-
11
-
## 安装 Hugo
12
-
13
-
本页面使用了 [Hugo](https://github.com/spf13/hugo) 静态页面生成工具，如果您有维护它的意愿，则需要在本地计算机上下载并安装 Hugo。Hugo 的安装教程不在本文档的讲述范围之内，详情请参见 [官方文档](https://gohugo.io/overview/installing/)。
14
-
15
-
## 如何部署
16
-
17
-
在 [localhost:1313](http://localhost:1313) 处构建和运行网站的命令如下，如果需要停止可以使用组合键 `Ctrl+C`:
18
-
19
-
```
20
-
make server
21
-
```
22
-
23
-
完成更改后，只需创建一个 Pull Request (PR)，该 PR 一经合并网站将自动更新。
24
-
25
-
## 如何贡献您的代码
26
-
27
-
Fork -> Patch -> Push -> Pull Request
7
+
https://gitea.com/gitea/gitea-docusaurus
28
8
29
9
## 关于我们
30
10
-174
docs/assets/js/search.js
-174
docs/assets/js/search.js
···
1
-
/* global Fuse, Mark */
2
-
3
-
function ready(fn) {
4
-
if (document.readyState !== 'loading') {
5
-
fn();
6
-
} else {
7
-
document.addEventListener('DOMContentLoaded', fn);
8
-
}
9
-
}
10
-
11
-
ready(doSearch);
12
-
13
-
const summaryInclude = 60;
14
-
const fuseOptions = {
15
-
shouldSort: true,
16
-
includeMatches: true,
17
-
matchAllTokens: true,
18
-
threshold: 0, // for parsing diacritics
19
-
tokenize: true,
20
-
location: 0,
21
-
distance: 100,
22
-
maxPatternLength: 32,
23
-
minMatchCharLength: 1,
24
-
keys: [{
25
-
name: 'title',
26
-
weight: 0.8
27
-
},
28
-
{
29
-
name: 'contents',
30
-
weight: 0.5
31
-
},
32
-
{
33
-
name: 'tags',
34
-
weight: 0.3
35
-
},
36
-
{
37
-
name: 'categories',
38
-
weight: 0.3
39
-
}
40
-
]
41
-
};
42
-
43
-
function param(name) {
44
-
return decodeURIComponent((window.location.search.split(`${name}=`)[1] || '').split('&')[0]).replace(/\+/g, ' ');
45
-
}
46
-
47
-
const searchQuery = param('s');
48
-
49
-
function doSearch() {
50
-
if (searchQuery) {
51
-
document.getElementById('search-query').value = searchQuery;
52
-
executeSearch(searchQuery);
53
-
} else {
54
-
const para = document.createElement('P');
55
-
para.textContent = 'Please enter a word or phrase above';
56
-
document.getElementById('search-results').append(para);
57
-
}
58
-
}
59
-
60
-
function getJSON(url, fn) {
61
-
const request = new XMLHttpRequest();
62
-
request.open('GET', url, true);
63
-
request.addEventListener('load', () => {
64
-
if (request.status >= 200 && request.status < 400) {
65
-
const data = JSON.parse(request.responseText);
66
-
fn(data);
67
-
} else {
68
-
console.error(`Target reached on ${url} with error ${request.status}`);
69
-
}
70
-
});
71
-
request.addEventListener('error', () => {
72
-
console.error(`Connection error ${request.status}`);
73
-
});
74
-
request.send();
75
-
}
76
-
77
-
function executeSearch(searchQuery) {
78
-
getJSON(`/${document.LANG}/index.json`, (data) => {
79
-
const pages = data;
80
-
const fuse = new Fuse(pages, fuseOptions);
81
-
const result = fuse.search(searchQuery);
82
-
document.getElementById('search-results').innerHTML = '';
83
-
if (result.length > 0) {
84
-
populateResults(result);
85
-
} else {
86
-
const para = document.createElement('P');
87
-
para.textContent = 'No matches found';
88
-
document.getElementById('search-results').append(para);
89
-
}
90
-
});
91
-
}
92
-
93
-
function populateResults(result) {
94
-
for (const [key, value] of result.entries()) {
95
-
const content = value.item.contents;
96
-
let snippet = '';
97
-
const snippetHighlights = [];
98
-
if (fuseOptions.tokenize) {
99
-
snippetHighlights.push(searchQuery);
100
-
for (const mvalue of value.matches) {
101
-
if (mvalue.key === 'tags' || mvalue.key === 'categories') {
102
-
snippetHighlights.push(mvalue.value);
103
-
} else if (mvalue.key === 'contents') {
104
-
const ind = content.toLowerCase().indexOf(searchQuery.toLowerCase());
105
-
const start = ind - summaryInclude > 0 ? ind - summaryInclude : 0;
106
-
const end = ind + searchQuery.length + summaryInclude < content.length ? ind + searchQuery.length + summaryInclude : content.length;
107
-
snippet += content.substring(start, end);
108
-
if (ind > -1) {
109
-
snippetHighlights.push(content.substring(ind, ind + searchQuery.length));
110
-
} else {
111
-
snippetHighlights.push(mvalue.value.substring(mvalue.indices[0][0], mvalue.indices[0][1] - mvalue.indices[0][0] + 1));
112
-
}
113
-
}
114
-
}
115
-
}
116
-
117
-
if (snippet.length < 1) {
118
-
snippet += content.substring(0, summaryInclude * 2);
119
-
}
120
-
// pull template from hugo template definition
121
-
const templateDefinition = document.getElementById('search-result-template').innerHTML;
122
-
// replace values
123
-
const output = render(templateDefinition, {
124
-
key,
125
-
title: value.item.title,
126
-
link: value.item.permalink,
127
-
tags: value.item.tags,
128
-
categories: value.item.categories,
129
-
snippet
130
-
});
131
-
document.getElementById('search-results').append(htmlToElement(output));
132
-
133
-
for (const snipvalue of snippetHighlights) {
134
-
new Mark(document.getElementById(`summary-${key}`)).mark(snipvalue);
135
-
}
136
-
}
137
-
}
138
-
139
-
function render(templateString, data) {
140
-
let conditionalMatches, copy;
141
-
const conditionalPattern = /\$\{\s*isset ([a-zA-Z]*) \s*\}(.*)\$\{\s*end\s*\}/g;
142
-
// since loop below depends on re.lastIndex, we use a copy to capture any manipulations whilst inside the loop
143
-
copy = templateString;
144
-
while ((conditionalMatches = conditionalPattern.exec(templateString)) !== null) {
145
-
if (data[conditionalMatches[1]]) {
146
-
// valid key, remove conditionals, leave content.
147
-
copy = copy.replace(conditionalMatches[0], conditionalMatches[2]);
148
-
} else {
149
-
// not valid, remove entire section
150
-
copy = copy.replace(conditionalMatches[0], '');
151
-
}
152
-
}
153
-
templateString = copy;
154
-
// now any conditionals removed we can do simple substitution
155
-
let key, find, re;
156
-
for (key of Object.keys(data)) {
157
-
find = `\\$\\{\\s*${key}\\s*\\}`;
158
-
re = new RegExp(find, 'g');
159
-
templateString = templateString.replace(re, data[key]);
160
-
}
161
-
return templateString;
162
-
}
163
-
164
-
/**
165
-
* By Mark Amery: https://stackoverflow.com/a/35385518
166
-
* @param {String} HTML representing a single element
167
-
* @return {Element}
168
-
*/
169
-
function htmlToElement(html) {
170
-
const template = document.createElement('template');
171
-
html = html.trim(); // Never return a text node of whitespace as the result
172
-
template.innerHTML = html;
173
-
return template.content.firstChild;
174
-
}
-369
docs/config.yaml
-369
docs/config.yaml
···
1
-
baseurl: https://docs.gitea.io/
2
-
languageCode: en-us
3
-
title: Docs
4
-
theme: gitea
5
-
6
-
defaultContentLanguage: en-us
7
-
defaultContentLanguageInSubdir: true
8
-
enableMissingTranslationPlaceholders: true
9
-
enableEmoji: true
10
-
11
-
permalinks:
12
-
post: /:year/:month/:title/
13
-
doc: /:sections[1:]/:slug/
14
-
page: /:slug/
15
-
default: /:slug/
16
-
17
-
params:
18
-
description: Git with a cup of tea
19
-
author: The Gitea Authors
20
-
website: https://docs.gitea.io
21
-
version: 1.19.0 # FIXME: this version was used as "latest stable release", but it always gets outdated and doesn't make sense
22
-
minGoVersion: 1.20
23
-
goVersion: 1.20
24
-
minNodeVersion: 16
25
-
search: nav
26
-
repo: "https://github.com/go-gitea/gitea"
27
-
docContentPath: "docs/content"
28
-
29
-
markup:
30
-
tableOfContents:
31
-
startLevel: 1
32
-
endLevel: 9
33
-
34
-
outputs:
35
-
home:
36
-
- HTML
37
-
- RSS
38
-
- JSON
39
-
40
-
menu:
41
-
page:
42
-
- name: Website
43
-
url: https://gitea.io/en-us/
44
-
weight: 10
45
-
pre: home
46
-
- name: Docs
47
-
url: /en-us/
48
-
weight: 20
49
-
pre: question
50
-
post: active
51
-
- name: API
52
-
url: https://try.gitea.io/api/swagger
53
-
weight: 45
54
-
pre: plug
55
-
- name: Blog
56
-
url: https://blog.gitea.io/
57
-
weight: 30
58
-
pre: rss
59
-
- name: Shop
60
-
url: https://shop.gitea.io/
61
-
weight: 40
62
-
pre: shopping-cart
63
-
- name: Translation
64
-
url: https://crowdin.com/project/gitea
65
-
weight: 41
66
-
pre: language
67
-
- name: Downloads
68
-
url: https://dl.gitea.io/
69
-
weight: 50
70
-
pre: download
71
-
- name: GitHub
72
-
url: https://github.com/go-gitea/
73
-
weight: 60
74
-
pre: github
75
-
- name: Discord Chat
76
-
url: https://discord.gg/Gitea
77
-
weight: 70
78
-
pre: comment
79
-
- name: Forum
80
-
url: https://discourse.gitea.io/
81
-
weight: 80
82
-
pre: group
83
-
84
-
languages:
85
-
en-us:
86
-
weight: 0
87
-
languageName: English
88
-
89
-
zh-cn:
90
-
weight: 1
91
-
languageName: 中文(简体)
92
-
menu:
93
-
page:
94
-
- name: 网站
95
-
url: https://gitea.io/zh-cn/
96
-
weight: 10
97
-
pre: home
98
-
- name: 文档
99
-
url: /zh-cn/
100
-
weight: 20
101
-
pre: question
102
-
post: active
103
-
- name: API
104
-
url: https://try.gitea.io/api/swagger
105
-
weight: 45
106
-
pre: plug
107
-
- name: 博客
108
-
url: https://blog.gitea.io/
109
-
weight: 30
110
-
pre: rss
111
-
- name: 导入
112
-
url: https://code.gitea.io/
113
-
weight: 40
114
-
pre: code
115
-
- name: 翻译
116
-
url: https://crowdin.com/project/gitea
117
-
weight: 41
118
-
pre: language
119
-
- name: 下载
120
-
url: https://dl.gitea.io/
121
-
weight: 50
122
-
pre: download
123
-
- name: GitHub
124
-
url: https://github.com/go-gitea/
125
-
weight: 60
126
-
pre: github
127
-
- name: Discord Chat
128
-
url: https://discord.gg/Gitea
129
-
weight: 70
130
-
pre: comment
131
-
- name: Forum
132
-
url: https://discourse.gitea.io/
133
-
weight: 80
134
-
pre: group
135
-
136
-
zh-tw:
137
-
weight: 2
138
-
languageName: 中文(繁體)
139
-
menu:
140
-
page:
141
-
- name: 網站
142
-
url: https://gitea.io/zh-tw/
143
-
weight: 10
144
-
pre: home
145
-
- name: 文件
146
-
url: /zh-tw/
147
-
weight: 20
148
-
pre: question
149
-
post: active
150
-
- name: API
151
-
url: https://try.gitea.io/api/swagger
152
-
weight: 45
153
-
pre: plug
154
-
- name: 部落格
155
-
url: https://blog.gitea.io/
156
-
weight: 30
157
-
pre: rss
158
-
- name: 商店
159
-
url: https://shop.gitea.io/
160
-
weight: 40
161
-
pre: shopping-cart
162
-
- name: 翻譯
163
-
url: https://crowdin.com/project/gitea
164
-
weight: 41
165
-
pre: language
166
-
- name: 下載
167
-
url: https://dl.gitea.io/
168
-
weight: 50
169
-
pre: download
170
-
- name: GitHub
171
-
url: https://github.com/go-gitea/
172
-
weight: 60
173
-
pre: github
174
-
- name: Discord 聊天室
175
-
url: https://discord.gg/Gitea
176
-
weight: 70
177
-
pre: comment
178
-
- name: 討論區
179
-
url: https://discourse.gitea.io/
180
-
weight: 80
181
-
pre: group
182
-
183
-
pt-br:
184
-
weight: 3
185
-
languageName: Português Brasileiro
186
-
menu:
187
-
page:
188
-
- name: Página inicial
189
-
url: https://gitea.io/pt-br/
190
-
weight: 10
191
-
pre: home
192
-
- name: Documentação
193
-
url: /pt-br/
194
-
weight: 20
195
-
pre: question
196
-
post: active
197
-
- name: API
198
-
url: https://try.gitea.io/api/swagger
199
-
weight: 45
200
-
pre: plug
201
-
- name: Blog
202
-
url: https://blog.gitea.io/
203
-
weight: 30
204
-
pre: rss
205
-
- name: Código-fonte
206
-
url: https://code.gitea.io/
207
-
weight: 40
208
-
pre: code
209
-
- name: Translation
210
-
url: https://crowdin.com/project/gitea
211
-
weight: 41
212
-
pre: language
213
-
- name: Downloads
214
-
url: https://dl.gitea.io/
215
-
weight: 50
216
-
pre: download
217
-
- name: GitHub
218
-
url: https://github.com/go-gitea/
219
-
weight: 60
220
-
pre: github
221
-
- name: Chat no Discord
222
-
url: https://discord.gg/Gitea
223
-
weight: 70
224
-
pre: comment
225
-
- name: Forum
226
-
url: https://discourse.gitea.io/
227
-
weight: 80
228
-
pre: group
229
-
230
-
nl-nl:
231
-
weight: 4
232
-
languageName: Nederlands
233
-
menu:
234
-
page:
235
-
- name: Website
236
-
url: https://gitea.io/nl-nl/
237
-
weight: 10
238
-
pre: home
239
-
- name: Docs
240
-
url: /nl-nl/
241
-
weight: 20
242
-
pre: question
243
-
post: active
244
-
- name: API
245
-
url: https://try.gitea.io/api/swagger
246
-
weight: 45
247
-
pre: plug
248
-
- name: Blog
249
-
url: https://blog.gitea.io/
250
-
weight: 30
251
-
pre: rss
252
-
- name: Code
253
-
url: https://code.gitea.io/
254
-
weight: 40
255
-
pre: code
256
-
- name: Translation
257
-
url: https://crowdin.com/project/gitea
258
-
weight: 41
259
-
pre: language
260
-
- name: Downloads
261
-
url: https://dl.gitea.io/
262
-
weight: 50
263
-
pre: download
264
-
- name: GitHub
265
-
url: https://github.com/go-gitea/
266
-
weight: 60
267
-
pre: github
268
-
- name: Discord Chat
269
-
url: https://discord.gg/Gitea
270
-
weight: 70
271
-
pre: comment
272
-
- name: Forum
273
-
url: https://discourse.gitea.io/
274
-
weight: 80
275
-
pre: group
276
-
277
-
fr-fr:
278
-
weight: 5
279
-
languageName: Français
280
-
menu:
281
-
page:
282
-
- name: Site
283
-
url: https://gitea.io/en-us/
284
-
weight: 10
285
-
pre: home
286
-
post: active
287
-
- name: Documentation
288
-
url: /fr-fr/
289
-
weight: 20
290
-
pre: question
291
-
- name: API
292
-
url: https://try.gitea.io/api/swagger
293
-
weight: 45
294
-
pre: plug
295
-
- name: Blog
296
-
url: https://blog.gitea.io/
297
-
weight: 30
298
-
pre: rss
299
-
- name: Code
300
-
url: https://code.gitea.io/
301
-
weight: 40
302
-
pre: code
303
-
- name: Translation
304
-
url: https://crowdin.com/project/gitea
305
-
weight: 41
306
-
pre: language
307
-
- name: Téléchargement
308
-
url: https://dl.gitea.io/
309
-
weight: 50
310
-
pre: download
311
-
- name: GitHub
312
-
url: https://github.com/go-gitea/
313
-
weight: 60
314
-
pre: github
315
-
- name: Discord Chat
316
-
url: https://discord.gg/Gitea
317
-
weight: 70
318
-
pre: comment
319
-
- name: Forum
320
-
url: https://discourse.gitea.io/
321
-
weight: 80
322
-
pre: group
323
-
324
-
de-de:
325
-
weight: 6
326
-
languageName: Deutsch
327
-
menu:
328
-
page:
329
-
- name: Webseite
330
-
url: https://gitea.io/en-us/
331
-
weight: 10
332
-
pre: home
333
-
post: active
334
-
- name: Dokumentation
335
-
url: /de-de/
336
-
weight: 20
337
-
pre: question
338
-
- name: API
339
-
url: https://try.gitea.io/api/swagger
340
-
weight: 45
341
-
pre: plug
342
-
- name: Blog
343
-
url: https://blog.gitea.io/
344
-
weight: 30
345
-
pre: rss
346
-
- name: Code
347
-
url: https://code.gitea.io/
348
-
weight: 40
349
-
pre: code
350
-
- name: Übersetzung
351
-
url: https://crowdin.com/project/gitea
352
-
weight: 41
353
-
pre: language
354
-
- name: Downloads
355
-
url: https://dl.gitea.io/
356
-
weight: 50
357
-
pre: download
358
-
- name: GitHub
359
-
url: https://github.com/go-gitea/
360
-
weight: 60
361
-
pre: github
362
-
- name: Discord Chat
363
-
url: https://discord.gg/Gitea
364
-
weight: 70
365
-
pre: comment
366
-
- name: Forum
367
-
url: https://discourse.gitea.io/
368
-
weight: 80
369
-
pre: group
+2
-2
docs/content/doc/actions.en-us.md
docs/content/actions.en-us.md
+2
-2
docs/content/doc/actions.en-us.md
docs/content/actions.en-us.md
+2
-2
docs/content/doc/administration.en-us.md
docs/content/administration.en-us.md
+2
-2
docs/content/doc/administration.en-us.md
docs/content/administration.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Administration"
4
4
slug: "administration"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
menu:
9
9
sidebar:
10
10
name: "Administration"
11
-
weight: 20
11
+
sidebar_position: 20
12
12
collapse: true
13
13
identifier: "administration"
14
14
---
+2
-2
docs/content/doc/administration.fr-fr.md
docs/content/administration.fr-fr.md
+2
-2
docs/content/doc/administration.fr-fr.md
docs/content/administration.fr-fr.md
+2
-2
docs/content/doc/administration.zh-cn.md
docs/content/administration.zh-cn.md
+2
-2
docs/content/doc/administration.zh-cn.md
docs/content/administration.zh-cn.md
+2
-2
docs/content/doc/administration.zh-tw.md
docs/content/administration.zh-tw.md
+2
-2
docs/content/doc/administration.zh-tw.md
docs/content/administration.zh-tw.md
docs/content/doc/administration/_index.en-us.md
docs/content/administration/_index.en-us.md
docs/content/doc/administration/_index.en-us.md
docs/content/administration/_index.en-us.md
docs/content/doc/administration/_index.zh-cn.md
docs/content/administration/_index.zh-cn.md
docs/content/doc/administration/_index.zh-cn.md
docs/content/administration/_index.zh-cn.md
docs/content/doc/administration/_index.zh-tw.md
docs/content/administration/_index.zh-tw.md
docs/content/doc/administration/_index.zh-tw.md
docs/content/administration/_index.zh-tw.md
+2
-2
docs/content/doc/administration/adding-legal-pages.en-us.md
docs/content/administration/adding-legal-pages.en-us.md
+2
-2
docs/content/doc/administration/adding-legal-pages.en-us.md
docs/content/administration/adding-legal-pages.en-us.md
···
2
2
date: "2019-12-28"
3
3
title: "Adding Legal Pages"
4
4
slug: adding-legal-pages
5
-
weight: 110
5
+
sidebar_position: 110
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
12
12
parent: "administration"
13
13
name: "Adding Legal Pages"
14
14
identifier: "adding-legal-pages"
15
-
weight: 110
15
+
sidebar_position: 110
16
16
---
17
17
18
18
Some jurisdictions (such as EU), requires certain legal pages (e.g. Privacy Policy) to be added to website. Follow these steps to add them to your Gitea instance.
+2
-2
docs/content/doc/administration/adding-legal-pages.zh-cn.md
docs/content/administration/adding-legal-pages.zh-cn.md
+2
-2
docs/content/doc/administration/adding-legal-pages.zh-cn.md
docs/content/administration/adding-legal-pages.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "添加法律页面"
4
4
slug: adding-legal-pages
5
-
weight: 110
5
+
sidebar_position: 110
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
12
12
parent: "administration"
13
13
name: "添加法律页面"
14
14
identifier: "adding-legal-pages"
15
-
weight: 110
15
+
sidebar_position: 110
16
16
---
17
17
18
18
一些法域（例如欧盟）要求在网站上添加特定的法律页面（例如隐私政策）。按照以下步骤将它们添加到你的 Gitea 实例中。
+2
-6
docs/content/doc/administration/backup-and-restore.en-us.md
docs/content/administration/backup-and-restore.en-us.md
+2
-6
docs/content/doc/administration/backup-and-restore.en-us.md
docs/content/administration/backup-and-restore.en-us.md
···
2
2
date: "2017-01-01T16:00:00+02:00"
3
3
title: "Backup and Restore"
4
4
slug: "backup-and-restore"
5
-
weight: 11
5
+
sidebar_position: 11
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Backup and Restore"
14
-
weight: 11
14
+
sidebar_position: 11
15
15
identifier: "backup-and-restore"
16
16
---
17
17
···
19
19
20
20
Gitea currently has a `dump` command that will save the installation to a ZIP file. This
21
21
file can be unpacked and used to restore an instance.
22
-
23
-
**Table of Contents**
24
-
25
-
{{< toc >}}
26
22
27
23
## Backup Consistency
28
24
+2
-2
docs/content/doc/administration/backup-and-restore.zh-cn.md
docs/content/administration/backup-and-restore.zh-cn.md
+2
-2
docs/content/doc/administration/backup-and-restore.zh-cn.md
docs/content/administration/backup-and-restore.zh-cn.md
···
2
2
date: "2018-06-06T09:33:00+08:00"
3
3
title: "备份与恢复"
4
4
slug: "backup-and-restore"
5
-
weight: 11
5
+
sidebar_position: 11
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "备份与恢复"
14
-
weight: 11
14
+
sidebar_position: 11
15
15
identifier: "backup-and-restore"
16
16
---
17
17
+2
-2
docs/content/doc/administration/backup-and-restore.zh-tw.md
docs/content/administration/backup-and-restore.zh-tw.md
+2
-2
docs/content/doc/administration/backup-and-restore.zh-tw.md
docs/content/administration/backup-and-restore.zh-tw.md
···
2
2
date: "2017-01-01T16:00:00+02:00"
3
3
title: "用法: 備份與還原"
4
4
slug: "backup-and-restore"
5
-
weight: 11
5
+
sidebar_position: 11
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "備份與還原"
14
-
weight: 11
14
+
sidebar_position: 11
15
15
identifier: "backup-and-restore"
16
16
---
17
17
+4
-8
docs/content/doc/administration/cmd-embedded.en-us.md
docs/content/administration/cmd-embedded.en-us.md
+4
-8
docs/content/doc/administration/cmd-embedded.en-us.md
docs/content/administration/cmd-embedded.en-us.md
···
2
2
date: "2020-01-25T21:00:00-03:00"
3
3
title: "Embedded data extraction tool"
4
4
slug: "cmd-embedded"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Embedded data extraction tool"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "cmd-embedded"
16
16
---
17
17
18
18
# Embedded data extraction tool
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
Gitea's executable contains all the resources required to run: templates, images, style-sheets
25
21
and translations. Any of them can be overridden by placing a replacement in a matching path
26
-
inside the `custom` directory (see [Customizing Gitea]({{< relref "doc/administration/customizing-gitea.en-us.md" >}})).
22
+
inside the `custom` directory (see [Customizing Gitea](administration/customizing-gitea.md)).
27
23
28
24
To obtain a copy of the embedded resources ready for editing, the `embedded` command from the CLI
29
25
can be used from the OS shell interface.
···
87
83
The `--custom` flag tells Gitea to extract the files directly into the `custom` directory.
88
84
For this to work, the command needs to know the location of the `app.ini` configuration
89
85
file (`--config`) and, depending of the configuration, be ran from the directory where
90
-
Gitea normally starts. See [Customizing Gitea]({{< relref "doc/administration/customizing-gitea.en-us.md" >}}) for details.
86
+
Gitea normally starts. See [Customizing Gitea](administration/customizing-gitea.md) for details.
91
87
92
88
The `--overwrite` flag allows any existing files in the destination directory to be overwritten.
93
89
+4
-8
docs/content/doc/administration/cmd-embedded.zh-cn.md
docs/content/administration/cmd-embedded.zh-cn.md
+4
-8
docs/content/doc/administration/cmd-embedded.zh-cn.md
docs/content/administration/cmd-embedded.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "嵌入资源提取工具"
4
4
slug: "cmd-embedded"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "嵌入资源提取工具"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "cmd-embedded"
16
16
---
17
17
18
18
# 嵌入资源提取工具
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
-
Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置]({{< relref "doc/administration/customizing-gitea.zh-cn.md" >}})）。
20
+
Gitea 的可执行文件包含了运行所需的所有资源：模板、图片、样式表和翻译文件。你可以通过在 `custom` 目录下的相应路径中放置替换文件来覆盖其中的任何资源（详见 [自定义 Gitea 配置](administration/customizing-gitea.md)）。
25
21
26
22
要获取嵌入资源的副本以进行编辑，可以使用 CLI 中的 `embedded` 命令，通过操作系统的 shell 执行。
27
23
···
75
71
76
72
`--destination` 选项用于指定提取文件的目标目录。默认为当前目录。
77
73
78
-
`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置]({{< relref "doc/administration/customizing-gitea.zh-cn.md" >}})。
74
+
`--custom` 标志告知 Gitea 直接将文件提取到 `custom` 目录中。为使其正常工作，该命令需要知道 `app.ini` 配置文件的位置（通过 `--config` 指定），并且根据配置的不同，需要从 Gitea 通常启动的目录运行。有关详细信息，请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md)。
79
75
80
76
`--overwrite` 标志允许覆盖目标目录中的任何现有文件。
81
77
+2
-6
docs/content/doc/administration/command-line.en-us.md
docs/content/administration/command-line.en-us.md
+2
-6
docs/content/doc/administration/command-line.en-us.md
docs/content/administration/command-line.en-us.md
···
2
2
date: "2017-01-01T16:00:00+02:00"
3
3
title: "Gitea Command Line"
4
4
slug: "command-line"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Command Line"
14
-
weight: 1
14
+
sidebar_position: 1
15
15
identifier: "command-line"
16
16
---
17
17
18
18
# Command Line
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Usage
25
21
+2
-6
docs/content/doc/administration/command-line.zh-cn.md
docs/content/administration/command-line.zh-cn.md
+2
-6
docs/content/doc/administration/command-line.zh-cn.md
docs/content/administration/command-line.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "Gitea 命令行"
4
4
slug: "command-line"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Gitea 命令行"
14
-
weight: 1
14
+
sidebar_position: 1
15
15
identifier: "command-line"
16
16
---
17
17
18
18
# 命令行
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 用法
25
21
+59
-61
docs/content/doc/administration/config-cheat-sheet.en-us.md
docs/content/administration/config-cheat-sheet.en-us.md
+59
-61
docs/content/doc/administration/config-cheat-sheet.en-us.md
docs/content/administration/config-cheat-sheet.en-us.md
···
2
2
date: "2016-12-26T16:00:00+02:00"
3
3
title: "Config Cheat Sheet"
4
4
slug: "config-cheat-sheet"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Config Cheat Sheet"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "config-cheat-sheet"
16
16
---
17
17
···
34
34
Values containing `#` or `;` must be quoted using `` ` `` or `"""`.
35
35
36
36
**Note:** A full restart is required for Gitea configuration changes to take effect.
37
-
38
-
{{< toc >}}
39
37
40
38
## Default Configuration (non-`app.ini` configuration)
41
39
···
82
80
- `SCRIPT_TYPE`: **bash**: The script type this server supports. Usually this is `bash`,
83
81
but some users report that only `sh` is available.
84
82
- `DETECTED_CHARSETS_ORDER`: **UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, UTF-32LE, ISO-8859, windows-1252, ISO-8859, windows-1250, ISO-8859, ISO-8859, ISO-8859, windows-1253, ISO-8859, windows-1255, ISO-8859, windows-1251, windows-1256, KOI8-R, ISO-8859, windows-1254, Shift_JIS, GB18030, EUC-JP, EUC-KR, Big5, ISO-2022, ISO-2022, ISO-2022, IBM424_rtl, IBM424_ltr, IBM420_rtl, IBM420_ltr**: Tie-break order of detected charsets - if the detected charsets have equal confidence, charsets earlier in the list will be chosen in preference to those later. Adding `defaults` will place the unnamed charsets at that point.
85
-
- `ANSI_CHARSET`: **\<empty\>**: Default ANSI charset to override non-UTF-8 charsets to.
83
+
- `ANSI_CHARSET`: **_empty_**: Default ANSI charset to override non-UTF-8 charsets to.
86
84
- `FORCE_PRIVATE`: **false**: Force every new repository to be private.
87
85
- `DEFAULT_PRIVATE`: **last**: Default private when creating a new repository.
88
86
\[last, private, public\]
···
97
95
default SSH port is used.
98
96
- `GO_GET_CLONE_URL_PROTOCOL`: **https**: Value for the "go get" request returns the repository url as https or ssh
99
97
default is https.
100
-
- `ACCESS_CONTROL_ALLOW_ORIGIN`: **\<empty\>**: Value for Access-Control-Allow-Origin header,
98
+
- `ACCESS_CONTROL_ALLOW_ORIGIN`: **_empty_**: Value for Access-Control-Allow-Origin header,
101
99
default is not to present. **WARNING**: This maybe harmful to you website if you do not
102
100
give it a right value.
103
101
- `DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH`: **false**: Close an issue if a commit on a non default branch marks it as closed.
···
147
145
148
146
- `ENABLED`: **true**: Whether repository file uploads are enabled
149
147
- `TEMP_PATH`: **data/tmp/uploads**: Path for uploads (content gets deleted on Gitea restart)
150
-
- `ALLOWED_TYPES`: **\<empty\>**: Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
148
+
- `ALLOWED_TYPES`: **_empty_**: Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
151
149
- `FILE_MAX_SIZE`: **3**: Max size of each file in megabytes.
152
150
- `MAX_FILES`: **5**: Max number of files per upload
153
151
154
152
### Repository - Release (`repository.release`)
155
153
156
-
- `ALLOWED_TYPES`: **\<empty\>**: Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
154
+
- `ALLOWED_TYPES`: **_empty_**: Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
157
155
- `DEFAULT_PAGING_NUM`: **10**: The default paging number of releases user interface
158
156
- For settings related to file attachments on releases, see the `attachment` section.
159
157
···
291
289
- `ROOT_URL`: **%(PROTOCOL)s://%(DOMAIN)s:%(HTTP\_PORT)s/**:
292
290
Overwrite the automatically generated public URL.
293
291
This is useful if the internal and the external URL don't match (e.g. in Docker).
294
-
- `STATIC_URL_PREFIX`: **\<empty\>**:
292
+
- `STATIC_URL_PREFIX`: **_empty_**:
295
293
Overwrite this option to request static resources from a different URL.
296
294
This includes CSS files, images, JS files and web fonts.
297
295
Avatar images are dynamic resources and still served by Gitea.
···
337
335
- `SSH_ROOT_PATH`: **~/.ssh**: Root path of SSH directory.
338
336
- `SSH_CREATE_AUTHORIZED_KEYS_FILE`: **true**: Gitea will create a authorized_keys file by default when it is not using the internal ssh server. If you intend to use the AuthorizedKeysCommand functionality then you should turn this off.
339
337
- `SSH_AUTHORIZED_KEYS_BACKUP`: **false**: Enable SSH Authorized Key Backup when rewriting all keys, default is false.
340
-
- `SSH_TRUSTED_USER_CA_KEYS`: **\<empty\>**: Specifies the public keys of certificate authorities that are trusted to sign user certificates for authentication. Multiple keys should be comma separated. E.g.`ssh-<algorithm> <key>` or `ssh-<algorithm> <key1>, ssh-<algorithm> <key2>`. For more information see `TrustedUserCAKeys` in the sshd config man pages. When empty no file will be created and `SSH_AUTHORIZED_PRINCIPALS_ALLOW` will default to `off`.
338
+
- `SSH_TRUSTED_USER_CA_KEYS`: **_empty_**: Specifies the public keys of certificate authorities that are trusted to sign user certificates for authentication. Multiple keys should be comma separated. E.g.`ssh-<algorithm> <key>` or `ssh-<algorithm> <key1>, ssh-<algorithm> <key2>`. For more information see `TrustedUserCAKeys` in the sshd config man pages. When empty no file will be created and `SSH_AUTHORIZED_PRINCIPALS_ALLOW` will default to `off`.
341
339
- `SSH_TRUSTED_USER_CA_KEYS_FILENAME`: **`RUN_USER`/.ssh/gitea-trusted-user-ca-keys.pem**: Absolute path of the `TrustedUserCaKeys` file Gitea will manage. If you're running your own ssh server and you want to use the Gitea managed file you'll also need to modify your sshd_config to point to this file. The official docker image will automatically work without further configuration.
342
340
- `SSH_AUTHORIZED_PRINCIPALS_ALLOW`: **off** or **username, email**: \[off, username, email, anything\]: Specify the principals values that users are allowed to use as principal. When set to `anything` no checks are done on the principal string. When set to `off` authorized principal are not allowed to be set.
343
341
- `SSH_CREATE_AUTHORIZED_PRINCIPALS_FILE`: **false/true**: Gitea will create a authorized_principals file by default when it is not using the internal ssh server and `SSH_AUTHORIZED_PRINCIPALS_ALLOW` is not `off`.
···
348
346
- `SSH_SERVER_MACS`: **hmac-sha2-256-etm@openssh.com, hmac-sha2-256, hmac-sha1**: For the built-in SSH server, choose the MACs to support for SSH connections, for system SSH this setting has no effect
349
347
- `SSH_SERVER_HOST_KEYS`: **ssh/gitea.rsa, ssh/gogs.rsa**: For the built-in SSH server, choose the keypairs to offer as the host key. The private key should be at `SSH_SERVER_HOST_KEY` and the public `SSH_SERVER_HOST_KEY.pub`. Relative paths are made absolute relative to the `APP_DATA_PATH`. If no key exists a 4096 bit RSA key will be created for you.
350
348
- `SSH_KEY_TEST_PATH`: **/tmp**: Directory to create temporary files in when testing public keys using ssh-keygen, default is the system temporary directory.
351
-
- `SSH_KEYGEN_PATH`: **\<empty\>**: Use `ssh-keygen` to parse public SSH keys. The value is passed to the shell. By default, Gitea does the parsing itself.
349
+
- `SSH_KEYGEN_PATH`: **_empty_**: Use `ssh-keygen` to parse public SSH keys. The value is passed to the shell. By default, Gitea does the parsing itself.
352
350
- `SSH_EXPOSE_ANONYMOUS`: **false**: Enable exposure of SSH clone URL to anonymous visitors, default is false.
353
351
- `SSH_PER_WRITE_TIMEOUT`: **30s**: Timeout for any write to the SSH connections. (Set to
354
352
-1 to disable all timeouts.)
···
367
365
- `LANDING_PAGE`: **home**: Landing page for unauthenticated users \[home, explore, organizations, login, **custom**\]. Where custom would instead be any URL such as "/org/repo" or even `https://anotherwebsite.com`
368
366
- `LFS_START_SERVER`: **false**: Enables Git LFS support.
369
367
- `LFS_CONTENT_PATH`: **%(APP_DATA_PATH)s/lfs**: Default LFS content path. (if it is on local storage.) **DEPRECATED** use settings in `[lfs]`.
370
-
- `LFS_JWT_SECRET`: **\<empty\>**: LFS authentication secret, change this a unique string.
371
-
- `LFS_JWT_SECRET_URI`: **\<empty\>**: Instead of defining LFS_JWT_SECRET in the configuration, this configuration option can be used to give Gitea a path to a file that contains the secret (example value: `file:/etc/gitea/lfs_jwt_secret`)
368
+
- `LFS_JWT_SECRET`: **_empty_**: LFS authentication secret, change this a unique string.
369
+
- `LFS_JWT_SECRET_URI`: **_empty_**: Instead of defining LFS_JWT_SECRET in the configuration, this configuration option can be used to give Gitea a path to a file that contains the secret (example value: `file:/etc/gitea/lfs_jwt_secret`)
372
370
- `LFS_HTTP_AUTH_EXPIRY`: **24h**: LFS authentication validity period in time.Duration, pushes taking longer than this may fail.
373
371
- `LFS_MAX_FILE_SIZE`: **0**: Maximum allowed LFS file size in bytes (Set to 0 for no limit).
374
372
- `LFS_LOCKS_PAGING_NUM`: **50**: Maximum number of LFS Locks returned per page.
···
377
375
- `REDIRECTOR_USE_PROXY_PROTOCOL`: **%(USE_PROXY_PROTOCOL)s**: expect PROXY protocol header on connections to https redirector.
378
376
- `PORT_TO_REDIRECT`: **80**: Port for the http redirection service to listen on. Used when `REDIRECT_OTHER_PORT` is true.
379
377
- `SSL_MIN_VERSION`: **TLSv1.2**: Set the minimum version of ssl support.
380
-
- `SSL_MAX_VERSION`: **\<empty\>**: Set the maximum version of ssl support.
378
+
- `SSL_MAX_VERSION`: **_empty_**: Set the maximum version of ssl support.
381
379
- `SSL_CURVE_PREFERENCES`: **X25519,P256**: Set the preferred curves,
382
380
- `SSL_CIPHER_SUITES`: **ecdhe_ecdsa_with_aes_256_gcm_sha384,ecdhe_rsa_with_aes_256_gcm_sha384,ecdhe_ecdsa_with_aes_128_gcm_sha256,ecdhe_rsa_with_aes_128_gcm_sha256,ecdhe_ecdsa_with_chacha20_poly1305,ecdhe_rsa_with_chacha20_poly1305**: Set the preferred cipher suites.
383
381
- If there is no hardware support for AES suites, by default the ChaCha suites will be preferred over the AES suites.
···
413
411
- "ecdhe_rsa_with_chacha20_poly1305" is an alias for "ecdhe_rsa_with_chacha20_poly1305_sha256"
414
412
- "ecdhe_ecdsa_with_chacha20_poly1305" is alias for "ecdhe_ecdsa_with_chacha20_poly1305_sha256"
415
413
- `ENABLE_ACME`: **false**: Flag to enable automatic certificate management via an ACME capable Certificate Authority (CA) server (default: Lets Encrypt). If enabled, `CERT_FILE` and `KEY_FILE` are ignored, and the CA must resolve `DOMAIN` to this gitea server. Ensure that DNS records are set and either port `80` or port `443` are accessible by the CA server (the public internet by default), and redirected to the appropriate ports `PORT_TO_REDIRECT` or `HTTP_PORT` respectively.
416
-
- `ACME_URL`: **\<empty\>**: The CA's ACME directory URL, e.g. for a self-hosted [smallstep CA server](https://github.com/smallstep/certificates), it can look like `https://ca.example.com/acme/acme/directory`. If left empty, it defaults to using Let's Encerypt's production CA (check `LETSENCRYPT_ACCEPTTOS` as well).
414
+
- `ACME_URL`: **_empty_**: The CA's ACME directory URL, e.g. for a self-hosted [smallstep CA server](https://github.com/smallstep/certificates), it can look like `https://ca.example.com/acme/acme/directory`. If left empty, it defaults to using Let's Encerypt's production CA (check `LETSENCRYPT_ACCEPTTOS` as well).
417
415
- `ACME_ACCEPTTOS`: **false**: This is an explicit check that you accept the terms of service of the ACME provider. The default is Lets Encrypt [terms of service](https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf).
418
416
- `ACME_DIRECTORY`: **https**: Directory that the certificate manager will use to cache information such as certs and private keys.
419
-
- `ACME_EMAIL`: **\<empty\>**: Email used for the ACME registration. Usually it is to notify about problems with issued certificates.
420
-
- `ACME_CA_ROOT`: **\<empty\>**: The CA's root certificate. If left empty, it defaults to using the system's trust chain.
417
+
- `ACME_EMAIL`: **_empty_**: Email used for the ACME registration. Usually it is to notify about problems with issued certificates.
418
+
- `ACME_CA_ROOT`: **_empty_**: The CA's root certificate. If left empty, it defaults to using the system's trust chain.
421
419
- `ALLOW_GRACEFUL_RESTARTS`: **true**: Perform a graceful restart on SIGHUP
422
420
- `GRACEFUL_HAMMER_TIME`: **60s**: After a restart the parent process will stop accepting new connections and will allow requests to finish before stopping. Shutdown will be forced if it takes longer than this time.
423
421
- `STARTUP_TIMEOUT`: **0**: Shutsdown the server if startup takes longer than the provided time. On Windows setting this sends a waithint to the SVC host to tell the SVC host startup may take some time. Please note startup is determined by the opening of the listeners - HTTP/HTTPS/SSH. Indexers may take longer to startup and can have their own timeouts.
···
428
426
- `HOST`: **127.0.0.1:3306**: Database host address and port or absolute path for unix socket \[mysql, postgres\] (ex: /var/run/mysqld/mysqld.sock).
429
427
- `NAME`: **gitea**: Database name.
430
428
- `USER`: **root**: Database username.
431
-
- `PASSWD`: **\<empty\>**: Database user password. Use \`your password\` or """your password""" for quoting if you use special characters in the password.
432
-
- `SCHEMA`: **\<empty\>**: For PostgreSQL only, schema to use if different from "public". The schema must exist beforehand,
429
+
- `PASSWD`: **_empty_**: Database user password. Use \`your password\` or """your password""" for quoting if you use special characters in the password.
430
+
- `SCHEMA`: **_empty_**: For PostgreSQL only, schema to use if different from "public". The schema must exist beforehand,
433
431
the user must have creation privileges on it, and the user search path must be set to the look into the schema first
434
432
(e.g. `ALTER USER user SET SEARCH_PATH = schema_name,"$user",public;`).
435
433
- `SSL_MODE`: **disable**: SSL/TLS encryption mode for connecting to the database. This option is only applied for PostgreSQL and MySQL.
···
517
515
518
516
- `INSTALL_LOCK`: **false**: Controls access to the installation page. When set to "true", the installation page is not accessible.
519
517
- `SECRET_KEY`: **\<random at every install\>**: Global secret key. This key is VERY IMPORTANT, if you lost it, the data encrypted by it (like 2FA secret) can't be decrypted anymore.
520
-
- `SECRET_KEY_URI`: **\<empty\>**: Instead of defining SECRET_KEY, this option can be used to use the key stored in a file (example value: `file:/etc/gitea/secret_key`). It shouldn't be lost like SECRET_KEY.
518
+
- `SECRET_KEY_URI`: **_empty_**: Instead of defining SECRET_KEY, this option can be used to use the key stored in a file (example value: `file:/etc/gitea/secret_key`). It shouldn't be lost like SECRET_KEY.
521
519
- `LOGIN_REMEMBER_DAYS`: **7**: Cookie lifetime, in days.
522
520
- `COOKIE_USERNAME`: **gitea\_awesome**: Name of the cookie used to store the current username.
523
521
- `COOKIE_REMEMBER_NAME`: **gitea\_incredible**: Name of cookie used to store authentication
···
543
541
- `ONLY_ALLOW_PUSH_IF_GITEA_ENVIRONMENT_SET`: **true**: Set to `false` to allow local users to push to gitea-repositories without setting up the Gitea environment. This is not recommended and if you want local users to push to Gitea repositories you should set the environment appropriately.
544
542
- `IMPORT_LOCAL_PATHS`: **false**: Set to `false` to prevent all users (including admin) from importing local path on server.
545
543
- `INTERNAL_TOKEN`: **\<random at every install if no uri set\>**: Secret used to validate communication within Gitea binary.
546
-
- `INTERNAL_TOKEN_URI`: **\<empty\>**: Instead of defining INTERNAL_TOKEN in the configuration, this configuration option can be used to give Gitea a path to a file that contains the internal token (example value: `file:/etc/gitea/internal_token`)
544
+
- `INTERNAL_TOKEN_URI`: **_empty_**: Instead of defining INTERNAL_TOKEN in the configuration, this configuration option can be used to give Gitea a path to a file that contains the internal token (example value: `file:/etc/gitea/internal_token`)
547
545
- `PASSWORD_HASH_ALGO`: **pbkdf2**: The hash algorithm to use \[argon2, pbkdf2, pbkdf2_v1, pbkdf2_hi, scrypt, bcrypt\], argon2 and scrypt will spend significant amounts of memory.
548
546
- Note: The default parameters for `pbkdf2` hashing have changed - the previous settings are available as `pbkdf2_v1` but are not recommended.
549
547
- The hash functions may be tuned by using `$` after the algorithm:
···
574
572
## Camo (`camo`)
575
573
576
574
- `ENABLED`: **false**: Enable media proxy, we support images only at the moment.
577
-
- `SERVER_URL`: **\<empty\>**: URL of camo server, it **is required** if camo is enabled.
578
-
- `HMAC_KEY`: **\<empty\>**: Provide the HMAC key for encoding URLs, it **is required** if camo is enabled.
575
+
- `SERVER_URL`: **_empty_**: URL of camo server, it **is required** if camo is enabled.
576
+
- `HMAC_KEY`: **_empty_**: Provide the HMAC key for encoding URLs, it **is required** if camo is enabled.
579
577
- `ALLWAYS`: **false**: Set to true to use camo for both HTTP and HTTPS content, otherwise only non-HTTPS URLs are proxied
580
578
581
579
## OpenID (`openid`)
582
580
583
581
- `ENABLE_OPENID_SIGNIN`: **false**: Allow authentication in via OpenID.
584
582
- `ENABLE_OPENID_SIGNUP`: **! DISABLE\_REGISTRATION**: Allow registering via OpenID.
585
-
- `WHITELISTED_URIS`: **\<empty\>**: If non-empty, list of POSIX regex patterns matching
583
+
- `WHITELISTED_URIS`: **_empty_**: If non-empty, list of POSIX regex patterns matching
586
584
OpenID URI's to permit.
587
-
- `BLACKLISTED_URIS`: **\<empty\>**: If non-empty, list of POSIX regex patterns matching
585
+
- `BLACKLISTED_URIS`: **_empty_**: If non-empty, list of POSIX regex patterns matching
588
586
OpenID URI's to block.
589
587
590
588
## OAuth2 Client (`oauth2_client`)
591
589
592
590
- `REGISTER_EMAIL_CONFIRM`: _[service]_ **REGISTER\_EMAIL\_CONFIRM**: Set this to enable or disable email confirmation of OAuth2 auto-registration. (Overwrites the REGISTER\_EMAIL\_CONFIRM setting of the `[service]` section)
593
-
- `OPENID_CONNECT_SCOPES`: **\<empty\>**: List of additional openid connect scopes. (`openid` is implicitly added)
591
+
- `OPENID_CONNECT_SCOPES`: **_empty_**: List of additional openid connect scopes. (`openid` is implicitly added)
594
592
- `ENABLE_AUTO_REGISTRATION`: **false**: Automatically create user accounts for new oauth2 users.
595
593
- `USERNAME`: **nickname**: The source of the username for new oauth2 accounts:
596
594
- userid - use the userid / sub attribute
···
654
652
- `ENABLE_TIMETRACKING`: **true**: Enable Timetracking feature.
655
653
- `DEFAULT_ENABLE_TIMETRACKING`: **true**: Allow repositories to use timetracking by default.
656
654
- `DEFAULT_ALLOW_ONLY_CONTRIBUTORS_TO_TRACK_TIME`: **true**: Only allow users with write permissions to track time.
657
-
- `EMAIL_DOMAIN_ALLOWLIST`: **\<empty\>**: If non-empty, comma separated list of domain names that can only be used to register on this instance, wildcard is supported.
658
-
- `EMAIL_DOMAIN_BLOCKLIST`: **\<empty\>**: If non-empty, comma separated list of domain names that cannot be used to register on this instance, wildcard is supported.
655
+
- `EMAIL_DOMAIN_ALLOWLIST`: **_empty_**: If non-empty, comma separated list of domain names that can only be used to register on this instance, wildcard is supported.
656
+
- `EMAIL_DOMAIN_BLOCKLIST`: **_empty_**: If non-empty, comma separated list of domain names that cannot be used to register on this instance, wildcard is supported.
659
657
- `SHOW_REGISTRATION_BUTTON`: **! DISABLE\_REGISTRATION**: Show Registration Button
660
658
- `SHOW_MILESTONES_DASHBOARD_PAGE`: **true** Enable this to show the milestones dashboard page - a view of all the user's milestones
661
659
- `AUTO_WATCH_NEW_REPOS`: **true**: Enable this to let all organisation users watch new repos when they are created
···
699
697
- Wildcard hosts: `*.mydomain.com`, `192.168.100.*`
700
698
- `SKIP_TLS_VERIFY`: **false**: Allow insecure certification.
701
699
- `PAGING_NUM`: **10**: Number of webhook history events that are shown in one page.
702
-
- `PROXY_URL`: **\<empty\>**: Proxy server URL, support http://, https//, socks://, blank will follow environment http_proxy/https_proxy. If not given, will use global proxy setting.
703
-
- `PROXY_HOSTS`: **\<empty\>`**: Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts. If not given, will use global proxy setting.
700
+
- `PROXY_URL`: **_empty_**: Proxy server URL, support http://, https//, socks://, blank will follow environment http_proxy/https_proxy. If not given, will use global proxy setting.
701
+
- `PROXY_HOSTS`: **_empty_`**: Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts. If not given, will use global proxy setting.
704
702
705
703
## Mailer (`mailer`)
706
704
···
711
709
[Gitea 1.17 configuration document](https://github.com/go-gitea/gitea/blob/release/v1.17/docs/content/doc/advanced/config-cheat-sheet.en-us.md)
712
710
713
711
- `ENABLED`: **false**: Enable to use a mail service.
714
-
- `PROTOCOL`: **\<empty\>**: Mail server protocol. One of "smtp", "smtps", "smtp+starttls", "smtp+unix", "sendmail", "dummy". _Before 1.18, this was inferred from a combination of `MAILER_TYPE` and `IS_TLS_ENABLED`._
712
+
- `PROTOCOL`: **_empty_**: Mail server protocol. One of "smtp", "smtps", "smtp+starttls", "smtp+unix", "sendmail", "dummy". _Before 1.18, this was inferred from a combination of `MAILER_TYPE` and `IS_TLS_ENABLED`._
715
713
- SMTP family, if your provider does not explicitly say which protocol it uses but does provide a port, you can set SMTP_PORT instead and this will be inferred.
716
714
- **sendmail** Use the operating system's `sendmail` command instead of SMTP. This is common on Linux systems.
717
715
- **dummy** Send email messages to the log as a testing phase.
718
716
- Note that enabling sendmail will ignore all other `mailer` settings except `ENABLED`, `FROM`, `SUBJECT_PREFIX` and `SENDMAIL_PATH`.
719
717
- Enabling dummy will ignore all settings except `ENABLED`, `SUBJECT_PREFIX` and `FROM`.
720
-
- `SMTP_ADDR`: **\<empty\>**: Mail server address. e.g. smtp.gmail.com. For smtp+unix, this should be a path to a unix socket instead. _Before 1.18, this was combined with `SMTP_PORT` under the name `HOST`._
721
-
- `SMTP_PORT`: **\<empty\>**: Mail server port. If no protocol is specified, it will be inferred by this setting. Common ports are listed below. _Before 1.18, this was combined with `SMTP_ADDR` under the name `HOST`._
718
+
- `SMTP_ADDR`: **_empty_**: Mail server address. e.g. smtp.gmail.com. For smtp+unix, this should be a path to a unix socket instead. _Before 1.18, this was combined with `SMTP_PORT` under the name `HOST`._
719
+
- `SMTP_PORT`: **_empty_**: Mail server port. If no protocol is specified, it will be inferred by this setting. Common ports are listed below. _Before 1.18, this was combined with `SMTP_ADDR` under the name `HOST`._
722
720
- 25: insecure SMTP
723
721
- 465: SMTP Secure
724
722
- 587: StartTLS
···
726
724
- `CLIENT_CERT_FILE`: **custom/mailer/cert.pem**: Client certificate file.
727
725
- `CLIENT_KEY_FILE`: **custom/mailer/key.pem**: Client key file.
728
726
- `FORCE_TRUST_SERVER_CERT`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe. Consider adding the certificate to the system trust store instead.
729
-
- `USER`: **\<empty\>**: Username of mailing user (usually the sender's e-mail address).
730
-
- `PASSWD`: **\<empty\>**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password.
731
-
- Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup]({{< relref "doc/administration/email-setup.en-us.md" >}}) for more information.
727
+
- `USER`: **_empty_**: Username of mailing user (usually the sender's e-mail address).
728
+
- `PASSWD`: **_empty_**: Password of mailing user. Use \`your password\` for quoting if you use special characters in the password.
729
+
- Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or SMTP host is localhost. See [Email Setup](administration/email-setup.md) for more information.
732
730
- `ENABLE_HELO`: **true**: Enable HELO operation.
733
731
- `HELO_HOSTNAME`: **(retrieved from system)**: HELO hostname.
734
-
- `FROM`: **\<empty\>**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \<email@example.com\> format.
735
-
- `ENVELOPE_FROM`: **\<empty\>**: Address set as the From address on the SMTP mail envelope. Set to `<>` to send an empty address.
736
-
- `SUBJECT_PREFIX`: **\<empty\>**: Prefix to be placed before e-mail subject lines.
732
+
- `FROM`: **_empty_**: Mail from address, RFC 5322. This can be just an email address, or the "Name" \<email@example.com\> format.
733
+
- `ENVELOPE_FROM`: **_empty_**: Address set as the From address on the SMTP mail envelope. Set to `<>` to send an empty address.
734
+
- `SUBJECT_PREFIX`: **_empty_**: Prefix to be placed before e-mail subject lines.
737
735
- `SENDMAIL_PATH`: **sendmail**: The location of sendmail on the operating system (can be command or full path).
738
-
- `SENDMAIL_ARGS`: **\<empty\>**: Specify any extra sendmail arguments. (NOTE: you should be aware that email addresses can look like options - if your `sendmail` command takes options you must set the option terminator `--`)
736
+
- `SENDMAIL_ARGS`: **_empty_**: Specify any extra sendmail arguments. (NOTE: you should be aware that email addresses can look like options - if your `sendmail` command takes options you must set the option terminator `--`)
739
737
- `SENDMAIL_TIMEOUT`: **5m**: default timeout for sending email through sendmail
740
738
- `SENDMAIL_CONVERT_CRLF`: **true**: Most versions of sendmail prefer LF line endings rather than CRLF line endings. Set this to false if your version of sendmail requires CRLF line endings.
741
739
- `SEND_BUFFER_LEN`: **100**: Buffer length of mailing queue. **DEPRECATED** use `LENGTH` in `[queue.mailer]`
···
744
742
## Incoming Email (`email.incoming`)
745
743
746
744
- `ENABLED`: **false**: Enable handling of incoming emails.
747
-
- `REPLY_TO_ADDRESS`: **\<empty\>**: The email address including the `%{token}` placeholder that will be replaced per user/action. Example: `incoming+%{token}@example.com`. The placeholder must appear in the user part of the address (before the `@`).
748
-
- `HOST`: **\<empty\>**: IMAP server host.
749
-
- `PORT`: **\<empty\>**: IMAP server port.
750
-
- `USERNAME`: **\<empty\>**: Username of the receiving account.
751
-
- `PASSWORD`: **\<empty\>**: Password of the receiving account.
745
+
- `REPLY_TO_ADDRESS`: **_empty_**: The email address including the `%{token}` placeholder that will be replaced per user/action. Example: `incoming+%{token}@example.com`. The placeholder must appear in the user part of the address (before the `@`).
746
+
- `HOST`: **_empty_**: IMAP server host.
747
+
- `PORT`: **_empty_**: IMAP server port.
748
+
- `USERNAME`: **_empty_**: Username of the receiving account.
749
+
- `PASSWORD`: **_empty_**: Password of the receiving account.
752
750
- `USE_TLS`: **false**: Whether the IMAP server uses TLS.
753
751
- `SKIP_TLS_VERIFY`: **false**: If set to `true`, completely ignores server certificate validation errors. This option is unsafe.
754
752
- `MAILBOX`: **INBOX**: The mailbox name where incoming mail will end up.
···
760
758
- `ENABLED`: **true**: Enable the cache.
761
759
- `ADAPTER`: **memory**: Cache engine adapter, either `memory`, `redis`, `redis-cluster`, `twoqueue` or `memcache`. (`twoqueue` represents a size limited LRU cache.)
762
760
- `INTERVAL`: **60**: Garbage Collection interval (sec), for memory and twoqueue cache only.
763
-
- `HOST`: **\<empty\>**: Connection string for `redis`, `redis-cluster` and `memcache`. For `twoqueue` sets configuration for the queue.
761
+
- `HOST`: **_empty_**: Connection string for `redis`, `redis-cluster` and `memcache`. For `twoqueue` sets configuration for the queue.
764
762
- Redis: `redis://:macaron@127.0.0.1:6379/0?pool_size=100&idle_timeout=180s`
765
763
- Redis-cluster `redis+cluster://:macaron@127.0.0.1:6379/0?pool_size=100&idle_timeout=180s`
766
764
- Memcache: `127.0.0.1:9090;127.0.0.1:9091`
···
781
779
- `COOKIE_NAME`: **i\_like\_gitea**: The name of the cookie used for the session ID.
782
780
- `GC_INTERVAL_TIME`: **86400**: GC interval in seconds.
783
781
- `SESSION_LIFE_TIME`: **86400**: Session life time in seconds, default is 86400 (1 day)
784
-
- `DOMAIN`: **\<empty\>**: Sets the cookie Domain
782
+
- `DOMAIN`: **_empty_**: Sets the cookie Domain
785
783
- `SAME_SITE`: **lax** \[strict, lax, none\]: Set the SameSite setting for the cookie.
786
784
787
785
## Picture (`picture`)
···
836
834
837
835
## Log (`log`)
838
836
839
-
- `ROOT_PATH`: **\<empty\>**: Root path for log files.
837
+
- `ROOT_PATH`: **_empty_**: Root path for log files.
840
838
- `MODE`: **console**: Logging mode. For multiple modes, use a comma to separate values. You can configure each mode in per mode log subsections `\[log.writer-mode-name\]`.
841
839
- `LEVEL`: **Info**: General log level. \[Trace, Debug, Info, Warn, Error, Critical, Fatal, None\]
842
840
- `STACKTRACE_LEVEL`: **None**: Default log level at which to log create stack traces (rarely useful, do not set it). \[Trace, Debug, Info, Warn, Error, Critical, Fatal, None\]
843
841
- `ENABLE_SSH_LOG`: **false**: save ssh log to log file
844
-
- `logger.access.MODE`: **\<empty\>**: The "access" logger
842
+
- `logger.access.MODE`: **_empty_**: The "access" logger
845
843
- `logger.router.MODE`: **,**: The "router" logger, a single comma means it will use the default MODE above
846
844
- `logger.xorm.MODE`: **,**: The "xorm" logger
847
845
···
855
853
- `ResponseWriter`: the responseWriter from the request.
856
854
- `RequestID`: the value matching REQUEST_ID_HEADERS（default: `-`, if not matched）.
857
855
- You must be very careful to ensure that this template does not throw errors or panics as this template runs outside the panic/recovery script.
858
-
- `REQUEST_ID_HEADERS`: **\<empty\>**: You can configure multiple values that are splited by comma here. It will match in the order of configuration, and the first match will be finally printed in the access log.
856
+
- `REQUEST_ID_HEADERS`: **_empty_**: You can configure multiple values that are splited by comma here. It will match in the order of configuration, and the first match will be finally printed in the access log.
859
857
- e.g.
860
858
- In the Request Header: X-Request-ID: **test-id-123**
861
859
- Configuration in app.ini: REQUEST_ID_HEADERS = X-Request-ID
···
923
921
924
922
- `SCHEDULE`: **@midnight**: Cron syntax for scheduling repository health check.
925
923
- `TIMEOUT`: **60s**: Time duration syntax for health check execution timeout.
926
-
- `ARGS`: **\<empty\>**: Arguments for command `git fsck`, e.g. `--unreachable --tags`. See more on http://git-scm.com/docs/git-fsck
924
+
- `ARGS`: **_empty_**: Arguments for command `git fsck`, e.g. `--unreachable --tags`. See more on http://git-scm.com/docs/git-fsck
927
925
928
926
#### Cron - Repository Statistics Check (`cron.check_repo_stats`)
929
927
···
965
963
- `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
966
964
- `TIMEOUT`: **60s**: Time duration syntax for garbage collection execution timeout.
967
965
- `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
968
-
- `ARGS`: **\<empty\>**: Arguments for command `git gc`, e.g. `--aggressive --auto`. The default value is same with [git] -> GC_ARGS
966
+
- `ARGS`: **_empty_**: Arguments for command `git gc`, e.g. `--aggressive --auto`. The default value is same with [git] -> GC_ARGS
969
967
970
968
#### Cron - Update the '.ssh/authorized_keys' file with Gitea SSH keys (`cron.resync_all_sshkeys`)
971
969
···
1047
1045
- `MAX_GIT_DIFF_FILES`: **100**: Max number of files shown in diff view.
1048
1046
- `COMMITS_RANGE_SIZE`: **50**: Set the default commits range size
1049
1047
- `BRANCHES_RANGE_SIZE`: **20**: Set the default branches range size
1050
-
- `GC_ARGS`: **\<empty\>**: Arguments for command `git gc`, e.g. `--aggressive --auto`. See more on http://git-scm.com/docs/git-gc/
1048
+
- `GC_ARGS`: **_empty_**: Arguments for command `git gc`, e.g. `--aggressive --auto`. See more on http://git-scm.com/docs/git-gc/
1051
1049
- `ENABLE_AUTO_GIT_WIRE_PROTOCOL`: **true**: If use Git wire protocol version 2 when Git version >= 2.18, default is true, set to false when you always want Git wire protocol version 1.
1052
1050
To enable this for Git over SSH when using a OpenSSH server, add `AcceptEnv GIT_PROTOCOL` to your sshd_config file.
1053
1051
- `PULL_REQUEST_PUSH_MESSAGE`: **true**: Respond to pushes to a non-default branch with a URL for creating a Pull Request (if the repository has them enabled)
···
1080
1078
- `ENABLED`: **false**: Enables /metrics endpoint for prometheus.
1081
1079
- `ENABLED_ISSUE_BY_LABEL`: **false**: Enable issue by label metrics with format `gitea_issues_by_label{label="bug"} 2`.
1082
1080
- `ENABLED_ISSUE_BY_REPOSITORY`: **false**: Enable issue by repository metrics with format `gitea_issues_by_repository{repository="org/repo"} 5`.
1083
-
- `TOKEN`: **\<empty\>**: You need to specify the token, if you want to include in the authorization the metrics . The same token need to be used in prometheus parameters `bearer_token` or `bearer_token_file`.
1081
+
- `TOKEN`: **_empty_**: You need to specify the token, if you want to include in the authorization the metrics . The same token need to be used in prometheus parameters `bearer_token` or `bearer_token_file`.
1084
1082
1085
1083
## API (`api`)
1086
1084
···
1097
1095
- `REFRESH_TOKEN_EXPIRATION_TIME`: **730**: Lifetime of an OAuth2 refresh token in hours
1098
1096
- `INVALIDATE_REFRESH_TOKENS`: **false**: Check if refresh token has already been used
1099
1097
- `JWT_SIGNING_ALGORITHM`: **RS256**: Algorithm used to sign OAuth2 tokens. Valid values: \[`HS256`, `HS384`, `HS512`, `RS256`, `RS384`, `RS512`, `ES256`, `ES384`, `ES512`\]
1100
-
- `JWT_SECRET`: **\<empty\>**: OAuth2 authentication secret for access and refresh tokens, change this to a unique string. This setting is only needed if `JWT_SIGNING_ALGORITHM` is set to `HS256`, `HS384` or `HS512`.
1101
-
- `JWT_SECRET_URI`: **\<empty\>**: Instead of defining JWT_SECRET in the configuration, this configuration option can be used to give Gitea a path to a file that contains the secret (example value: `file:/etc/gitea/oauth2_jwt_secret`)
1098
+
- `JWT_SECRET`: **_empty_**: OAuth2 authentication secret for access and refresh tokens, change this to a unique string. This setting is only needed if `JWT_SIGNING_ALGORITHM` is set to `HS256`, `HS384` or `HS512`.
1099
+
- `JWT_SECRET_URI`: **_empty_**: Instead of defining JWT_SECRET in the configuration, this configuration option can be used to give Gitea a path to a file that contains the secret (example value: `file:/etc/gitea/oauth2_jwt_secret`)
1102
1100
- `JWT_SIGNING_PRIVATE_KEY_FILE`: **jwt/private.pem**: Private key file path used to sign OAuth2 tokens. The path is relative to `APP_DATA_PATH`. This setting is only needed if `JWT_SIGNING_ALGORITHM` is set to `RS256`, `RS384`, `RS512`, `ES256`, `ES384` or `ES512`. The file must contain a RSA or ECDSA private key in the PKCS8 format. If no key exists a 4096 bit key will be created for you.
1103
1101
- `MAX_TOKEN_LENGTH`: **32767**: Maximum length of token/cookie to accept from OAuth2 provider
1104
1102
···
1125
1123
1126
1124
- ENABLED: **false** Enable markup support; set to **true** to enable this renderer.
1127
1125
- NEED\_POSTPROCESS: **true** set to **true** to replace links / sha1 and etc.
1128
-
- FILE\_EXTENSIONS: **\<empty\>** List of file extensions that should be rendered by an external
1126
+
- FILE\_EXTENSIONS: **_empty_** List of file extensions that should be rendered by an external
1129
1127
command. Multiple extensions needs a comma as splitter.
1130
1128
- RENDER\_COMMAND: External command to render all matching extensions.
1131
1129
- IS\_INPUT\_FILE: **false** Input is not a standard input but a file param followed `RENDER_COMMAND`.
···
1184
1182
1185
1183
- `MAX_ATTEMPTS`: **3**: Max attempts per http/https request on migrations.
1186
1184
- `RETRY_BACKOFF`: **3**: Backoff time per http/https request retry (seconds)
1187
-
- `ALLOWED_DOMAINS`: **\<empty\>**: Domains allowlist for migrating repositories, default is blank. It means everything will be allowed. Multiple domains could be separated by commas. Wildcard is supported: `github.com, *.github.com`.
1188
-
- `BLOCKED_DOMAINS`: **\<empty\>**: Domains blocklist for migrating repositories, default is blank. Multiple domains could be separated by commas. When `ALLOWED_DOMAINS` is not blank, this option has a higher priority to deny domains. Wildcard is supported.
1185
+
- `ALLOWED_DOMAINS`: **_empty_**: Domains allowlist for migrating repositories, default is blank. It means everything will be allowed. Multiple domains could be separated by commas. Wildcard is supported: `github.com, *.github.com`.
1186
+
- `BLOCKED_DOMAINS`: **_empty_**: Domains blocklist for migrating repositories, default is blank. Multiple domains could be separated by commas. When `ALLOWED_DOMAINS` is not blank, this option has a higher priority to deny domains. Wildcard is supported.
1189
1187
- `ALLOW_LOCALNETWORKS`: **false**: Allow private addresses defined by RFC 1918, RFC 1122, RFC 4632 and RFC 4291. If a domain is allowed by `ALLOWED_DOMAINS`, this option will be ignored.
1190
1188
- `SKIP_TLS_VERIFY`: **false**: Allow skip tls verify
1191
1189
···
1364
1362
## Proxy (`proxy`)
1365
1363
1366
1364
- `PROXY_ENABLED`: **false**: Enable the proxy if true, all requests to external via HTTP will be affected, if false, no proxy will be used even environment http_proxy/https_proxy
1367
-
- `PROXY_URL`: **\<empty\>**: Proxy server URL, support http://, https//, socks://, blank will follow environment http_proxy/https_proxy
1368
-
- `PROXY_HOSTS`: **\<empty\>**: Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts.
1365
+
- `PROXY_URL`: **_empty_**: Proxy server URL, support http://, https//, socks://, blank will follow environment http_proxy/https_proxy
1366
+
- `PROXY_HOSTS`: **_empty_**: Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts.
1369
1367
1370
1368
i.e.
1371
1369
+8
-10
docs/content/doc/administration/config-cheat-sheet.zh-cn.md
docs/content/administration/config-cheat-sheet.zh-cn.md
+8
-10
docs/content/doc/administration/config-cheat-sheet.zh-cn.md
docs/content/administration/config-cheat-sheet.zh-cn.md
···
2
2
date: "2016-12-26T16:00:00+02:00"
3
3
title: "配置说明"
4
4
slug: "config-cheat-sheet"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "配置说明"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "config-cheat-sheet"
16
16
---
17
17
···
26
26
27
27
此文档的内容可能过于陈旧或者错误，请参考英文文档。
28
28
29
-
{{< toc >}}
30
-
31
29
## Overall (`DEFAULT`)
32
30
33
31
- `APP_NAME`: 应用名称，改成你希望的名字。
···
46
44
47
45
### Repository - Release (`repository.release`)
48
46
49
-
- `ALLOWED_TYPES`: **\<empty\>**: 允许扩展名的列表，用逗号分隔 (`.zip`), mime 类型 (`text/plain`) 或者匹配符号 (`image/*`, `audio/*`, `video/*`). 空值或者 `*/*` 允许所有类型。
47
+
- `ALLOWED_TYPES`: **_empty_**: 允许扩展名的列表，用逗号分隔 (`.zip`), mime 类型 (`text/plain`) 或者匹配符号 (`image/*`, `audio/*`, `video/*`). 空值或者 `*/*` 允许所有类型。
50
48
- `DEFAULT_PAGING_NUM`: **10**: 默认的发布版本页面分页。
51
49
52
50
## UI (`ui`)
···
187
185
- `ENABLED`: **true**: 是否启用。
188
186
- `ADAPTER`: **memory**: 缓存引擎，可以为 `memory`, `redis` 或 `memcache`。
189
187
- `INTERVAL`: **60**: 只对内存缓存有效，GC间隔，单位秒。
190
-
- `HOST`: **\<empty\>**: 针对redis和memcache有效，主机地址和端口。
188
+
- `HOST`: **_empty_**: 针对redis和memcache有效，主机地址和端口。
191
189
- Redis: `network=tcp,addr=127.0.0.1:6379,password=macaron,db=0,pool_size=100,idle_timeout=180`
192
190
- Memache: `127.0.0.1:9090;127.0.0.1:9091`
193
191
- `ITEM_TTL`: **16h**: 缓存项目失效时间，设置为 -1 则禁用缓存。
···
392
390
393
391
- `MAX_ATTEMPTS`: **3**: 在迁移过程中的 http/https 请求重试次数。
394
392
- `RETRY_BACKOFF`: **3**: 等待下一次重试的时间，单位秒。
395
-
- `ALLOWED_DOMAINS`: **\<empty\>**: 迁移仓库的域名白名单，默认为空，表示允许从任意域名迁移仓库，多个域名用逗号分隔。
396
-
- `BLOCKED_DOMAINS`: **\<empty\>**: 迁移仓库的域名黑名单，默认为空，多个域名用逗号分隔。如果 `ALLOWED_DOMAINS` 不为空，此选项有更高的优先级拒绝这里的域名。
393
+
- `ALLOWED_DOMAINS`: **_empty_**: 迁移仓库的域名白名单，默认为空，表示允许从任意域名迁移仓库，多个域名用逗号分隔。
394
+
- `BLOCKED_DOMAINS`: **_empty_**: 迁移仓库的域名黑名单，默认为空，多个域名用逗号分隔。如果 `ALLOWED_DOMAINS` 不为空，此选项有更高的优先级拒绝这里的域名。
397
395
- `ALLOW_LOCALNETWORKS`: **false**: Allow private addresses defined by RFC 1918
398
396
- `SKIP_TLS_VERIFY`: **false**: 允许忽略 TLS 认证
399
397
···
515
513
## Proxy (`proxy`)
516
514
517
515
- `PROXY_ENABLED`: **false**: 是否启用全局代理。如果为否，则不使用代理，环境变量中的代理也不使用
518
-
- `PROXY_URL`: **\<empty\>**: 代理服务器地址，支持 http://, https//, socks://，为空则不启用代理而使用环境变量中的 http_proxy/https_proxy
519
-
- `PROXY_HOSTS`: **\<empty\>**: 逗号分隔的多个需要代理的网址，支持 * 号匹配符号， ** 表示匹配所有网站
516
+
- `PROXY_URL`: **_empty_**: 代理服务器地址，支持 http://, https//, socks://，为空则不启用代理而使用环境变量中的 http_proxy/https_proxy
517
+
- `PROXY_HOSTS`: **_empty_**: 逗号分隔的多个需要代理的网址，支持 * 号匹配符号， ** 表示匹配所有网站
520
518
521
519
i.e.
522
520
+4
-8
docs/content/doc/administration/customizing-gitea.en-us.md
docs/content/administration/customizing-gitea.en-us.md
+4
-8
docs/content/doc/administration/customizing-gitea.en-us.md
docs/content/administration/customizing-gitea.en-us.md
···
2
2
date: "2017-04-15T14:56:00+02:00"
3
3
title: "Customizing Gitea"
4
4
slug: "customizing-gitea"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
12
12
parent: "administration"
13
13
name: "Customizing Gitea"
14
14
identifier: "customizing-gitea"
15
-
weight: 100
15
+
sidebar_position: 100
16
16
---
17
17
18
18
# Customizing Gitea
···
48
48
49
49
**Note:** Gitea must perform a full restart to see configuration changes.
50
50
51
-
**Table of Contents**
52
-
53
-
{{< toc >}}
54
-
55
51
## Serving custom public files
56
52
57
53
To make Gitea serve custom public files (like pages and images), use the folder
···
91
87
Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://golang.org/pkg/html/template/),
92
88
which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory.
93
89
94
-
To obtain any embedded file (including templates), the [`gitea embedded` tool]({{< relref "doc/administration/cmd-embedded.en-us.md" >}}) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using).
90
+
To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using).
95
91
96
92
Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and
97
93
shouldn't be touched without fully understanding these components.
···
320
316
321
317
`#hex-color label name ; label description`
322
318
323
-
For more information, see the [labels documentation]({{< relref "doc/usage/labels.en-us.md" >}}).
319
+
For more information, see the [labels documentation](usage/labels.md).
324
320
325
321
### Licenses
326
322
+2
-2
docs/content/doc/administration/customizing-gitea.zh-cn.md
docs/content/administration/customizing-gitea.zh-cn.md
+2
-2
docs/content/doc/administration/customizing-gitea.zh-cn.md
docs/content/administration/customizing-gitea.zh-cn.md
···
2
2
date: "2017-04-15T14:56:00+02:00"
3
3
title: "自定义 Gitea 配置"
4
4
slug: "customizing-gitea"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "自定义 Gitea 配置"
14
-
weight: 100
14
+
sidebar_position: 100
15
15
identifier: "customizing-gitea"
16
16
---
17
17
+3
-7
docs/content/doc/administration/email-setup.en-us.md
docs/content/administration/email-setup.en-us.md
+3
-7
docs/content/doc/administration/email-setup.en-us.md
docs/content/administration/email-setup.en-us.md
···
2
2
date: "2019-10-15T10:10:00+05:00"
3
3
title: "Email setup"
4
4
slug: "email-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Email setup"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "email-setup"
16
16
---
17
17
18
18
# Email setup
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea has mailer functionality for sending transactional emails (such as registration confirmation). It can be configured to either use Sendmail (or compatible MTAs like Postfix and msmtp) or directly use SMTP server.
25
21
···
60
56
61
57
To send a test email to validate the settings, go to Gitea > Site Administration > Configuration > SMTP Mailer Configuration.
62
58
63
-
For the full list of options check the [Config Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md" >}})
59
+
For the full list of options check the [Config Cheat Sheet](administration/config-cheat-sheet.md)
64
60
65
61
Please note: authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through:
66
62
+2
-6
docs/content/doc/administration/email-setup.zh-cn.md
docs/content/administration/email-setup.zh-cn.md
+2
-6
docs/content/doc/administration/email-setup.zh-cn.md
docs/content/administration/email-setup.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "Email 设置"
4
4
slug: "email-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Email 设置"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "email-setup"
16
16
---
17
17
18
18
# Email 设置
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea 具有邮件功能，用于发送事务性邮件（例如注册确认邮件）。它可以配置为使用 Sendmail（或兼容的 MTA，例如 Postfix 和 msmtp）或直接使用 SMTP 服务器。
25
21
+2
-6
docs/content/doc/administration/environment-variables.en-us.md
docs/content/administration/environment-variables.en-us.md
+2
-6
docs/content/doc/administration/environment-variables.en-us.md
docs/content/administration/environment-variables.en-us.md
···
2
2
date: "2017-04-08T11:34:00+02:00"
3
3
title: "Environment variables"
4
4
slug: "environment-variables"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Environment variables"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "environment-variables"
16
16
---
17
17
18
18
# Environment variables
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
This is an inventory of Gitea environment variables. They change Gitea behaviour.
25
21
+2
-2
docs/content/doc/administration/environment-variables.zh-cn.md
docs/content/administration/environment-variables.zh-cn.md
+2
-2
docs/content/doc/administration/environment-variables.zh-cn.md
docs/content/administration/environment-variables.zh-cn.md
···
2
2
date: "2017-04-08T11:34:00+02:00"
3
3
title: "环境变量清单"
4
4
slug: "environment-variables"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "环境变量清单"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "environment-variables"
16
16
---
17
17
+3
-7
docs/content/doc/administration/external-renderers.en-us.md
docs/content/administration/external-renderers.en-us.md
+3
-7
docs/content/doc/administration/external-renderers.en-us.md
docs/content/administration/external-renderers.en-us.md
···
2
2
date: "2018-11-23:00:00+02:00"
3
3
title: "External renderers"
4
4
slug: "external-renderers"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "External renderers"
14
-
weight: 60
14
+
sidebar_position: 60
15
15
identifier: "external-renderers"
16
16
---
17
17
18
18
# Custom files rendering configuration
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
Gitea supports custom file renderings (i.e., Jupyter notebooks, asciidoc, etc.) through external binaries,
25
21
it is just a matter of:
26
22
···
36
32
If you're using a Docker image, your `Dockerfile` should contain something along this lines:
37
33
38
34
```docker
39
-
FROM gitea/gitea:{{< version >}}
35
+
FROM gitea/gitea:@version@
40
36
[...]
41
37
42
38
COPY custom/app.ini /data/gitea/conf/app.ini
+4
-8
docs/content/doc/administration/external-renderers.zh-cn.md
docs/content/administration/external-renderers.zh-cn.md
+4
-8
docs/content/doc/administration/external-renderers.zh-cn.md
docs/content/administration/external-renderers.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "外部渲染器"
4
4
slug: "external-renderers"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "外部渲染器"
14
-
weight: 60
14
+
sidebar_position: 60
15
15
identifier: "external-renderers"
16
16
---
17
17
18
18
# 自定义文件渲染配置
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
Gitea 通过外部二进制文件支持自定义文件渲染（例如 Jupyter notebooks、asciidoc 等），只需要进行以下步骤：
25
21
26
22
- 安装外部二进制文件
27
23
- 在您的 `app.ini` 文件中添加一些配置
28
24
- 重新启动 Gitea 实例
29
25
30
-
此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置]({{< relref "doc/administration/customizing-gitea.zh-cn.md" >}}) 页面上的一些示例。
26
+
此功能支持整个文件的渲染。如果您想要在 Markdown 中渲染代码块，您需要使用 JavaScript 进行一些操作。请参阅 [自定义 Gitea 配置](administration/customizing-gitea.md) 页面上的一些示例。
31
27
32
28
## 安装外部二进制文件
33
29
···
35
31
如果您正在使用 Docker 镜像，则您的 `Dockerfile` 应该包含以下内容：
36
32
37
33
```docker
38
-
FROM gitea/gitea:{{< version >}}
34
+
FROM gitea/gitea:@version@
39
35
[...]
40
36
41
37
COPY custom/app.ini /data/gitea/conf/app.ini
+2
-2
docs/content/doc/administration/fail2ban-setup.en-us.md
docs/content/administration/fail2ban-setup.en-us.md
+2
-2
docs/content/doc/administration/fail2ban-setup.en-us.md
docs/content/administration/fail2ban-setup.en-us.md
···
2
2
date: "2018-05-11T11:00:00+02:00"
3
3
title: "Fail2ban Setup "
4
4
slug: "fail2ban-setup"
5
-
weight: 16
5
+
sidebar_position: 16
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Fail2ban setup"
14
-
weight: 16
14
+
sidebar_position: 16
15
15
identifier: "fail2ban-setup"
16
16
---
17
17
+2
-2
docs/content/doc/administration/fail2ban-setup.zh-cn.md
docs/content/administration/fail2ban-setup.zh-cn.md
+2
-2
docs/content/doc/administration/fail2ban-setup.zh-cn.md
docs/content/administration/fail2ban-setup.zh-cn.md
···
2
2
date: "2022-08-01T00:00:00+00:00"
3
3
title: "设置 Fail2ban"
4
4
slug: "fail2ban-setup"
5
-
weight: 16
5
+
sidebar_position: 16
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "设置 Fail2ban"
14
-
weight: 16
14
+
sidebar_position: 16
15
15
identifier: "fail2ban-setup"
16
16
---
17
17
+2
-2
docs/content/doc/administration/git-lfs-support.en-us.md
docs/content/administration/git-lfs-support.en-us.md
+2
-2
docs/content/doc/administration/git-lfs-support.en-us.md
docs/content/administration/git-lfs-support.en-us.md
···
2
2
date: "2019-10-06T08:00:00+05:00"
3
3
title: "Git LFS setup"
4
4
slug: "git-lfs-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Git LFS setup"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "git-lfs-setup"
16
16
---
17
17
+2
-2
docs/content/doc/administration/git-lfs-support.zh-cn.md
docs/content/administration/git-lfs-support.zh-cn.md
+2
-2
docs/content/doc/administration/git-lfs-support.zh-cn.md
docs/content/administration/git-lfs-support.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "Git LFS 设置"
4
4
slug: "git-lfs-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Git LFS 设置"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "git-lfs-setup"
16
16
---
17
17
+3
-7
docs/content/doc/administration/https-support.en-us.md
docs/content/administration/https-support.en-us.md
+3
-7
docs/content/doc/administration/https-support.en-us.md
docs/content/administration/https-support.en-us.md
···
2
2
date: "2018-06-02T11:00:00+02:00"
3
3
title: "HTTPS setup"
4
4
slug: "https-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "HTTPS setup"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "https-setup"
16
16
---
17
17
18
18
# HTTPS setup to encrypt connections to Gitea
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Using the built-in server
25
21
26
22
Before you enable HTTPS, make sure that you have valid SSL/TLS certificates.
27
23
You could use self-generated certificates for evaluation and testing. Please run `gitea cert --host [HOST]` to generate a self signed certificate.
28
24
29
-
If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide]({{< relref "doc/administration/reverse-proxies.en-us.md" >}}).
25
+
If you are using Apache or nginx on the server, it's recommended to check the [reverse proxy guide](administration/reverse-proxies.md).
30
26
31
27
To use Gitea's built-in HTTPS support, you must change your `app.ini` file:
32
28
+3
-7
docs/content/doc/administration/https-support.zh-cn.md
docs/content/administration/https-support.zh-cn.md
+3
-7
docs/content/doc/administration/https-support.zh-cn.md
docs/content/administration/https-support.zh-cn.md
···
2
2
date: "2023-04-09T11:00:00+02:00"
3
3
title: "HTTPS配置"
4
4
slug: "https-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
menu:
9
9
sidebar:
10
10
parent: "administration"
11
11
name: "HTTPS setup"
12
-
weight: 12
12
+
sidebar_position: 12
13
13
identifier: "https-setup"
14
14
---
15
15
16
16
# HTTPS setup to encrypt connections to Gitea
17
17
18
-
**Table of Contents**
19
-
20
-
{{< toc >}}
21
-
22
18
## 使用内置服务器
23
19
24
20
在启用HTTPS之前，确保您拥有有效的SSL/TLS证书。
25
21
建议在测试和评估情况下使用自签名证书，请运行 `gitea cert --host [HOST]` 以生成自签名证书
26
22
27
-
如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南]({{< relref "doc/administration/reverse-proxies.zh-cn.md" >}})。
23
+
如果您在服务器上使用阿帕奇（Apache）或Nginx，建议参考 [反向代理指南](administration/reverse-proxies.md)。
28
24
29
25
要使用Gitea内置HTTPS支持，您必须编辑`app.ini`文件。
30
26
+4
-8
docs/content/doc/administration/logging-config.en-us.md
docs/content/administration/logging-config.en-us.md
+4
-8
docs/content/doc/administration/logging-config.en-us.md
docs/content/administration/logging-config.en-us.md
···
2
2
date: "2019-04-02T17:06:00+01:00"
3
3
title: "Logging Configuration"
4
4
slug: "logging-config"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Logging Configuration"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "logging-config"
16
16
---
17
17
···
25
25
26
26
There is a fully functional log output by default, so it is not necessary to define one.
27
27
28
-
**Table of Contents**
29
-
30
-
{{< toc >}}
31
-
32
28
## Collecting Logs for Help
33
29
34
-
To collect logs for help and issue report, see [Support Options]({{< relref "doc/help/support.en-us.md" >}}).
30
+
To collect logs for help and issue report, see [Support Options](help/support.md).
35
31
36
32
## The `[log]` section
37
33
···
47
43
And it can contain the following sub-loggers:
48
44
49
45
- `logger.router.MODE`: (Default: **,**): List of log outputs to use for the Router logger.
50
-
- `logger.access.MODE`: (Default: **\<empty\>**) List of log outputs to use for the Access logger. By default, the access logger is disabled.
46
+
- `logger.access.MODE`: (Default: **_empty_**) List of log outputs to use for the Access logger. By default, the access logger is disabled.
51
47
- `logger.xorm.MODE`: (Default: **,**) List of log outputs to use for the XORM logger.
52
48
53
49
Setting a comma (`,`) to sub-logger's mode means making it use the default global `MODE`.
+4
-8
docs/content/doc/administration/logging-config.zh-cn.md
docs/content/administration/logging-config.zh-cn.md
+4
-8
docs/content/doc/administration/logging-config.zh-cn.md
docs/content/administration/logging-config.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "日志配置"
4
4
slug: "logging-config"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "日志配置"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "logging-config"
16
16
---
17
17
···
25
25
26
26
默认情况下，已经有一个完全功能的日志输出，因此不需要重新定义。
27
27
28
-
**目录**
29
-
30
-
{{< toc >}}
31
-
32
28
## 收集日志以获取帮助
33
29
34
-
要收集日志以获取帮助和报告问题，请参阅 [需要帮助]({{< relref "doc/help/support.zh-cn.md" >}})。
30
+
要收集日志以获取帮助和报告问题，请参阅 [需要帮助](help/support.md)。
35
31
36
32
## `[log]` 部分
37
33
···
47
43
它还可以包含以下子日志记录器：
48
44
49
45
- `logger.router.MODE`：（默认值：**,**）：用于路由器日志记录器的日志输出列表。
50
-
- `logger.access.MODE`：（默认值：**\<empty\>**）：用于访问日志记录器的日志输出列表。默认情况下，访问日志记录器被禁用。
46
+
- `logger.access.MODE`：（默认值：**_empty_**）：用于访问日志记录器的日志输出列表。默认情况下，访问日志记录器被禁用。
51
47
- `logger.xorm.MODE`：（默认值：**,**）：用于 XORM 日志记录器的日志输出列表。
52
48
53
49
将子日志记录器的模式设置为逗号（`,`）表示使用默认的全局 `MODE`。
+2
-6
docs/content/doc/administration/mail-templates.en-us.md
docs/content/administration/mail-templates.en-us.md
+2
-6
docs/content/doc/administration/mail-templates.en-us.md
docs/content/administration/mail-templates.en-us.md
···
2
2
date: "2019-10-23T17:00:00-03:00"
3
3
title: "Mail templates"
4
4
slug: "mail-templates"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Mail templates"
14
-
weight: 45
14
+
sidebar_position: 45
15
15
identifier: "mail-templates"
16
16
---
17
17
18
18
# Mail templates
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
To craft the e-mail subject and contents for certain operations, Gitea can be customized by using templates. The templates
25
21
for these functions are located under the [`custom` directory](https://docs.gitea.io/en-us/customizing-gitea/).
+2
-6
docs/content/doc/administration/mail-templates.zh-cn.md
docs/content/administration/mail-templates.zh-cn.md
+2
-6
docs/content/doc/administration/mail-templates.zh-cn.md
docs/content/administration/mail-templates.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "邮件模板"
4
4
slug: "mail-templates"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "邮件模板"
14
-
weight: 45
14
+
sidebar_position: 45
15
15
identifier: "mail-templates"
16
16
---
17
17
18
18
# 邮件模板
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
为了定制特定操作的电子邮件主题和内容，可以使用模板来自定义 Gitea。这些功能的模板位于 [`custom` 目录](https://docs.gitea.io/en-us/customizing-gitea/) 下。
25
21
如果没有自定义的替代方案，Gitea 将使用内部模板作为默认模板。
+2
-6
docs/content/doc/administration/repo-indexer.en-us.md
docs/content/administration/repo-indexer.en-us.md
+2
-6
docs/content/doc/administration/repo-indexer.en-us.md
docs/content/administration/repo-indexer.en-us.md
···
2
2
date: "2019-09-06T01:35:00-03:00"
3
3
title: "Repository indexer"
4
4
slug: "repo-indexer"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Repository indexer"
14
-
weight: 45
14
+
sidebar_position: 45
15
15
identifier: "repo-indexer"
16
16
---
17
17
18
18
# Repository indexer
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Setting up the repository indexer
25
21
+2
-6
docs/content/doc/administration/repo-indexer.zh-cn.md
docs/content/administration/repo-indexer.zh-cn.md
+2
-6
docs/content/doc/administration/repo-indexer.zh-cn.md
docs/content/administration/repo-indexer.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "仓库索引器"
4
4
slug: "repo-indexer"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "仓库索引器"
14
-
weight: 45
14
+
sidebar_position: 45
15
15
identifier: "repo-indexer"
16
16
---
17
17
18
18
# 仓库索引器
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 设置仓库索引器
25
21
+2
-6
docs/content/doc/administration/reverse-proxies.en-us.md
docs/content/administration/reverse-proxies.en-us.md
+2
-6
docs/content/doc/administration/reverse-proxies.en-us.md
docs/content/administration/reverse-proxies.en-us.md
···
2
2
date: "2018-05-22T11:00:00+00:00"
3
3
title: "Reverse Proxies"
4
4
slug: "reverse-proxies"
5
-
weight: 16
5
+
sidebar_position: 16
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Reverse Proxies"
14
-
weight: 16
14
+
sidebar_position: 16
15
15
identifier: "reverse-proxies"
16
16
---
17
17
18
18
# Reverse Proxies
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Nginx
25
21
+2
-6
docs/content/doc/administration/reverse-proxies.zh-cn.md
docs/content/administration/reverse-proxies.zh-cn.md
+2
-6
docs/content/doc/administration/reverse-proxies.zh-cn.md
docs/content/administration/reverse-proxies.zh-cn.md
···
2
2
date: "2018-05-22T11:00:00+00:00"
3
3
title: "反向代理"
4
4
slug: "reverse-proxies"
5
-
weight: 16
5
+
sidebar_position: 16
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "反向代理"
14
-
weight: 16
14
+
sidebar_position: 16
15
15
identifier: "reverse-proxies"
16
16
---
17
17
18
18
# 反向代理
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 使用 Nginx 作为反向代理服务
25
21
+3
-3
docs/content/doc/administration/search-engines-indexation.en-us.md
docs/content/administration/search-engines-indexation.en-us.md
+3
-3
docs/content/doc/administration/search-engines-indexation.en-us.md
docs/content/administration/search-engines-indexation.en-us.md
···
2
2
date: "2019-12-31T13:55:00+05:00"
3
3
title: "Search Engines Indexation"
4
4
slug: "search-engines-indexation"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "Search Engines Indexation"
14
-
weight: 60
14
+
sidebar_position: 60
15
15
identifier: "search-engines-indexation"
16
16
---
17
17
···
23
23
## Block search engines indexation using robots.txt
24
24
25
25
To make Gitea serve a custom `robots.txt` (default: empty 404) for top level installations,
26
-
create a file called `robots.txt` in the [`custom` folder or `CustomPath`]({{< relref "doc/administration/customizing-gitea.en-us.md" >}})
26
+
create a file called `robots.txt` in the [`custom` folder or `CustomPath`](administration/customizing-gitea.md)
27
27
28
28
Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt).
29
29
+3
-3
docs/content/doc/administration/search-engines-indexation.zh-cn.md
docs/content/administration/search-engines-indexation.zh-cn.md
+3
-3
docs/content/doc/administration/search-engines-indexation.zh-cn.md
docs/content/administration/search-engines-indexation.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "搜索引擎索引"
4
4
slug: "search-engines-indexation"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "搜索引擎索引"
14
-
weight: 60
14
+
sidebar_position: 60
15
15
identifier: "search-engines-indexation"
16
16
---
17
17
···
22
22
23
23
## 使用 robots.txt 阻止搜索引擎索引
24
24
25
-
为了使 Gitea 为顶级安装提供自定义的`robots.txt`（默认为空的 404），请在[`custom`文件夹或`CustomPath`]（{{< relref "doc/administration/customizing-gitea.zh-cn.md" >}}）中创建一个名为 `robots.txt` 的文件。
25
+
为了使 Gitea 为顶级安装提供自定义的`robots.txt`（默认为空的 404），请在[`custom`文件夹或`CustomPath`]（administration/customizing-gitea.md）中创建一个名为 `robots.txt` 的文件。
26
26
27
27
有关如何配置 `robots.txt` 的示例，请参考 [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt)。
28
28
+2
-6
docs/content/doc/administration/signing.en-us.md
docs/content/administration/signing.en-us.md
+2
-6
docs/content/doc/administration/signing.en-us.md
docs/content/administration/signing.en-us.md
···
2
2
date: "2019-08-17T10:20:00+01:00"
3
3
title: "GPG Commit Signatures"
4
4
slug: "signing"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "GPG Commit Signatures"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "signing"
16
16
---
17
17
18
18
# GPG Commit Signatures
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea will verify GPG commit signatures in the provided tree by
25
21
checking if the commits are signed by a key within the Gitea database,
+2
-6
docs/content/doc/administration/signing.zh-cn.md
docs/content/administration/signing.zh-cn.md
+2
-6
docs/content/doc/administration/signing.zh-cn.md
docs/content/administration/signing.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "GPG 提交签名"
4
4
slug: "signing"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "administration"
13
13
name: "GPG 提交签名"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "signing"
16
16
---
17
17
18
18
# GPG 提交签名
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea 将通过检查提交是否由 Gitea 数据库中的密钥签名，或者提交是否与 Git 的默认密钥匹配，来验证提供的树中的 GPG 提交签名。
25
21
+2
-2
docs/content/doc/contributing.en-us.md
docs/content/contributing.en-us.md
+2
-2
docs/content/doc/contributing.en-us.md
docs/content/contributing.en-us.md
+2
-2
docs/content/doc/contributing.fr-fr.md
docs/content/contributing.fr-fr.md
+2
-2
docs/content/doc/contributing.fr-fr.md
docs/content/contributing.fr-fr.md
+2
-2
docs/content/doc/contributing.zh-tw.md
docs/content/contributing.zh-tw.md
+2
-2
docs/content/doc/contributing.zh-tw.md
docs/content/contributing.zh-tw.md
docs/content/doc/contributing/_index.de-de.md
docs/content/contributing/_index.de-de.md
docs/content/doc/contributing/_index.de-de.md
docs/content/contributing/_index.de-de.md
docs/content/doc/contributing/_index.en-us.md
docs/content/contributing/_index.en-us.md
docs/content/doc/contributing/_index.en-us.md
docs/content/contributing/_index.en-us.md
docs/content/doc/contributing/_index.zh-cn.md
docs/content/contributing/_index.zh-cn.md
docs/content/doc/contributing/_index.zh-cn.md
docs/content/contributing/_index.zh-cn.md
docs/content/doc/contributing/_index.zh-tw.md
docs/content/contributing/_index.zh-tw.md
docs/content/doc/contributing/_index.zh-tw.md
docs/content/contributing/_index.zh-tw.md
+2
-6
docs/content/doc/contributing/guidelines-backend.en-us.md
docs/content/contributing/guidelines-backend.en-us.md
+2
-6
docs/content/doc/contributing/guidelines-backend.en-us.md
docs/content/contributing/guidelines-backend.en-us.md
···
2
2
date: "2021-11-01T23:41:00+08:00"
3
3
title: "Guidelines for Backend Development"
4
4
slug: "guidelines-backend"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "Guidelines for Backend"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "guidelines-backend"
16
16
---
17
17
18
18
# Guidelines for Backend Development
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Background
25
21
+2
-6
docs/content/doc/contributing/guidelines-backend.zh-cn.md
docs/content/contributing/guidelines-backend.zh-cn.md
+2
-6
docs/content/doc/contributing/guidelines-backend.zh-cn.md
docs/content/contributing/guidelines-backend.zh-cn.md
···
2
2
date: "2023-05-25T23:41:00+08:00"
3
3
title: "后端开发指南"
4
4
slug: "guidelines-backend"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "后端开发指南"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "guidelines-backend"
16
16
---
17
17
18
18
# 后端开发指南
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 背景
25
21
+2
-6
docs/content/doc/contributing/guidelines-frontend.en-us.md
docs/content/contributing/guidelines-frontend.en-us.md
+2
-6
docs/content/doc/contributing/guidelines-frontend.en-us.md
docs/content/contributing/guidelines-frontend.en-us.md
···
2
2
date: "2021-10-13T16:00:00+02:00"
3
3
title: "Guidelines for Frontend Development"
4
4
slug: "guidelines-frontend"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "Guidelines for Frontend"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "guidelines-frontend"
16
16
---
17
17
18
18
# Guidelines for Frontend Development
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Background
25
21
+2
-6
docs/content/doc/contributing/guidelines-frontend.zh-cn.md
docs/content/contributing/guidelines-frontend.zh-cn.md
+2
-6
docs/content/doc/contributing/guidelines-frontend.zh-cn.md
docs/content/contributing/guidelines-frontend.zh-cn.md
···
2
2
date: "2023-05-25T16:00:00+02:00"
3
3
title: "前端开发指南"
4
4
slug: "guidelines-frontend"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "前端开发指南"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "guidelines-frontend"
16
16
---
17
17
18
18
# 前端开发指南
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 背景
25
21
+2
-6
docs/content/doc/contributing/guidelines-refactoring.en-us.md
docs/content/contributing/guidelines-refactoring.en-us.md
+2
-6
docs/content/doc/contributing/guidelines-refactoring.en-us.md
docs/content/contributing/guidelines-refactoring.en-us.md
···
2
2
date: "2023-02-14T00:00:00+00:00"
3
3
title: "Guidelines for Refactoring"
4
4
slug: "guidelines-refactoring"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "Guidelines for Refactoring"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "guidelines-refactoring"
16
16
---
17
17
18
18
# Guidelines for Refactoring
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Background
25
21
+2
-6
docs/content/doc/contributing/guidelines-refactoring.zh-cn.md
docs/content/contributing/guidelines-refactoring.zh-cn.md
+2
-6
docs/content/doc/contributing/guidelines-refactoring.zh-cn.md
docs/content/contributing/guidelines-refactoring.zh-cn.md
···
2
2
date: "2023-05-25T00:00:00+00:00"
3
3
title: "重构指南"
4
4
slug: "guidelines-refactoring"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "重构指南"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "guidelines-refactoring"
16
16
---
17
17
18
18
# 重构指南
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 背景
25
21
+2
-2
docs/content/doc/contributing/localization.de-de.md
docs/content/contributing/localization.de-de.md
+2
-2
docs/content/doc/contributing/localization.de-de.md
docs/content/contributing/localization.de-de.md
···
2
2
date: "2021-01-22T00:00:00+02:00"
3
3
title: "Übersetzungs Richtlinien"
4
4
slug: "localization"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
menu:
9
9
sidebar:
10
10
parent: "contributing"
11
11
name: "Übersetzungsrichtlinien"
12
-
weight: 70
12
+
sidebar_position: 70
13
13
identifier: "localization"
14
14
---
15
15
+2
-2
docs/content/doc/contributing/localization.en-us.md
docs/content/contributing/localization.en-us.md
+2
-2
docs/content/doc/contributing/localization.en-us.md
docs/content/contributing/localization.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Localization"
4
4
slug: "localization"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "Localization"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "localization"
16
16
---
17
17
+2
-2
docs/content/doc/contributing/localization.zh-cn.md
docs/content/contributing/localization.zh-cn.md
+2
-2
docs/content/doc/contributing/localization.zh-cn.md
docs/content/contributing/localization.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "本地化"
4
4
slug: "localization"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "本地化"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "localization"
16
16
---
17
17
+2
-2
docs/content/doc/contributing/localization.zh-tw.md
docs/content/contributing/localization.zh-tw.md
+2
-2
docs/content/doc/contributing/localization.zh-tw.md
docs/content/contributing/localization.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "在地化"
4
4
slug: "localization"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "contributing"
13
13
name: "在地化"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "localization"
16
16
---
17
17
+2
-2
docs/content/doc/contributing/translation.zh-cn.md
docs/content/contributing/translation.zh-cn.md
+2
-2
docs/content/doc/contributing/translation.zh-cn.md
docs/content/contributing/translation.zh-cn.md
···
1
1
---
2
2
date: "2023-05-25T00:00:00+02:00"
3
3
title: "翻译指南"
4
-
weight: 70
4
+
sidebar_position: 70
5
5
toc: true
6
6
draft: false
7
7
menu:
8
8
sidebar:
9
9
parent: "contributing"
10
10
name: "翻译指南"
11
-
weight: 70
11
+
sidebar_position: 70
12
12
identifier: "translation-guidelines"
13
13
---
14
14
+2
-2
docs/content/doc/development.en-us.md
docs/content/development.en-us.md
+2
-2
docs/content/doc/development.en-us.md
docs/content/development.en-us.md
+2
-2
docs/content/doc/development.zh-cn.md
docs/content/development.zh-cn.md
+2
-2
docs/content/doc/development.zh-cn.md
docs/content/development.zh-cn.md
+2
-2
docs/content/doc/development.zh-tw.md
docs/content/development.zh-tw.md
+2
-2
docs/content/doc/development.zh-tw.md
docs/content/development.zh-tw.md
docs/content/doc/development/_index.en-us.md
docs/content/development/_index.en-us.md
docs/content/doc/development/_index.en-us.md
docs/content/development/_index.en-us.md
docs/content/doc/development/_index.zh-cn.md
docs/content/development/_index.zh-cn.md
docs/content/doc/development/_index.zh-cn.md
docs/content/development/_index.zh-cn.md
docs/content/doc/development/_index.zh-tw.md
docs/content/development/_index.zh-tw.md
docs/content/doc/development/_index.zh-tw.md
docs/content/development/_index.zh-tw.md
+2
-6
docs/content/doc/development/api-usage.en-us.md
docs/content/development/api-usage.en-us.md
+2
-6
docs/content/doc/development/api-usage.en-us.md
docs/content/development/api-usage.en-us.md
···
2
2
date: "2018-06-24:00:00+02:00"
3
3
title: "API Usage"
4
4
slug: "api-usage"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "API Usage"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "api-usage"
16
16
---
17
17
18
18
# API Usage
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Enabling/configuring API access
25
21
+2
-2
docs/content/doc/development/api-usage.zh-cn.md
docs/content/development/api-usage.zh-cn.md
+2
-2
docs/content/doc/development/api-usage.zh-cn.md
docs/content/development/api-usage.zh-cn.md
···
2
2
date: "2018-06-24:00:00+02:00"
3
3
title: "API 使用指南"
4
4
slug: "api-usage"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "API 使用指南"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "api-usage"
16
16
---
17
17
+9
-13
docs/content/doc/development/hacking-on-gitea.en-us.md
docs/content/development/hacking-on-gitea.en-us.md
+9
-13
docs/content/doc/development/hacking-on-gitea.en-us.md
docs/content/development/hacking-on-gitea.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Hacking on Gitea"
4
4
slug: "hacking-on-gitea"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "Hacking on Gitea"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "hacking-on-gitea"
16
16
---
17
17
18
18
# Hacking on Gitea
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Quickstart
25
21
26
22
To get a quick working development environment you could use Gitpod.
···
34
30
35
31
Next, [install Node.js with npm](https://nodejs.org/en/download/) which is
36
32
required to build the JavaScript and CSS files. The minimum supported Node.js
37
-
version is {{< min-node-version >}} and the latest LTS version is recommended.
33
+
version is @minNodeVersion@ and the latest LTS version is recommended.
38
34
39
35
**Note**: When executing make tasks that require external tools, like
40
36
`make watch-backend`, Gitea will automatically download and build these as
···
42
38
on the executable path. If you don't add the go bin directory to the
43
39
executable path you will have to manage this yourself.
44
40
45
-
**Note 2**: Go version {{< min-go-version >}} or higher is required.
41
+
**Note 2**: Go version @minGoVersion@ or higher is required.
46
42
Gitea uses `gofmt` to format source code. However, the results of
47
43
`gofmt` can differ by the version of `go`. Therefore it is
48
44
recommended to install the version of Go that our continuous integration is
49
-
running. As of last update, the Go version should be {{< go-version >}}.
45
+
running. As of last update, the Go version should be @goVersion@.
50
46
51
47
To lint the template files, ensure [Python](https://www.python.org/) and
52
48
[Poetry](https://python-poetry.org/) are installed.
···
126
122
## Building Gitea (Basic)
127
123
128
124
Take a look at our
129
-
[instructions]({{< relref "doc/installation/from-source.en-us.md" >}})
130
-
for [building from source]({{< relref "doc/installation/from-source.en-us.md" >}}).
125
+
[instructions](installation/from-source.md)
126
+
for [building from source](installation/from-source.md).
131
127
132
128
The simplest recommended way to build from source is:
133
129
···
181
177
182
178
### Working on JS and CSS
183
179
184
-
Frontend development should follow [Guidelines for Frontend Development]({{< relref "doc/contributing/guidelines-frontend.en-us.md" >}})
180
+
Frontend development should follow [Guidelines for Frontend Development](contributing/guidelines-frontend.md)
185
181
186
182
To build with frontend resources, either use the `watch-frontend` target mentioned above or just build once:
187
183
···
268
264
When creating new configuration options, it is not enough to add them to the
269
265
`modules/setting` files. You should add information to `custom/conf/app.ini`
270
266
and to the
271
-
[configuration cheat sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md" >}})
267
+
[configuration cheat sheet](administration/config-cheat-sheet.md)
272
268
found in `docs/content/doc/administer/config-cheat-sheet.en-us.md`
273
269
274
270
### Changing the logo
+9
-13
docs/content/doc/development/hacking-on-gitea.zh-cn.md
docs/content/development/hacking-on-gitea.zh-cn.md
+9
-13
docs/content/doc/development/hacking-on-gitea.zh-cn.md
docs/content/development/hacking-on-gitea.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "玩转 Gitea"
4
4
slug: "hacking-on-gitea"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "玩转 Gitea"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "hacking-on-gitea"
16
16
---
17
17
18
18
# Hacking on Gitea
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 快速入门
25
21
26
22
要获得快速工作的开发环境，您可以使用 Gitpod。
···
32
28
您需要 [安装 go]( https://golang.org/doc/install ) 并设置您的 go 环境。
33
29
34
30
接下来，[使用 npm 安装 Node.js](https://nodejs.org/en/download/) ，这是构建
35
-
JavaScript 和 CSS 文件的必要工具。最低支持的 Node.js 版本是 {{< min-node-version >}}
31
+
JavaScript 和 CSS 文件的必要工具。最低支持的 Node.js 版本是 @minNodeVersion@
36
32
并且推荐使用最新的 LTS 版本。
37
33
38
34
**注意** ：当执行需要外部工具的 make 任务时，比如
···
40
36
将 `"$GOPATH"/bin` 目录加入到可执行路径上。如果你不把go bin目录添加到可执行路径你必须手动
41
37
指定可执行程序路径。
42
38
43
-
**注意2** ：Go版本 {{< min-go-version >}} 或更高版本是必须的。Gitea 使用 `gofmt` 来
39
+
**注意2** ：Go版本 @minGoVersion@ 或更高版本是必须的。Gitea 使用 `gofmt` 来
44
40
格式化源代码。然而，`gofmt` 的结果可能因 `go` 的版本而有差异。因此推荐安装我们持续集成使用
45
-
的 Go版本。截至上次更新，Go 版本应该是 {{< go-version >}}。
41
+
的 Go版本。截至上次更新，Go 版本应该是 @goVersion@。
46
42
47
43
## 安装 Make
48
44
···
115
111
## 构建 Gitea（基本）
116
112
117
113
看看我们的
118
-
[说明]({{< relref "doc/installation/from-source.zh-cn.md" >}})
119
-
关于如何[从源代码构建]({{< relref "doc/installation/from-source.zh-cn.md" >}}) 。
114
+
[说明](installation/from-source.md)
115
+
关于如何[从源代码构建](installation/from-source.md) 。
120
116
121
117
从源代码构建的最简单推荐方法是：
122
118
···
168
164
169
165
### 处理 JS 和 CSS
170
166
171
-
前端开发应遵循 [Guidelines for Frontend Development]({{< relref "doc/contributing/guidelines-frontend.zh-cn.md" >}})。
167
+
前端开发应遵循 [Guidelines for Frontend Development](contributing/guidelines-frontend.md)。
172
168
173
169
要使用前端资源构建，请使用上面提到的“watch-frontend”目标或只构建一次：
174
170
···
249
245
### 创建新的配置选项
250
246
251
247
创建新的配置选项时，将它们添加到 `modules/setting` 的对应文件。您应该将信息添加到 `custom/conf/app.ini`
252
-
并到[配置备忘单]({{< relref "doc/administration/config-cheat-sheet.zh-cn.md" >}})
248
+
并到[配置备忘单](administration/config-cheat-sheet.md)
253
249
在 `docs/content/doc/advanced/config-cheat-sheet.zh-cn.md` 中找到
254
250
255
251
### 更改Logo
+2
-2
docs/content/doc/development/integrations.en-us.md
docs/content/development/integrations.en-us.md
+2
-2
docs/content/doc/development/integrations.en-us.md
docs/content/development/integrations.en-us.md
···
2
2
date: "2019-04-15T17:29:00+08:00"
3
3
title: "Integrations"
4
4
slug: "integrations"
5
-
weight: 65
5
+
sidebar_position: 65
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "Integrations"
14
-
weight: 65
14
+
sidebar_position: 65
15
15
identifier: "integrations"
16
16
---
17
17
+2
-2
docs/content/doc/development/integrations.zh-cn.md
docs/content/development/integrations.zh-cn.md
+2
-2
docs/content/doc/development/integrations.zh-cn.md
docs/content/development/integrations.zh-cn.md
···
2
2
date: "2023-05-25T17:29:00+08:00"
3
3
title: "集成"
4
4
slug: "integrations"
5
-
weight: 65
5
+
sidebar_position: 65
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "集成"
14
-
weight: 65
14
+
sidebar_position: 65
15
15
identifier: "integrations"
16
16
---
17
17
+2
-2
docs/content/doc/development/integrations.zh-tw.md
docs/content/development/integrations.zh-tw.md
+2
-2
docs/content/doc/development/integrations.zh-tw.md
docs/content/development/integrations.zh-tw.md
···
2
2
date: "2019-04-15T17:29:00+08:00"
3
3
title: "整合"
4
4
slug: "integrations"
5
-
weight: 65
5
+
sidebar_position: 65
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "整合"
14
-
weight: 65
14
+
sidebar_position: 65
15
15
identifier: "integrations"
16
16
---
17
17
+2
-2
docs/content/doc/development/migrations.en-us.md
docs/content/development/migrations.en-us.md
+2
-2
docs/content/doc/development/migrations.en-us.md
docs/content/development/migrations.en-us.md
···
2
2
date: "2019-04-15T17:29:00+08:00"
3
3
title: "Migrations Interfaces"
4
4
slug: "migrations-interfaces"
5
-
weight: 55
5
+
sidebar_position: 55
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "Migrations Interfaces"
14
-
weight: 55
14
+
sidebar_position: 55
15
15
identifier: "migrations-interfaces"
16
16
---
17
17
+2
-2
docs/content/doc/development/migrations.zh-cn.md
docs/content/development/migrations.zh-cn.md
+2
-2
docs/content/doc/development/migrations.zh-cn.md
docs/content/development/migrations.zh-cn.md
···
2
2
date: "2023-05-25T17:29:00+08:00"
3
3
title: "迁移界面"
4
4
slug: "migrations-interfaces"
5
-
weight: 55
5
+
sidebar_position: 55
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "迁移界面"
14
-
weight: 55
14
+
sidebar_position: 55
15
15
identifier: "migrations-interfaces"
16
16
---
17
17
+2
-2
docs/content/doc/development/migrations.zh-tw.md
docs/content/development/migrations.zh-tw.md
+2
-2
docs/content/doc/development/migrations.zh-tw.md
docs/content/development/migrations.zh-tw.md
···
2
2
date: "2019-04-15T17:29:00+08:00"
3
3
title: "遷移介面"
4
4
slug: "migrations-interfaces"
5
-
weight: 55
5
+
sidebar_position: 55
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "遷移介面"
14
-
weight: 55
14
+
sidebar_position: 55
15
15
identifier: "migrations-interfaces"
16
16
---
17
17
+2
-6
docs/content/doc/development/oauth2-provider.en-us.md
docs/content/development/oauth2-provider.en-us.md
+2
-6
docs/content/doc/development/oauth2-provider.en-us.md
docs/content/development/oauth2-provider.en-us.md
···
2
2
date: "2023-06-01T08:40:00+08:00"
3
3
title: "OAuth2 provider"
4
4
slug: "oauth2-provider"
5
-
weight: 41
5
+
sidebar_position: 41
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "OAuth2 Provider"
14
-
weight: 41
14
+
sidebar_position: 41
15
15
identifier: "oauth2-provider"
16
16
---
17
17
18
18
# OAuth2 provider
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea supports acting as an OAuth2 provider to allow third party applications to access its resources with the user's consent. This feature is available since release 1.8.0.
25
21
+2
-6
docs/content/doc/development/oauth2-provider.zh-cn.md
docs/content/development/oauth2-provider.zh-cn.md
+2
-6
docs/content/doc/development/oauth2-provider.zh-cn.md
docs/content/development/oauth2-provider.zh-cn.md
···
2
2
date: "2019-04-19:44:00+01:00"
3
3
title: "OAuth2 提供者"
4
4
slug: "oauth2-provider"
5
-
weight: 41
5
+
sidebar_position: 41
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "OAuth2 提供者"
14
-
weight: 41
14
+
sidebar_position: 41
15
15
identifier: "oauth2-provider"
16
16
---
17
17
18
18
# OAuth2 提供者
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea 支持作为 OAuth2 提供者，允许第三方应用程序在用户同意的情况下访问其资源。此功能自 1.8.0 版起可用。
25
21
+2
-4
docs/content/doc/development/oauth2-provider.zh-tw.md
docs/content/development/oauth2-provider.zh-tw.md
+2
-4
docs/content/doc/development/oauth2-provider.zh-tw.md
docs/content/development/oauth2-provider.zh-tw.md
···
2
2
date: "2019-04-19:44:00+01:00"
3
3
title: "OAuth2 提供者"
4
4
slug: "oauth2-provider"
5
-
weight: 41
5
+
sidebar_position: 41
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "development"
13
13
name: "OAuth2 提供者"
14
-
weight: 41
14
+
sidebar_position: 41
15
15
identifier: "oauth2-provider"
16
16
---
17
17
18
18
# OAuth2 提供者
19
19
20
20
**目錄**
21
-
22
-
{{< toc >}}
23
21
24
22
Gitea 支援作為 OAuth2 提供者，能讓第三方程式能在使用者同意下存取 Gitea 的資源。此功能自 1.8.0 版開始提供。
25
23
+2
-2
docs/content/doc/help.en-us.md
docs/content/help.en-us.md
+2
-2
docs/content/doc/help.en-us.md
docs/content/help.en-us.md
+2
-2
docs/content/doc/help.fr-fr.md
docs/content/help.fr-fr.md
+2
-2
docs/content/doc/help.fr-fr.md
docs/content/help.fr-fr.md
+2
-2
docs/content/doc/help.zh-cn.md
docs/content/help.zh-cn.md
+2
-2
docs/content/doc/help.zh-cn.md
docs/content/help.zh-cn.md
+2
-2
docs/content/doc/help.zh-tw.md
docs/content/help.zh-tw.md
+2
-2
docs/content/doc/help.zh-tw.md
docs/content/help.zh-tw.md
docs/content/doc/help/_index.en-us.md
docs/content/help/_index.en-us.md
docs/content/doc/help/_index.en-us.md
docs/content/help/_index.en-us.md
docs/content/doc/help/_index.zh-cn.md
docs/content/help/_index.zh-cn.md
docs/content/doc/help/_index.zh-cn.md
docs/content/help/_index.zh-cn.md
docs/content/doc/help/_index.zh-tw.md
docs/content/help/_index.zh-tw.md
docs/content/doc/help/_index.zh-tw.md
docs/content/help/_index.zh-tw.md
+19
-23
docs/content/doc/help/faq.en-us.md
docs/content/help/faq.en-us.md
+19
-23
docs/content/doc/help/faq.en-us.md
docs/content/help/faq.en-us.md
···
2
2
date: "2019-04-05T16:00:00+02:00"
3
3
title: "FAQ"
4
4
slug: "faq"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "help"
13
13
name: "FAQ"
14
-
weight: 5
14
+
sidebar_position: 5
15
15
identifier: "faq"
16
16
---
17
17
18
-
# Frequently Asked Questions <!-- omit in toc -->
18
+
# Frequently Asked Questions
19
19
20
20
This page contains some common questions and answers.
21
21
22
-
For more help resources, check all [Support Options]({{< relref "doc/help/support.en-us.md" >}}).
23
-
24
-
**Table of Contents**
25
-
26
-
{{< toc >}}
22
+
For more help resources, check all [Support Options](help/support.md).
27
23
28
24
## Difference between 1.x and 1.x.x downloads, how can I get latest stable release with bug fixes?
29
25
···
43
39
44
40
To migrate from Gogs to Gitea:
45
41
46
-
- [Gogs version 0.9.146 or less]({{< relref "doc/installation/upgrade-from-gogs.en-us.md" >}})
42
+
- [Gogs version 0.9.146 or less](installation/upgrade-from-gogs.md)
47
43
- [Gogs version 0.11.46.0418](https://github.com/go-gitea/gitea/issues/4286)
48
44
49
45
To migrate from GitHub to Gitea, you can use Gitea's built-in migration form.
···
91
87
92
88
There are a few places that could make this show incorrectly.
93
89
94
-
1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide]({{< relref "doc/administration/reverse-proxies.en-us.md" >}})
90
+
1. If using a reverse proxy, make sure you have followed the correction directions in the [reverse proxy guide](administration/reverse-proxies.md)
95
91
2. Make sure you have correctly set `ROOT_URL` in the `server` section of your `app.ini`
96
92
97
93
If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini`
···
104
100
105
101
This error occurs when the reverse proxy limits the file upload size.
106
102
107
-
See the [reverse proxy guide]({{< relref "doc/administration/reverse-proxies.en-us.md" >}}) for a solution with nginx.
103
+
See the [reverse proxy guide](administration/reverse-proxies.md) for a solution with nginx.
108
104
109
105
## Custom Templates not loading or working incorrectly
110
106
···
114
110
115
111
1. To find `CustomPath`, look for Custom File Root Path in Site Administration -> Configuration
116
112
2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file)
117
-
3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea]({{< relref "doc/administration/customizing-gitea.en-us.md" >}}) page to add your template to the correct location.
113
+
3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea](administration/customizing-gitea.md) page to add your template to the correct location.
118
114
119
115
## Does Gitea have a "GitHub/GitLab pages" feature?
120
116
···
132
128
133
129
## Setting up logging
134
130
135
-
- [Official Docs]({{< relref "doc/administration/logging-config.en-us.md" >}})
131
+
- [Official Docs](administration/logging-config.md)
136
132
137
133
## What is Swagger?
138
134
···
140
136
141
137
All Gitea instances have the built-in API and there is no way to disable it completely.
142
138
You can, however, disable showing its documentation by setting `ENABLE_SWAGGER` to `false` in the `api` section of your `app.ini`.
143
-
For more information, refer to Gitea's [API docs]({{< relref "doc/development/api-usage.en-us.md" >}}).
139
+
For more information, refer to Gitea's [API docs](development/api-usage.md).
144
140
145
141
You can see the latest API (for example) on <https://try.gitea.io/api/swagger>.
146
142
···
155
151
1. By whitelisting or blocklisting certain email domains
156
152
2. By only whitelisting certain domains with OpenID (see below)
157
153
3. Setting `ENABLE_CAPTCHA` to `true` in your `app.ini` and properly configuring `RECAPTCHA_SECRET` and `RECAPTCHA_SITEKEY`
158
-
4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI]({{< relref "doc/administration/command-line.en-us.md" >}}), [API]({{< relref "doc/development/api-usage.en-us.md" >}}), or Gitea's Admin UI
154
+
4. Settings `DISABLE_REGISTRATION` to `true` and creating new users via the [CLI](administration/command-line.md), [API](development/api-usage.md), or Gitea's Admin UI
159
155
160
156
### Only allow/block certain email domains
161
157
···
181
177
182
178
### Enable Fail2ban
183
179
184
-
Use [Fail2Ban]({{< relref "doc/administration/fail2ban-setup.en-us.md" >}}) to monitor and stop automated login attempts or other malicious behavior based on log patterns
180
+
Use [Fail2Ban](administration/fail2ban-setup.md) to monitor and stop automated login attempts or other malicious behavior based on log patterns
185
181
186
182
## How to add/use custom themes
187
183
···
334
330
335
331
## How can I create users before starting Gitea
336
332
337
-
Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands]({{< relref "doc/administration/command-line.en-us.md#admin" >}}) to add users like normal.
333
+
Gitea provides a sub-command `gitea migrate` to initialize the database, after which you can use the [admin CLI commands](administration/command-line.md#admin) to add users like normal.
338
334
339
335
## How can I enable password reset
340
336
341
-
There is no setting for password resets. It is enabled when a [mail service]({{< relref "doc/administration/email-setup.en-us.md" >}}) is configured, and disabled otherwise.
337
+
There is no setting for password resets. It is enabled when a [mail service](administration/email-setup.md) is configured, and disabled otherwise.
342
338
343
339
## How can a user's password be changed
344
340
345
341
- As an **admin**, you can change any user's password (and optionally force them to change it on next login)...
346
342
- By navigating to your `Site Administration -> User Accounts` page and editing a user.
347
-
- By using the [admin CLI commands]({{< relref "doc/administration/command-line.en-us.md#admin" >}}).
343
+
- By using the [admin CLI commands](administration/command-line.md#admin).
348
344
349
-
Keep in mind most commands will also need a [global flag]({{< relref "doc/administration/command-line.en-us.md#global-options" >}}) to point the CLI at the correct configuration.
345
+
Keep in mind most commands will also need a [global flag](administration/command-line.md#global-options) to point the CLI at the correct configuration.
350
346
- As a **user** you can change it...
351
347
- In your account `Settings -> Account` page (this method **requires** you to know your current password).
352
348
- By using the `Forgot Password` link.
353
349
354
-
If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service]({{< relref "doc/administration/email-setup.en-us.md" >}}).
350
+
If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service](administration/email-setup.md).
355
351
356
352
## Why is my markdown broken
357
353
···
447
443
- You can also check `<ROOT_URL>/admin/config` for the repository root path.
448
444
- Ensure that the user/org exists that you want to adopt repositories for.
449
445
- As an admin, go to `<ROOT_URL>/admin/repos/unadopted` and search.
450
-
- Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`]({{< relref "doc/administration/config-cheat-sheet.en-us.md#repository" >}}).
446
+
- Users can also be given similar permissions via config [`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository).
451
447
- If the above steps are done correctly, you should be able to select repositories to adopt.
452
-
- If no repositories are found, enable [debug logging]({{< relref "doc/administration/config-cheat-sheet.en-us.md#repository" >}}) to check for any specific errors.
448
+
- If no repositories are found, enable [debug logging](administration/config-cheat-sheet.md#repository) to check for any specific errors.
453
449
454
450
## Gitea can't start on NFS
455
451
+22
-26
docs/content/doc/help/faq.zh-cn.md
docs/content/help/faq.zh-cn.md
+22
-26
docs/content/doc/help/faq.zh-cn.md
docs/content/help/faq.zh-cn.md
···
2
2
date: "2023-05-25T16:00:00+02:00"
3
3
title: "常见问题"
4
4
slug: "faq"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "help"
13
13
name: "常见问题"
14
-
weight: 5
14
+
sidebar_position: 5
15
15
identifier: "faq"
16
16
---
17
17
18
-
# 常见问题 <!-- omit in toc -->
18
+
# 常见问题
19
19
20
20
本页面包含一些常见问题和答案。
21
21
22
-
有关更多帮助资源，请查看所有[支持选项]({{< relref "doc/help/support.zh-cn.md" >}})。
23
-
24
-
**目录**
25
-
26
-
{{< toc >}}
22
+
有关更多帮助资源，请查看所有[支持选项](help/support.md)。
27
23
28
24
## 1.x和1.x.x下载之间的区别
29
25
···
45
41
46
42
要从Gogs迁移到Gitea：
47
43
48
-
- [Gogs版本0.9.146或更低]({{< relref "doc/installation/upgrade-from-gogs.zh-cn.md" >}})
44
+
- [Gogs版本0.9.146或更低](installation/upgrade-from-gogs.md)
49
45
- [Gogs版本0.11.46.0418](https://github.com/go-gitea/gitea/issues/4286)
50
46
51
47
要从GitHub迁移到Gitea，您可以使用Gitea内置的迁移表单。
···
92
88
93
89
有几个地方可能会导致显示不正确。
94
90
95
-
1. 如果使用反向代理，请确保按照[反向代理指南]({{< relref "doc/administration/reverse-proxies.zh-cn.md" >}})中的正确说明进行设置。
91
+
1. 如果使用反向代理，请确保按照[反向代理指南](administration/reverse-proxies.md)中的正确说明进行设置。
96
92
2. 确保在`app.ini`的`server`部分中正确设置了`ROOT_URL`。
97
93
98
94
如果某些克隆选项未显示（HTTP/S或SSH），可以在`app.ini中`
···
105
101
106
102
当反向代理限制文件上传大小时，会出现此错误。
107
103
108
-
有关使用nginx解决此问题，请参阅[反向代理指南]({{< relref "doc/administration/reverse-proxies.zh-cn.md" >}})。
104
+
有关使用nginx解决此问题，请参阅[反向代理指南](administration/reverse-proxies.md)。
109
105
110
106
## 自定义模板无法加载或运行错误
111
107
···
117
113
118
114
如果找不到，请尝试`echo $GITEA_CUSTOM`。
119
115
120
-
2. 如果仍然找不到，默认值可以被[计算]({{< relref "doc/help/faq.zh-cn.md#where-does-gitea-store-what-file" >}})
121
-
3. 如果仍然找不到路径，则可以参考[自定义Gitea]({{< relref "doc/administration/customizing-gitea.zh-cn.md" >}})页面，将模板添加到正确的位置。
116
+
2. 如果仍然找不到，默认值可以被[计算](help/faq.md#where-does-gitea-store-what-file)
117
+
3. 如果仍然找不到路径，则可以参考[自定义Gitea](administration/customizing-gitea.md)页面，将模板添加到正确的位置。
122
118
123
119
## Gitea是否有"GitHub/GitLab Pages"功能？
124
120
···
136
132
137
133
## 设置日志记录
138
134
139
-
- [官方文档]({{< relref "doc/administration/logging-config.zh-cn.md" >}})
135
+
- [官方文档](administration/logging-config.md)
140
136
141
137
## 什么是Swagger？
142
138
···
144
140
145
141
所有Gitea实例都有内置的API，无法完全禁用它。
146
142
但是，您可以在app.ini的api部分将ENABLE_SWAGGER设置为false，以禁用其文档显示。
147
-
有关更多信息，请参阅Gitea的[API文档]({{< relref "doc/development/api-usage.zh-cn.md" >}})。
143
+
有关更多信息，请参阅Gitea的[API文档](development/api-usage.md)。
148
144
149
145
您可以在上查看最新的API（例如）<https://try.gitea.io/api/swagger>。
150
146
···
159
155
1. 通过设置电子邮件域名的白名单或黑名单。
160
156
2. 通过设置一些域名或者OpenID白名单（见下文）。
161
157
3. 在您的`app.ini`中将`ENABLE_CAPTCHA`设置为`true`，并正确配置`RECAPTCHA_SECRET`和 `RECAPTCHA_SITEKEY`。
162
-
4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI]({{< relref "doc/administration/command-line.zh-cn.md" >}})、[API]({{< relref "doc/development/api-usage.zh-cn.md" >}}) 或 Gitea 的管理界面创建新用户。
158
+
4. 将`DISABLE_REGISTRATION`设置为`true`，并通过 [CLI](administration/command-line.md)、[API](development/api-usage.md) 或 Gitea 的管理界面创建新用户。
163
159
164
160
### 仅允许/阻止特定的电子邮件域名
165
161
···
185
181
186
182
### 启用 Fail2ban
187
183
188
-
使用 [Fail2Ban]({{< relref "doc/administration/fail2ban-setup.zh-cn.md" >}}) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。
184
+
使用 [Fail2Ban](administration/fail2ban-setup.md) 监视并阻止基于日志模式的自动登录尝试或其他恶意行为。
189
185
190
186
## 如何添加/使用自定义主题
191
187
···
216
212
217
213
请确保Gitea具有足够的权限来写入其主目录和数据目录。
218
214
219
-
参见[AppDataPath 和 RepoRootPath]({{< relref "doc/help/faq.zh-cn.md#where-does-gitea-store-what-file" >}})
215
+
参见[AppDataPath 和 RepoRootPath](help/faq.md#where-does-gitea-store-what-file)
220
216
221
217
**适用于Arch用户的注意事项：**在撰写本文时，Arch软件包的systemd文件包含了以下行：
222
218
···
338
334
339
335
## 如何在启动 Gitea 之前创建用户
340
336
341
-
Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令]({{< relref "doc/administration/command-line.zh-cn.md#admin" >}})像正常情况下添加用户。
337
+
Gitea 提供了一个子命令`gitea migrate`来初始化数据库，然后您可以使用[管理 CLI 命令](administration/command-line.md#admin)像正常情况下添加用户。
342
338
343
339
## 如何启用密码重置
344
340
345
-
没有密码重置的设置。当配置了[邮件服务]({{< relref "doc/administration/email-setup.zh-cn.md" >}})时，密码重置将自动启用；否则将被禁用。
341
+
没有密码重置的设置。当配置了[邮件服务](administration/email-setup.md)时，密码重置将自动启用；否则将被禁用。
346
342
347
343
## 如何更改用户的密码
348
344
349
345
- 作为管理员，您可以更改任何用户的密码（并可选择强制其在下次登录时更改密码）...
350
346
- 转到您的`站点管理 -> 用户账户`页面并编辑用户。
351
-
- 使用[管理 CLI 命令]({{< relref "doc/administration/command-line.zh-cn.md#admin" >}})。
347
+
- 使用[管理 CLI 命令](administration/command-line.md#admin)。
352
348
353
-
请注意，大多数命令还需要一个[全局标志]({{< relref "doc/administration/command-line.zh-cn.- md#global-options" >}})来指向正确的配置。
349
+
请注意，大多数命令还需要一个[全局标志](administration/command-line.md#global-options)来指向正确的配置。
354
350
- 作为**用户**，您可以更改密码...
355
351
- 在您的账户的`设置 -> 账户`页面（此方法**需要**您知道当前密码）。
356
352
- 使用`忘记密码`链接。
357
353
358
-
如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务]({{< relref "doc/administration/email-setup.zh-cn.md" >}})。
354
+
如果`忘记密码/账户恢复`页面被禁用，请联系管理员配置[邮件服务](administration/email-setup.md)。
359
355
360
356
## 为什么我的 Markdown 显示错误
361
357
···
410
406
411
407
类似地，Docker 上的标准输出可以使用`docker logs <container>`来查看。
412
408
413
-
要收集日志以进行帮助和问题报告，请参阅[支持选项]({{< relref "doc/help/support.zh-cn.md" >}})。
409
+
要收集日志以进行帮助和问题报告，请参阅[支持选项](help/support.md)。
414
410
415
411
## 初始日志记录
416
412
···
467
463
- 您还可以在`<ROOT_URL>/admin/config`中检查存储库根路径。
468
464
- 确保存在要采用存储库的用户/组织。
469
465
- 作为管理员，转到`<ROOT_URL>/admin/repos/unadopted`并搜索。
470
-
- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`]({{< relref "doc/administration/config-cheat-sheet.zh-cn.md#repository" >}}) 获得类似的权限。
466
+
- 用户也可以通过配置[`ALLOW_ADOPTION_OF_UNADOPTED_REPOSITORIES`](administration/config-cheat-sheet.md#repository) 获得类似的权限。
471
467
- 如果上述步骤都正确执行，您应该能够选择要采用的存储库。
472
-
- 如果没有找到存储库，请启用[调试日志记录]({{< relref "doc/administration/config-cheat-sheet.zh-cn.md#repository" >}})以检查是否有特定错误。
468
+
- 如果没有找到存储库，请启用[调试日志记录](administration/config-cheat-sheet.md#repository)以检查是否有特定错误。
+2
-2
docs/content/doc/help/support.en-us.md
docs/content/help/support.en-us.md
+2
-2
docs/content/doc/help/support.en-us.md
docs/content/help/support.en-us.md
···
2
2
date: "2018-05-21T15:00:00+00:00"
3
3
title: "Support Options"
4
4
slug: "support"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "help"
13
13
name: "Support Options"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "support"
16
16
---
17
17
+2
-2
docs/content/doc/help/support.zh-cn.md
docs/content/help/support.zh-cn.md
+2
-2
docs/content/doc/help/support.zh-cn.md
docs/content/help/support.zh-cn.md
···
2
2
date: "2017-01-20T15:00:00+08:00"
3
3
title: "需要帮助"
4
4
slug: "support"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "help"
13
13
name: "需要帮助"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "support"
16
16
---
17
17
+2
-2
docs/content/doc/help/support.zh-tw.md
docs/content/help/support.zh-tw.md
+2
-2
docs/content/doc/help/support.zh-tw.md
docs/content/help/support.zh-tw.md
···
2
2
date: "2018-05-21T15:00:00+00:00"
3
3
title: "取得協助"
4
4
slug: "support"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "help"
13
13
name: "取得協助"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "support"
16
16
---
17
17
+2
-2
docs/content/doc/installation.en-us.md
docs/content/installation.en-us.md
+2
-2
docs/content/doc/installation.en-us.md
docs/content/installation.en-us.md
+2
-2
docs/content/doc/installation.fr-fr.md
docs/content/installation.fr-fr.md
+2
-2
docs/content/doc/installation.fr-fr.md
docs/content/installation.fr-fr.md
+2
-2
docs/content/doc/installation.zh-cn.md
docs/content/installation.zh-cn.md
+2
-2
docs/content/doc/installation.zh-cn.md
docs/content/installation.zh-cn.md
+2
-2
docs/content/doc/installation.zh-tw.md
docs/content/installation.zh-tw.md
+2
-2
docs/content/doc/installation.zh-tw.md
docs/content/installation.zh-tw.md
docs/content/doc/installation/_index.en-us.md
docs/content/installation/_index.en-us.md
docs/content/doc/installation/_index.en-us.md
docs/content/installation/_index.en-us.md
docs/content/doc/installation/_index.fr-fr.md
docs/content/installation/_index.fr-fr.md
docs/content/doc/installation/_index.fr-fr.md
docs/content/installation/_index.fr-fr.md
docs/content/doc/installation/_index.zh-cn.md
docs/content/installation/_index.zh-cn.md
docs/content/doc/installation/_index.zh-cn.md
docs/content/installation/_index.zh-cn.md
docs/content/doc/installation/_index.zh-tw.md
docs/content/installation/_index.zh-tw.md
docs/content/doc/installation/_index.zh-tw.md
docs/content/installation/_index.zh-tw.md
+2
-6
docs/content/doc/installation/comparison.en-us.md
docs/content/installation/comparison.en-us.md
+2
-6
docs/content/doc/installation/comparison.en-us.md
docs/content/installation/comparison.en-us.md
···
2
2
date: "2018-05-07T13:00:00+02:00"
3
3
title: "Compared to other Git hosting"
4
4
slug: "comparison"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
10
10
menu:
11
11
sidebar:
12
12
name: "Comparison"
13
-
weight: 5
13
+
sidebar_position: 5
14
14
parent: installation
15
15
identifier: "comparison"
16
16
---
17
17
18
18
# Gitea compared to other Git hosting options
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
To help decide if Gitea is suited for your needs, here is how it compares to other Git self hosted options.
25
21
+2
-2
docs/content/doc/installation/comparison.zh-cn.md
docs/content/installation/comparison.zh-cn.md
+2
-2
docs/content/doc/installation/comparison.zh-cn.md
docs/content/installation/comparison.zh-cn.md
···
2
2
date: "2019-02-14T11:51:04+08:00"
3
3
title: "对比 Gitea 与其它 Git 托管工具"
4
4
slug: "comparison"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "横向对比"
14
-
weight: 5
14
+
sidebar_position: 5
15
15
identifier: "comparison"
16
16
---
17
17
+2
-4
docs/content/doc/installation/comparison.zh-tw.md
docs/content/installation/comparison.zh-tw.md
+2
-4
docs/content/doc/installation/comparison.zh-tw.md
docs/content/installation/comparison.zh-tw.md
···
2
2
date: "2018-05-07T13:00:00+02:00"
3
3
title: "比較 Gitea 和其它自託管 Git 服務"
4
4
slug: "comparison"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "比較"
14
-
weight: 5
14
+
sidebar_position: 5
15
15
identifier: "comparison"
16
16
---
17
17
18
18
# 比較 Gitea 和其它自託管 Git 服務
19
19
20
20
**目錄**
21
-
22
-
{{< toc >}}
23
21
24
22
為了幫助您判斷 Gitea 是否適合您的需求，這裡列出了它和其它自託管 Git 服務的比較。
25
23
+2
-6
docs/content/doc/installation/database-preparation.en-us.md
docs/content/installation/database-preparation.en-us.md
+2
-6
docs/content/doc/installation/database-preparation.en-us.md
docs/content/installation/database-preparation.en-us.md
···
2
2
date: "2020-01-16"
3
3
title: "Database Preparation"
4
4
slug: "database-prep"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Database preparation"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "database-prep"
16
16
---
17
17
···
22
22
Database instance can be on same machine as Gitea (local database setup), or on different machine (remote database).
23
23
24
24
Note: All steps below requires that the database engine of your choice is installed on your system. For remote database setup, install the server application on database instance and client program on your Gitea server. The client program is used to test connection to the database from Gitea server, while Gitea itself use database driver provided by Go to accomplish the same thing. In addition, make sure you use same engine version for both server and client for some engine features to work. For security reason, protect `root` (MySQL) or `postgres` (PostgreSQL) database superuser with secure password. The steps assumes that you run Linux for both database and Gitea servers.
25
-
26
-
**Table of Contents**
27
-
28
-
{{< toc >}}
29
25
30
26
## MySQL
31
27
+2
-6
docs/content/doc/installation/database-preparation.zh-cn.md
docs/content/installation/database-preparation.zh-cn.md
+2
-6
docs/content/doc/installation/database-preparation.zh-cn.md
docs/content/installation/database-preparation.zh-cn.md
···
2
2
date: "2020-01-16"
3
3
title: "数据库准备"
4
4
slug: "database-prep"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "数据库准备"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "database-prep"
16
16
---
17
17
···
22
22
数据库实例可以与 Gitea 实例在相同机器上（本地数据库），也可以与 Gitea 实例在不同机器上（远程数据库）。
23
23
24
24
注意：以下所有步骤要求您的选择的数据库引擎已安装在您的系统上。对于远程数据库设置，请在数据库实例上安装服务器应用程序，在 Gitea 服务器上安装客户端程序。客户端程序用于测试 Gitea 服务器与数据库之间的连接，而 Gitea 本身使用 Go 提供的数据库驱动程序完成相同的任务。此外，请确保服务器和客户端使用相同的引擎版本，以使某些引擎功能正常工作。出于安全原因，请使用安全密码保护 `root`（MySQL）或 `postgres`（PostgreSQL）数据库超级用户。以下步骤假设您在数据库和 Gitea 服务器上都使用 Linux。
25
-
26
-
**目录**
27
-
28
-
{{< toc >}}
29
25
30
26
## MySQL
31
27
+10
-14
docs/content/doc/installation/from-binary.en-us.md
docs/content/installation/from-binary.en-us.md
+10
-14
docs/content/doc/installation/from-binary.en-us.md
docs/content/installation/from-binary.en-us.md
···
2
2
date: "2017-06-19T12:00:00+02:00"
3
3
title: "Installation from binary"
4
4
slug: "install-from-binary"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "From binary"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "install-from-binary"
16
16
---
17
17
···
20
20
All downloads come with SQLite, MySQL and PostgreSQL support, and are built with
21
21
embedded assets. This can be different from Gogs.
22
22
23
-
**Table of Contents**
24
-
25
-
{{< toc >}}
26
-
27
23
## Download
28
24
29
25
You can find the file matching your platform from the [downloads page](https://dl.gitea.com/gitea/) after navigating to the version you want to download.
···
45
41
Copy the commands below and replace the URL within the one you wish to download.
46
42
47
43
```sh
48
-
wget -O gitea https://dl.gitea.com/gitea/{{< version >}}/gitea-{{< version >}}-linux-amd64
44
+
wget -O gitea https://dl.gitea.com/gitea/@version@/gitea-@version@-linux-amd64
49
45
chmod +x gitea
50
46
```
51
47
52
-
Note that the above command will download Gitea {{< version >}} for 64-bit Linux.
48
+
Note that the above command will download Gitea @version@ for 64-bit Linux.
53
49
54
50
## Verify GPG signature
55
51
···
58
54
59
55
```sh
60
56
gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2
61
-
gpg --verify gitea-{{< version >}}-linux-amd64.asc gitea-{{< version >}}-linux-amd64
57
+
gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64
62
58
```
63
59
64
60
Look for the text `Good signature from "Teabot <teabot@gitea.io>"` to assert a good binary,
···
66
62
67
63
## Recommended server configuration
68
64
69
-
**NOTE:** Many of the following directories can be configured using [Environment Variables]({{< relref "doc/administration/environment-variables.en-us.md" >}}) as well!
65
+
**NOTE:** Many of the following directories can be configured using [Environment Variables](administration/environment-variables.md) as well!
70
66
Of note, configuring `GITEA_WORK_DIR` will tell Gitea where to base its working directory, as well as ease installation.
71
67
72
68
### Prepare environment
···
127
123
* Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.)
128
124
* Ensure that any other secret keys you need are set.
129
125
130
-
See the [command line documentation]({{< relref "doc/administration/command-line.en-us.md" >}}) for information on using `gitea generate secret`.
126
+
See the [command line documentation](administration/command-line.md) for information on using `gitea generate secret`.
131
127
132
128
### Configure Gitea's working directory
133
129
···
159
155
160
156
### 1. Creating a service file to start Gitea automatically (recommended)
161
157
162
-
See how to create [Linux service]({{< relref "doc/installation/run-as-service-in-ubuntu.en-us.md" >}})
158
+
See how to create [Linux service](installation/run-as-service-in-ubuntu.md)
163
159
164
160
### 2. Running from command-line/terminal
165
161
···
172
168
You can update to a new version of Gitea by stopping Gitea, replacing the binary at `/usr/local/bin/gitea` and restarting the instance.
173
169
The binary file name should not be changed during the update to avoid problems in existing repositories.
174
170
175
-
It is recommended that you make a [backup]({{< relref "doc/administration/backup-and-restore.en-us.md" >}}) before updating your installation.
171
+
It is recommended that you make a [backup](administration/backup-and-restore.md) before updating your installation.
176
172
177
173
If you have carried out the installation steps as described above, the binary should
178
174
have the generic name `gitea`. Do not change this, i.e. to include the version number.
···
200
196
Gitea binary, usually producing an error such as `./gitea: /lib/x86_64-linux-gnu/libc.so.6:
201
197
version 'GLIBC\_2.14' not found (required by ./gitea)`. This is due to the integrated
202
198
SQLite support in the binaries provided by dl.gitea.com. In this situation, it is usually
203
-
possible to [install from source]({{< relref "doc/installation/from-source.en-us.md" >}}), without including
199
+
possible to [install from source](installation/from-source.md), without including
204
200
SQLite support.
205
201
206
202
### Running Gitea on another port
+4
-4
docs/content/doc/installation/from-binary.fr-fr.md
docs/content/installation/from-binary.fr-fr.md
+4
-4
docs/content/doc/installation/from-binary.fr-fr.md
docs/content/installation/from-binary.fr-fr.md
···
2
2
date: "2017-08-23T09:00:00+02:00"
3
3
title: "Installation avec le binaire pré-compilé"
4
4
slug: "install-from-binary"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Binaire pré-compilé"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "install-from-binary"
16
16
---
17
17
···
20
20
Tous les binaires sont livrés avec le support de SQLite, MySQL et PostgreSQL, et sont construits avec les ressources incorporées. Gardez à l'esprit que cela peut être différent pour les versions antérieures. L'installation basée sur nos binaires est assez simple, il suffit de choisir le fichier correspondant à votre plateforme à partir de la [page de téléchargement](https://dl.gitea.com/gitea). Copiez l'URL et remplacer l'URL dans les commandes suivantes par la nouvelle:
21
21
22
22
```
23
-
wget -O gitea https://dl.gitea.com/gitea/{{< version >}}/gitea-{{< version >}}-linux-amd64
23
+
wget -O gitea https://dl.gitea.com/gitea/@version@/gitea-@version@-linux-amd64
24
24
chmod +x gitea
25
25
```
26
26
···
36
36
37
37
### Anciennes version de glibc
38
38
39
-
Les anciennes distributions Linux (comme Debian 7 ou CentOS 6) peuvent ne pas être capable d'exécuter le binaire Gitea, résultant généralement une erreur du type ```./gitea: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./gitea)```. Cette erreur est due au driver SQLite que nous intégrons dans le binaire Gitea. Dans le futur, nous fournirons des binaires sans la dépendance pour la bibliothèque glibc. En attendant, vous pouvez mettre à jour votre distribution ou installer Gitea depuis le [code source]({{< relref "doc/installation/from-source.fr-fr.md" >}}).
39
+
Les anciennes distributions Linux (comme Debian 7 ou CentOS 6) peuvent ne pas être capable d'exécuter le binaire Gitea, résultant généralement une erreur du type ```./gitea: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./gitea)```. Cette erreur est due au driver SQLite que nous intégrons dans le binaire Gitea. Dans le futur, nous fournirons des binaires sans la dépendance pour la bibliothèque glibc. En attendant, vous pouvez mettre à jour votre distribution ou installer Gitea depuis le [code source](installation/from-source.md).
40
40
41
41
### Exécuter Gitea avec un autre port
42
42
+8
-12
docs/content/doc/installation/from-binary.zh-cn.md
docs/content/installation/from-binary.zh-cn.md
+8
-12
docs/content/doc/installation/from-binary.zh-cn.md
docs/content/installation/from-binary.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "使用二进制文件安装"
4
4
slug: "install-from-binary"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "使用二进制文件安装"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "install-from-binary"
16
16
---
17
17
···
19
19
20
20
所有打包的二进制程序均包含 SQLite，MySQL 和 PostgreSQL 的数据库连接支持，同时网站的静态资源均已嵌入到可执行程序中，这一点和曾经的 Gogs 有所不同。
21
21
22
-
**目录**
23
-
24
-
{{< toc >}}
25
-
26
22
## 下载
27
23
28
24
你可以从 [下载页面](https://dl.gitea.com/gitea/) 选择对应平台的二进制文件。
···
42
38
使用以下命令下载适用于 64-bit Linux 平台的二进制文件。
43
39
44
40
```sh
45
-
wget -O gitea https://dl.gitea.com/gitea/{{< version >}}/gitea-{{< version >}}-linux-amd64
41
+
wget -O gitea https://dl.gitea.com/gitea/@version@/gitea-@version@-linux-amd64
46
42
chmod +x gitea
47
43
```
48
44
···
53
49
54
50
```sh
55
51
gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2
56
-
gpg --verify gitea-{{< version >}}-linux-amd64.asc gitea-{{< version >}}-linux-amd64
52
+
gpg --verify gitea-@version@-linux-amd64.asc gitea-@version@-linux-amd64
57
53
```
58
54
59
55
校验正确时的信息为 `Good signature from "Teabot <teabot@gitea.io>"`。
···
61
57
62
58
## 服务器设置
63
59
64
-
**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量]({{< relref "doc/administration/environment-variables.zh-cn.md" >}}) 初始化。
60
+
**提示：** `GITEA_WORK_DIR` 表示 Gitea 工作的路径。以下路径可以通过 [环境变量](administration/environment-variables.md) 初始化。
65
61
66
62
### 准备环境
67
63
···
143
139
144
140
### 1. 创建服务自动启动 Gitea（推荐）
145
141
146
-
学习创建 [Linux 服务]({{< relref "doc/installation/run-as-service-in-ubuntu.zh-cn.md" >}})
142
+
学习创建 [Linux 服务](installation/run-as-service-in-ubuntu.md)
147
143
148
144
### 2. 通过命令行终端运行
149
145
···
155
151
156
152
您可以通过停止程序，替换 `/usr/local/bin/gitea` 并重启来更新到新版本。直接替换可执行程序时不要更改或使用新的文件名称，以避免数据出错。
157
153
158
-
建议您在更新之前进行[备份]({{< relref "doc/administration/backup-and-restore.zh-cn.md" >}})。
154
+
建议您在更新之前进行[备份](administration/backup-and-restore.md)。
159
155
160
156
### 1. 使用 systemd 重新启动 Gitea（推荐）
161
157
···
175
171
176
172
> 更多经验总结，请参考英文版 [Troubleshooting](/en-us/install-from-binary/#troubleshooting)
177
173
178
-
如果从本页中没有找到你需要的内容，请访问 [帮助页面]({{< relref "doc/help/support.zh-cn.md" >}})
174
+
如果从本页中没有找到你需要的内容，请访问 [帮助页面](help/support.md)
+3
-3
docs/content/doc/installation/from-binary.zh-tw.md
docs/content/installation/from-binary.zh-tw.md
+3
-3
docs/content/doc/installation/from-binary.zh-tw.md
docs/content/installation/from-binary.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "執行檔安裝"
4
4
slug: "install-from-binary"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "執行檔"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "install-from-binary"
16
16
---
17
17
···
20
20
所有的執行檔皆支援 SQLite, MySQL and PostgreSQL，且所有檔案都已經包在執行檔內，這一點跟之前的版本有所不同。關於執行檔的安裝方式非常簡單，只要從[下載頁面](https://dl.gitea.com/gitea)選擇相對應平台，複製下載連結，使用底下指令就可以完成了:
21
21
22
22
```
23
-
wget -O gitea https://dl.gitea.com/gitea/{{< version >}}/gitea-{{< version >}}-linux-amd64
23
+
wget -O gitea https://dl.gitea.com/gitea/@version@/gitea-@version@-linux-amd64
24
24
chmod +x gitea
25
25
```
26
26
+4
-8
docs/content/doc/installation/from-package.en-us.md
docs/content/installation/from-package.en-us.md
+4
-8
docs/content/doc/installation/from-package.en-us.md
docs/content/installation/from-package.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Installation from package"
4
4
slug: "install-from-package"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "From package"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "install-from-package"
16
16
---
17
17
18
-
**Table of Contents**
19
-
20
-
{{< toc >}}
21
-
22
18
# Official packages
23
19
24
20
## macOS
25
21
26
22
Currently, the only supported method of installation on MacOS is [Homebrew](http://brew.sh/).
27
-
Following the [deployment from binary]({{< relref "doc/installation/from-binary.en-us.md" >}}) guide may work,
23
+
Following the [deployment from binary](installation/from-binary.md) guide may work,
28
24
but is not supported. To install Gitea via `brew`:
29
25
30
26
```
···
87
83
choco install gitea
88
84
```
89
85
90
-
Or follow the [deployment from binary]({{< relref "doc/installation/from-binary.en-us.md" >}}) guide.
86
+
Or follow the [deployment from binary](installation/from-binary.md) guide.
91
87
92
88
## FreeBSD
93
89
+5
-5
docs/content/doc/installation/from-package.fr-fr.md
docs/content/installation/from-package.fr-fr.md
+5
-5
docs/content/doc/installation/from-package.fr-fr.md
docs/content/installation/from-package.fr-fr.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Installation depuis le gestionnaire de paquets"
4
4
slug: "install-from-package"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Gestionnaire de paquets"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "install-from-package"
16
16
---
17
17
···
19
19
20
20
## Linux
21
21
22
-
Nous n'avons pas encore publié de paquet pour Linux, nous allons mettre à jour cette page directement lorsque nous commencerons à publier des paquets pour toutes distributions Linux. En attendant, vous devriez suivre les [instructions d'installation]({{< relref "doc/installation/from-binary.fr-fr.md" >}}) avec le binaire pré-compilé.
22
+
Nous n'avons pas encore publié de paquet pour Linux, nous allons mettre à jour cette page directement lorsque nous commencerons à publier des paquets pour toutes distributions Linux. En attendant, vous devriez suivre les [instructions d'installation](installation/from-binary.md) avec le binaire pré-compilé.
23
23
24
24
## Windows
25
25
26
-
Nous n'avons pas encore publié de paquet pour Windows, nous allons mettre à jour cette page directement lorsque nous commencerons à publier des paquets sous la forme de fichiers `MSI` ou via [Chocolatey](https://chocolatey.org/). En attendant, vous devriez suivre les [instructions d'installation]({{< relref "doc/installation/from-binary.fr-fr.md" >}}) avec le binaire pré-compilé.
26
+
Nous n'avons pas encore publié de paquet pour Windows, nous allons mettre à jour cette page directement lorsque nous commencerons à publier des paquets sous la forme de fichiers `MSI` ou via [Chocolatey](https://chocolatey.org/). En attendant, vous devriez suivre les [instructions d'installation](installation/from-binary.md) avec le binaire pré-compilé.
27
27
28
28
## macOS
29
29
30
-
Actuellement, nous ne supportons que l'installation via `brew` pour macOS. Si vous n'utilisez pas [Homebrew](http://brew.sh/), vous pouvez suivre les [instructions d'installation]({{< relref "doc/installation/from-binary.fr-fr.md" >}}) avec le binaire pré-compilé. Pour installer Gitea depuis `brew`, utilisez les commandes suivantes :
30
+
Actuellement, nous ne supportons que l'installation via `brew` pour macOS. Si vous n'utilisez pas [Homebrew](http://brew.sh/), vous pouvez suivre les [instructions d'installation](installation/from-binary.md) avec le binaire pré-compilé. Pour installer Gitea depuis `brew`, utilisez les commandes suivantes :
31
31
32
32
```
33
33
brew tap go-gitea/gitea
+4
-8
docs/content/doc/installation/from-package.zh-cn.md
docs/content/installation/from-package.zh-cn.md
+4
-8
docs/content/doc/installation/from-package.zh-cn.md
docs/content/installation/from-package.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "使用包管理器安装"
4
4
slug: "install-from-package"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "使用包管理器安装"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "install-from-package"
16
16
---
17
17
18
-
**目录**
19
-
20
-
{{< toc >}}
21
-
22
18
# 官方包管理器
23
19
24
20
## macOS
25
21
26
-
macOS 平台下当前我们仅支持通过 `brew` 来安装。如果你没有安装 [Homebrew](http://brew.sh/)，你也可以查看 [从二进制安装]({{< relref "doc/installation/from-binary.zh-cn.md" >}})。在你安装了 `brew` 之后， 你可以执行以下命令：
22
+
macOS 平台下当前我们仅支持通过 `brew` 来安装。如果你没有安装 [Homebrew](http://brew.sh/)，你也可以查看 [从二进制安装](installation/from-binary.md)。在你安装了 `brew` 之后， 你可以执行以下命令：
27
23
28
24
```
29
25
brew tap gitea/tap https://gitea.com/gitea/homebrew-gitea
···
77
73
choco install gitea
78
74
```
79
75
80
-
你也可以 [从二进制安装]({{< relref "doc/installation/from-binary.zh-cn.md" >}}) 。
76
+
你也可以 [从二进制安装](installation/from-binary.md) 。
81
77
82
78
## FreeBSD
83
79
+5
-5
docs/content/doc/installation/from-package.zh-tw.md
docs/content/installation/from-package.zh-tw.md
+5
-5
docs/content/doc/installation/from-package.zh-tw.md
docs/content/installation/from-package.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "套件安裝"
4
4
slug: "install-from-package"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "套件安裝"
14
-
weight: 20
14
+
sidebar_position: 20
15
15
identifier: "install-from-package"
16
16
---
17
17
···
19
19
20
20
## Linux
21
21
22
-
目前尚未發佈任何 Linux 套件，如果我們發佈了，會直接更新此網頁。在這之前請先參考[執行檔安裝]({{< relref "doc/installation/from-binary.zh-tw.md" >}})方式。
22
+
目前尚未發佈任何 Linux 套件，如果我們發佈了，會直接更新此網頁。在這之前請先參考[執行檔安裝](installation/from-binary.md)方式。
23
23
24
24
## Windows
25
25
···
29
29
choco install gitea
30
30
```
31
31
32
-
也可以參考[執行檔安裝]({{< relref "doc/installation/from-binary.zh-tw.md" >}})方式。
32
+
也可以參考[執行檔安裝](installation/from-binary.md)方式。
33
33
34
34
## macOS
35
35
36
-
目前我們只支援透過 `brew` 來安裝套件。假如您尚未使用 [Homebrew](http://brew.sh/)，您就必須參考[執行檔安裝]({{< relref "doc/installation/from-binary.zh-tw.md" >}})方式。透過 `brew` 安裝 Gitea，您只需要執行底下指令:
36
+
目前我們只支援透過 `brew` 來安裝套件。假如您尚未使用 [Homebrew](http://brew.sh/)，您就必須參考[執行檔安裝](installation/from-binary.md)方式。透過 `brew` 安裝 Gitea，您只需要執行底下指令:
37
37
38
38
```
39
39
brew tap go-gitea/gitea
+13
-17
docs/content/doc/installation/from-source.en-us.md
docs/content/installation/from-source.en-us.md
+13
-17
docs/content/doc/installation/from-source.en-us.md
docs/content/installation/from-source.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Installation from source"
4
4
slug: "install-from-source"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "From source"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "install-from-source"
16
16
---
17
17
···
25
25
26
26
Next, [install Node.js with npm](https://nodejs.org/en/download/) which is
27
27
required to build the JavaScript and CSS files. The minimum supported Node.js
28
-
version is {{< min-node-version >}} and the latest LTS version is recommended.
28
+
version is @minNodeVersion@ and the latest LTS version is recommended.
29
29
30
30
**Note**: When executing make tasks that require external tools, like
31
31
`make misspell-check`, Gitea will automatically download and build these as
···
33
33
on the executable path. If you don't add the go bin directory to the
34
34
executable path, you will have to manage this yourself.
35
35
36
-
**Note 2**: Go version {{< min-go-version >}} or higher is required. However, it is recommended to
36
+
**Note 2**: Go version @minGoVersion@ or higher is required. However, it is recommended to
37
37
obtain the same version as our continuous integration, see the advice given in
38
-
[Hacking on Gitea]({{< relref "doc/development/hacking-on-gitea.en-us.md" >}})
39
-
40
-
**Table of Contents**
41
-
42
-
{{< toc >}}
38
+
[Hacking on Gitea](development/hacking-on-gitea.md)
43
39
44
40
## Download
45
41
···
62
58
63
59
```bash
64
60
git branch -a
65
-
git checkout v{{< version >}}
61
+
git checkout v@version@
66
62
```
67
63
68
64
To validate a Pull Request, first enable the new branch (`xyz` is the PR id;
···
72
68
git fetch origin pull/xyz/head:pr-xyz
73
69
```
74
70
75
-
To build Gitea from source at a specific tagged release (like v{{< version >}}), list the
71
+
To build Gitea from source at a specific tagged release (like v@version@), list the
76
72
available tags and check out the specific tag.
77
73
78
74
List available tags with the following.
79
75
80
76
```bash
81
77
git tag -l
82
-
git checkout v{{< version >}} # or git checkout pr-xyz
78
+
git checkout v@version@ # or git checkout pr-xyz
83
79
```
84
80
85
81
## Build
86
82
87
83
To build from source, the following programs must be present on the system:
88
84
89
-
- `go` {{< min-go-version >}} or higher, see [here](https://golang.org/dl/)
90
-
- `node` {{< min-node-version >}} or higher with `npm`, see [here](https://nodejs.org/en/download/)
91
-
- `make`, see [here]({{< relref "doc/development/hacking-on-gitea.en-us.md" >}}#installing-make)
85
+
- `go` @minGoVersion@ or higher, see [here](https://golang.org/dl/)
86
+
- `node` @minNodeVersion@ or higher with `npm`, see [here](https://nodejs.org/en/download/)
87
+
- `make`, see [here](development/hacking-on-gitea.md#installing-make)
92
88
93
89
Various [make tasks](https://github.com/go-gitea/gitea/blob/main/Makefile)
94
90
are provided to keep the build process as simple as possible.
···
123
119
124
120
The `build` target is split into two sub-targets:
125
121
126
-
- `make backend` which requires [Go {{< min-go-version >}}](https://golang.org/dl/) or greater.
127
-
- `make frontend` which requires [Node.js {{< min-node-version >}}](https://nodejs.org/en/download/) or greater.
122
+
- `make backend` which requires [Go @minGoVersion@](https://golang.org/dl/) or greater.
123
+
- `make frontend` which requires [Node.js @minNodeVersion@](https://nodejs.org/en/download/) or greater.
128
124
129
125
If pre-built frontend files are present it is possible to only build the backend:
130
126
+5
-5
docs/content/doc/installation/from-source.fr-fr.md
docs/content/installation/from-source.fr-fr.md
+5
-5
docs/content/doc/installation/from-source.fr-fr.md
docs/content/installation/from-source.fr-fr.md
···
2
2
date: "2017-08-23T09:00:00+02:00"
3
3
title: "Installation depuis le code source"
4
4
slug: "install-from-source"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Code source"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "install-from-source"
16
16
---
17
17
···
36
36
37
37
```
38
38
git branch -a
39
-
git checkout v{{< version >}}
39
+
git checkout v@version@
40
40
```
41
41
42
42
Si vous souhaitez valider une demande d'ajout (_Pull request_), vous devez activer cette branche en premier :
···
45
45
git fetch origin pull/xyz/head:pr-xyz # xyz is PR value
46
46
```
47
47
48
-
Enfin, vous pouvez directement utiliser les versions étiquettées (ex : `v{{< version >}}`). Pour utiliser les étiquettes, vous devez lister les étiquettes disponibles et choisir une étiquette spécifique avec les commandes suivantes :
48
+
Enfin, vous pouvez directement utiliser les versions étiquettées (ex : `v@version@`). Pour utiliser les étiquettes, vous devez lister les étiquettes disponibles et choisir une étiquette spécifique avec les commandes suivantes :
49
49
50
50
```
51
51
git tag -l
52
-
git checkout v{{< version >}}
52
+
git checkout v@version@
53
53
git checkout pr-xyz
54
54
```
55
55
+7
-11
docs/content/doc/installation/from-source.zh-cn.md
docs/content/installation/from-source.zh-cn.md
+7
-11
docs/content/doc/installation/from-source.zh-cn.md
docs/content/installation/from-source.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "使用源代码安装"
4
4
slug: "install-from-source"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "使用源代码安装"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "install-from-source"
16
16
---
17
17
···
21
21
22
22
其次你需要[安装Node.js](https://nodejs.org/zh-cn/download/)，Node.js 和 npm 将用于构建 Gitea 前端。
23
23
24
-
**目录**
25
-
26
-
{{< toc >}}
27
-
28
24
## 下载
29
25
30
26
你需要获取Gitea的源码，最方便的方式是使用 `git` 命令。执行以下命令：
···
40
36
41
37
```bash
42
38
git branch -a
43
-
git checkout v{{< version >}}
39
+
git checkout v@version@
44
40
```
45
41
46
-
最后，你也可以直接使用标签版本如 `v{{< version >}}`。你可以执行以下命令列出可用的版本并选择某个版本签出：
42
+
最后，你也可以直接使用标签版本如 `v@version@`。你可以执行以下命令列出可用的版本并选择某个版本签出：
47
43
48
44
```bash
49
45
git tag -l
50
-
git checkout v{{< version >}}
46
+
git checkout v@version@
51
47
```
52
48
53
49
## 编译
54
50
55
51
要从源代码进行编译，以下依赖程序必须事先安装好：
56
52
57
-
- `go` {{< min-go-version >}} 或以上版本, 详见[这里](https://golang.google.cn/doc/install)
58
-
- `node` {{< min-node-version >}} 或以上版本，并且安装 `npm`, 详见[这里](https://nodejs.org/zh-cn/download/)
53
+
- `go` @minGoVersion@ 或以上版本, 详见[这里](https://golang.google.cn/doc/install)
54
+
- `node` @minNodeVersion@ 或以上版本，并且安装 `npm`, 详见[这里](https://nodejs.org/zh-cn/download/)
59
55
- `make`, 详见[这里](/zh-cn/hacking-on-gitea/)
60
56
61
57
各种可用的 [make 任务](https://github.com/go-gitea/gitea/blob/main/Makefile)
+5
-5
docs/content/doc/installation/from-source.zh-tw.md
docs/content/installation/from-source.zh-tw.md
+5
-5
docs/content/doc/installation/from-source.zh-tw.md
docs/content/installation/from-source.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "原始碼安裝"
4
4
slug: "install-from-source"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "原始碼安裝"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "install-from-source"
16
16
---
17
17
···
34
34
35
35
```
36
36
git branch -a
37
-
git checkout v{{< version >}}
37
+
git checkout v@version@
38
38
```
39
39
40
-
最後您也可以直接編譯最新的標籤版本像是 `v{{< version >}}`，假如您想要從原始碼編譯，這方法是最合適的，在編譯標籤版本前，您需要列出當下所有標籤，並且直接切換到標籤版本，請使用底下指令：:
40
+
最後您也可以直接編譯最新的標籤版本像是 `v@version@`，假如您想要從原始碼編譯，這方法是最合適的，在編譯標籤版本前，您需要列出當下所有標籤，並且直接切換到標籤版本，請使用底下指令：:
41
41
42
42
```
43
43
git tag -l
44
-
git checkout v{{< version >}}
44
+
git checkout v@version@
45
45
```
46
46
47
47
## 編譯
+2
-6
docs/content/doc/installation/on-cloud-provider.en-us.md
docs/content/installation/on-cloud-provider.en-us.md
+2
-6
docs/content/doc/installation/on-cloud-provider.en-us.md
docs/content/installation/on-cloud-provider.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Install on Cloud Provider"
4
4
slug: "install-on-cloud-provider"
5
-
weight: 90
5
+
sidebar_position: 90
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "On cloud provider"
14
-
weight: 90
14
+
sidebar_position: 90
15
15
identifier: "install-on-cloud-provider"
16
16
---
17
17
18
18
# Installation on Cloud Provider
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Cloudron
25
21
+2
-6
docs/content/doc/installation/on-cloud-provider.zh-cn.md
docs/content/installation/on-cloud-provider.zh-cn.md
+2
-6
docs/content/doc/installation/on-cloud-provider.zh-cn.md
docs/content/installation/on-cloud-provider.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "在云服务器中安装 Gitea"
4
4
slug: "install-on-cloud-provider"
5
-
weight: 90
5
+
sidebar_position: 90
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "在云服务器中安装 Gitea"
14
-
weight: 90
14
+
sidebar_position: 90
15
15
identifier: "install-on-cloud-provider"
16
16
---
17
17
18
18
# 在云服务器上安装 Gitea
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Cloudron
25
21
+2
-3
docs/content/doc/installation/on-kubernetes.en-us.md
docs/content/installation/on-kubernetes.en-us.md
+2
-3
docs/content/doc/installation/on-kubernetes.en-us.md
docs/content/installation/on-kubernetes.en-us.md
···
2
2
date: "2020-03-19T19:27:00+02:00"
3
3
title: "Install on Kubernetes"
4
4
slug: "install-on-kubernetes"
5
-
weight: 80
5
+
sidebar_position: 80
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Kubernetes"
14
-
weight: 80
14
+
sidebar_position: 80
15
15
identifier: "install-on-kubernetes"
16
16
---
17
17
···
48
48
49
49
```
50
50
HTTP/1.1 200 OK
51
-
52
51
53
52
{
54
53
"status": "pass",
+2
-3
docs/content/doc/installation/on-kubernetes.zh-cn.md
docs/content/installation/on-kubernetes.zh-cn.md
+2
-3
docs/content/doc/installation/on-kubernetes.zh-cn.md
docs/content/installation/on-kubernetes.zh-cn.md
···
2
2
date: "2020-03-19T19:27:00+02:00"
3
3
title: "在 Kubernetes 中安装 Gitea"
4
4
slug: "install-on-kubernetes"
5
-
weight: 80
5
+
sidebar_position: 80
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "在 Kubernetes 中安装 Gitea"
14
-
weight: 80
14
+
sidebar_position: 80
15
15
identifier: "install-on-kubernetes"
16
16
---
17
17
···
59
59
60
60
```
61
61
HTTP/1.1 200 OK
62
-
63
62
64
63
{
65
64
"status": "pass",
+2
-3
docs/content/doc/installation/on-kubernetes.zh-tw.md
docs/content/installation/on-kubernetes.zh-tw.md
+2
-3
docs/content/doc/installation/on-kubernetes.zh-tw.md
docs/content/installation/on-kubernetes.zh-tw.md
···
2
2
date: "2020-03-19T19:27:00+02:00"
3
3
title: "在 Kubernetes 安裝"
4
4
slug: "install-on-kubernetes"
5
-
weight: 80
5
+
sidebar_position: 80
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Kubernetes"
14
-
weight: 80
14
+
sidebar_position: 80
15
15
identifier: "install-on-kubernetes"
16
16
---
17
17
···
48
48
49
49
```
50
50
HTTP/1.1 200 OK
51
-
52
51
53
52
{
54
53
"status": "pass",
+2
-2
docs/content/doc/installation/run-as-service-in-ubuntu.en-us.md
docs/content/installation/run-as-service-in-ubuntu.en-us.md
+2
-2
docs/content/doc/installation/run-as-service-in-ubuntu.en-us.md
docs/content/installation/run-as-service-in-ubuntu.en-us.md
···
2
2
date: "2017-07-21T12:00:00+02:00"
3
3
title: "Run as service in Linux"
4
4
slug: "linux-service"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Linux service"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "linux-service"
16
16
---
17
17
+2
-2
docs/content/doc/installation/run-as-service-in-ubuntu.zh-cn.md
docs/content/installation/run-as-service-in-ubuntu.zh-cn.md
+2
-2
docs/content/doc/installation/run-as-service-in-ubuntu.zh-cn.md
docs/content/installation/run-as-service-in-ubuntu.zh-cn.md
···
2
2
date: "2017-07-21T12:00:00+02:00"
3
3
title: "在 Linux 中以 service 方式运行"
4
4
slug: "linux-service"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "在Linux中以service方式运行"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "linux-service"
16
16
---
17
17
+2
-2
docs/content/doc/installation/run-as-service-in-ubuntu.zh-tw.md
docs/content/installation/run-as-service-in-ubuntu.zh-tw.md
+2
-2
docs/content/doc/installation/run-as-service-in-ubuntu.zh-tw.md
docs/content/installation/run-as-service-in-ubuntu.zh-tw.md
···
2
2
date: "2017-07-21T12:00:00+02:00"
3
3
title: "在 Linux 中以服務執行"
4
4
slug: "linux-service"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Linux 服務"
14
-
weight: 40
14
+
sidebar_position: 40
15
15
identifier: "linux-service"
16
16
---
17
17
+2
-6
docs/content/doc/installation/upgrade-from-gitea.en-us.md
docs/content/installation/upgrade-from-gitea.en-us.md
+2
-6
docs/content/doc/installation/upgrade-from-gitea.en-us.md
docs/content/installation/upgrade-from-gitea.en-us.md
···
2
2
date: "2021-09-02T16:00:00+08:00"
3
3
title: "Upgrade from an old Gitea"
4
4
slug: "upgrade-from-gitea"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Upgrade From Old Gitea"
14
-
weight: 100
14
+
sidebar_position: 100
15
15
identifier: "upgrade-from-gitea"
16
16
---
17
17
18
18
# Upgrade from an old Gitea
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
To update Gitea, download a newer version, stop the old one, perform a backup, and run the new one.
25
21
Every time a Gitea instance starts up, it checks whether a database migration should be run.
+2
-6
docs/content/doc/installation/upgrade-from-gitea.zh-cn.md
docs/content/installation/upgrade-from-gitea.zh-cn.md
+2
-6
docs/content/doc/installation/upgrade-from-gitea.zh-cn.md
docs/content/installation/upgrade-from-gitea.zh-cn.md
···
2
2
date: "2021-09-02T16:00:00+08:00"
3
3
title: "从旧版 Gitea 升级"
4
4
slug: "upgrade-from-gitea"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
toc: false
7
7
draft: false
8
8
menu:
9
9
sidebar:
10
10
parent: "installation"
11
11
name: "从旧版 Gitea 升级"
12
-
weight: 100
12
+
sidebar_position: 100
13
13
identifier: "upgrade-from-gitea"
14
14
---
15
15
16
16
# 从旧版 Gitea 升级
17
-
18
-
**目录**
19
-
20
-
{{< toc >}}
21
17
22
18
想要升级 Gitea，只需要下载新版，停止运行旧版，进行数据备份，然后运行新版就好。
23
19
每次 Gitea 实例启动时，它都会检查是否要进行数据库迁移。
+3
-7
docs/content/doc/installation/upgrade-from-gogs.en-us.md
docs/content/installation/upgrade-from-gogs.en-us.md
+3
-7
docs/content/doc/installation/upgrade-from-gogs.en-us.md
docs/content/installation/upgrade-from-gogs.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Upgrade from Gogs"
4
4
slug: "upgrade-from-gogs"
5
-
weight: 101
5
+
sidebar_position: 101
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Upgrade From Gogs"
14
-
weight: 101
14
+
sidebar_position: 101
15
15
identifier: "upgrade-from-gogs"
16
16
---
17
17
18
18
# Upgrade from Gogs
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Gogs, version 0.9.146 and older, can be easily migrated to Gitea.
25
21
···
83
79
the destination platform from the [downloads page](https://dl.gitea.com/gitea/1.6.4/) and replace the binary.
84
80
Run Gitea at least once and check that everything works as expected.
85
81
86
-
Then repeat the procedure, but this time using the [latest release](https://dl.gitea.com/gitea/{{< version >}}/).
82
+
Then repeat the procedure, but this time using the [latest release](https://dl.gitea.com/gitea/@version@/).
87
83
88
84
## Upgrading from a more recent version of Gogs
89
85
+2
-2
docs/content/doc/installation/upgrade-from-gogs.fr-fr.md
docs/content/installation/upgrade-from-gogs.fr-fr.md
+2
-2
docs/content/doc/installation/upgrade-from-gogs.fr-fr.md
docs/content/installation/upgrade-from-gogs.fr-fr.md
···
2
2
date: "2017-08-23T09:00:00+02:00"
3
3
title: "Mise à jour depuis Gogs"
4
4
slug: "upgrade-from-gogs"
5
-
weight: 101
5
+
sidebar_position: 101
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Depuis Gogs"
14
-
weight: 101
14
+
sidebar_position: 101
15
15
identifier: "upgrade-from-gogs"
16
16
---
17
17
+2
-2
docs/content/doc/installation/upgrade-from-gogs.zh-cn.md
docs/content/installation/upgrade-from-gogs.zh-cn.md
+2
-2
docs/content/doc/installation/upgrade-from-gogs.zh-cn.md
docs/content/installation/upgrade-from-gogs.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "从 Gogs 升级"
4
4
slug: "upgrade-from-gogs"
5
-
weight: 101
5
+
sidebar_position: 101
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "从 Gogs 升级"
14
-
weight: 101
14
+
sidebar_position: 101
15
15
identifier: "upgrade-from-gogs"
16
16
---
17
17
+3
-5
docs/content/doc/installation/upgrade-from-gogs.zh-tw.md
docs/content/installation/upgrade-from-gogs.zh-tw.md
+3
-5
docs/content/doc/installation/upgrade-from-gogs.zh-tw.md
docs/content/installation/upgrade-from-gogs.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "從 Gogs 升級"
4
4
slug: "upgrade-from-gogs"
5
-
weight: 101
5
+
sidebar_position: 101
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "從 Gogs 升級"
14
-
weight: 101
14
+
sidebar_position: 101
15
15
identifier: "upgrade-from-gogs"
16
16
---
17
17
18
18
# 從 Gogs 升級
19
19
20
20
**目錄**
21
-
22
-
{{< toc >}}
23
21
24
22
若您正在執行 Gogs 0.9.146 以下版本，您可以很簡單地遷移到 Gitea。
25
23
···
80
78
請先升級到 [`gitea 1.6.4`](https://dl.gitea.com/gitea/1.6.4/)，先從[下載頁](https://dl.gitea.com/gitea/1.6.4/)下載
81
79
您平臺的二進位檔取代既有的。至少執行一次 Gitea 並確認一切符合預期。
82
80
83
-
接著重複上述步驟，但這次請使用[最新發行版本](https://dl.gitea.com/gitea/{{< version >}}/)。
81
+
接著重複上述步驟，但這次請使用[最新發行版本](https://dl.gitea.com/gitea/@version@/)。
84
82
85
83
## 從更新版本的 Gogs 升級
86
84
+2
-2
docs/content/doc/installation/windows-service.en-us.md
docs/content/installation/windows-service.en-us.md
+2
-2
docs/content/doc/installation/windows-service.en-us.md
docs/content/installation/windows-service.en-us.md
···
2
2
date: "2016-12-21T15:00:00-02:00"
3
3
title: "Register as a Windows Service"
4
4
slug: "windows-service"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Windows Service"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "windows-service"
16
16
---
17
17
+2
-2
docs/content/doc/installation/windows-service.fr-fr.md
docs/content/installation/windows-service.fr-fr.md
+2
-2
docs/content/doc/installation/windows-service.fr-fr.md
docs/content/installation/windows-service.fr-fr.md
···
2
2
date: "2017-08-23T09:00:00+02:00"
3
3
title: "Démarrer en tant que service Windows"
4
4
slug: "windows-service"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Service Windows"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "windows-service"
16
16
---
17
17
+2
-2
docs/content/doc/installation/windows-service.zh-cn.md
docs/content/installation/windows-service.zh-cn.md
+2
-2
docs/content/doc/installation/windows-service.zh-cn.md
docs/content/installation/windows-service.zh-cn.md
···
2
2
date: "2016-12-21T15:00:00-02:00"
3
3
title: "注册为Windows服务"
4
4
slug: "windows-service"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Windows服务"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "windows-service"
16
16
---
17
17
+2
-2
docs/content/doc/installation/windows-service.zh-tw.md
docs/content/installation/windows-service.zh-tw.md
+2
-2
docs/content/doc/installation/windows-service.zh-tw.md
docs/content/installation/windows-service.zh-tw.md
···
2
2
date: "2016-12-21T15:00:00-02:00"
3
3
title: "註冊為 Windows 服務"
4
4
slug: "windows-service"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Windows 服務"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "windows-service"
16
16
---
17
17
+10
-10
docs/content/doc/installation/with-docker-rootless.en-us.md
docs/content/installation/with-docker-rootless.en-us.md
+10
-10
docs/content/doc/installation/with-docker-rootless.en-us.md
docs/content/installation/with-docker-rootless.en-us.md
···
2
2
date: "2020-02-09T20:00:00+02:00"
3
3
title: "Installation with Docker (rootless)"
4
4
slug: "install-with-docker-rootless"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "With Docker Rootless"
14
-
weight: 60
14
+
sidebar_position: 60
15
15
identifier: "install-with-docker-rootless"
16
16
---
17
17
···
47
47
48
48
services:
49
49
server:
50
-
image: gitea/gitea:{{< version >}}-rootless
50
+
image: gitea/gitea:@version@-rootless
51
51
restart: always
52
52
volumes:
53
53
- ./data:/var/lib/gitea
···
67
67
68
68
> If you don't give the volume correct permissions, the container may not start.
69
69
70
-
For a stable release you could use `:latest-rootless`, `:1-rootless` or specify a certain release like `:{{< version >}}-rootless`, but if you'd like to use the latest development version then `:nightly-rootless` would be an appropriate tag. If you'd like to run the latest commit from a release branch you can use the `:1.x-nightly-rootless` tag, where x is the minor version of Gitea. (e.g. `:1.16-nightly-rootless`)
70
+
For a stable release you could use `:latest-rootless`, `:1-rootless` or specify a certain release like `:@version@-rootless`, but if you'd like to use the latest development version then `:nightly-rootless` would be an appropriate tag. If you'd like to run the latest commit from a release branch you can use the `:1.x-nightly-rootless` tag, where x is the minor version of Gitea. (e.g. `:1.16-nightly-rootless`)
71
71
72
72
## Custom port
73
73
···
80
80
81
81
services:
82
82
server:
83
-
image: gitea/gitea:{{< version >}}-rootless
83
+
image: gitea/gitea:@version@-rootless
84
84
restart: always
85
85
volumes:
86
86
- ./data:/var/lib/gitea
···
104
104
105
105
services:
106
106
server:
107
-
image: gitea/gitea:{{< version >}}-rootless
107
+
image: gitea/gitea:@version@-rootless
108
108
+ environment:
109
109
+ - GITEA__database__DB_TYPE=mysql
110
110
+ - GITEA__database__HOST=db:3306
···
145
145
146
146
services:
147
147
server:
148
-
image: gitea/gitea:{{< version >}}-rootless
148
+
image: gitea/gitea:@version@-rootless
149
149
environment:
150
150
+ - GITEA__database__DB_TYPE=postgres
151
151
+ - GITEA__database__HOST=db:5432
···
193
193
+
194
194
services:
195
195
server:
196
-
image: gitea/gitea:{{< version >}}-rootless
196
+
image: gitea/gitea:@version@-rootless
197
197
restart: always
198
198
volumes:
199
199
- - ./data:/var/lib/gitea
···
220
220
221
221
services:
222
222
server:
223
-
image: gitea/gitea:{{< version >}}-rootless
223
+
image: gitea/gitea:@version@-rootless
224
224
restart: always
225
225
+ user: 1001
226
226
volumes:
···
282
282
- Rename folder (inside volume) gitea to custom
283
283
- Edit app.ini if needed
284
284
- Set START_SSH_SERVER = true
285
-
- Use image gitea/gitea:{{< version >}}-rootless
285
+
- Use image gitea/gitea:@version@-rootless
286
286
287
287
## Managing Deployments With Environment Variables
288
288
+10
-10
docs/content/doc/installation/with-docker-rootless.zh-cn.md
docs/content/installation/with-docker-rootless.zh-cn.md
+10
-10
docs/content/doc/installation/with-docker-rootless.zh-cn.md
docs/content/installation/with-docker-rootless.zh-cn.md
···
2
2
date: "2020-02-09T20:00:00+02:00"
3
3
title: "使用 Docker 安装 (rootless)"
4
4
slug: "install-with-docker-rootless"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "使用 Docker 安装 (rootless)"
14
-
weight: 60
14
+
sidebar_position: 60
15
15
identifier: "install-with-docker-rootless"
16
16
---
17
17
···
42
42
43
43
services:
44
44
server:
45
-
image: gitea/gitea:{{< version >}}-rootless
45
+
image: gitea/gitea:@version@-rootless
46
46
restart: always
47
47
volumes:
48
48
- ./data:/var/lib/gitea
···
62
62
63
63
> 如果未为卷设置正确的权限，容器可能无法启动。
64
64
65
-
对于稳定版本，您可以使用 `:latest-rootless`、`:1-rootless`，或指定特定的版本，如: `{{< version >}}-rootless`。如果您想使用最新的开发版本，则可以使用 `:dev-rootless` 标签。如果您想运行发布分支的最新提交，可以使用 `:1.x-dev-rootless` 标签，其中 x是 Gitea 的次要版本号（例如:`1.16-dev-rootless`）。
65
+
对于稳定版本，您可以使用 `:latest-rootless`、`:1-rootless`，或指定特定的版本，如: `@version@-rootless`。如果您想使用最新的开发版本，则可以使用 `:dev-rootless` 标签。如果您想运行发布分支的最新提交，可以使用 `:1.x-dev-rootless` 标签，其中 x是 Gitea 的次要版本号（例如:`1.16-dev-rootless`）。
66
66
67
67
## 自定义端口
68
68
···
73
73
74
74
services:
75
75
server:
76
-
image: gitea/gitea:{{< version >}}-rootless
76
+
image: gitea/gitea:@version@-rootless
77
77
restart: always
78
78
volumes:
79
79
- ./data:/var/lib/gitea
···
96
96
97
97
services:
98
98
server:
99
-
image: gitea/gitea:{{< version >}}-rootless
99
+
image: gitea/gitea:@version@-rootless
100
100
+ environment:
101
101
+ - GITEA__database__DB_TYPE=mysql
102
102
+ - GITEA__database__HOST=db:3306
···
136
136
137
137
services:
138
138
server:
139
-
image: gitea/gitea:{{< version >}}-rootless
139
+
image: gitea/gitea:@version@-rootless
140
140
environment:
141
141
+ - GITEA__database__DB_TYPE=postgres
142
142
+ - GITEA__database__HOST=db:5432
···
181
181
+
182
182
services:
183
183
server:
184
-
image: gitea/gitea:{{< version >}}-rootless
184
+
image: gitea/gitea:@version@-rootless
185
185
restart: always
186
186
volumes:
187
187
- - ./data:/var/lib/gitea
···
208
208
209
209
services:
210
210
server:
211
-
image: gitea/gitea:{{< version >}}-rootless
211
+
image: gitea/gitea:@version@-rootless
212
212
restart: always
213
213
+ user: 1001
214
214
volumes:
···
259
259
- 将卷中的文件夹（gitea）重命名为 custom
260
260
- 如果需要，编辑 `app.ini`
261
261
- 设置 `START_SSH_SERVER = true`
262
-
- 使用镜像 `gitea/gitea:{{< version >}}-rootless`
262
+
- 使用镜像 `gitea/gitea:@version@-rootless`
263
263
264
264
## 使用环境变量管理部署
265
265
+8
-12
docs/content/doc/installation/with-docker.en-us.md
docs/content/installation/with-docker.en-us.md
+8
-12
docs/content/doc/installation/with-docker.en-us.md
docs/content/installation/with-docker.en-us.md
···
2
2
date: "2020-03-19T19:27:00+02:00"
3
3
title: "Installation with Docker"
4
4
slug: "install-with-docker"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "With Docker"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "install-with-docker"
16
16
---
17
17
···
25
25
of `docker-compose` is out of scope of this documentation. To install `docker-compose` itself, follow
26
26
the official [install instructions](https://docs.docker.com/compose/install/).
27
27
28
-
**Table of Contents**
29
-
30
-
{{< toc >}}
31
-
32
28
## Basics
33
29
34
30
The most simple setup just creates a volume and a network and starts the `gitea/gitea:latest`
···
36
32
Create a directory like `gitea` and paste the following content into a file named `docker-compose.yml`.
37
33
Note that the volume should be owned by the user/group with the UID/GID specified in the config file.
38
34
If you don't give the volume correct permissions, the container may not start.
39
-
For a stable release you can use `:latest`, `:1` or specify a certain release like `:{{< version >}}`, but if you'd like to use the latest development version of Gitea then you could use the `:nightly` tag. If you'd like to run the latest commit from a release branch you can use the `:1.x-nightly` tag, where x is the minor version of Gitea. (e.g. `:1.16-nightly`)
35
+
For a stable release you can use `:latest`, `:1` or specify a certain release like `:@version@`, but if you'd like to use the latest development version of Gitea then you could use the `:nightly` tag. If you'd like to run the latest commit from a release branch you can use the `:1.x-nightly` tag, where x is the minor version of Gitea. (e.g. `:1.16-nightly`)
40
36
41
37
```yaml
42
38
version: "3"
···
47
43
48
44
services:
49
45
server:
50
-
image: gitea/gitea:{{< version >}}
46
+
image: gitea/gitea:@version@
51
47
container_name: gitea
52
48
environment:
53
49
- USER_UID=1000
···
79
75
80
76
services:
81
77
server:
82
-
image: gitea/gitea:{{< version >}}
78
+
image: gitea/gitea:@version@
83
79
container_name: gitea
84
80
environment:
85
81
- USER_UID=1000
···
114
110
115
111
services:
116
112
server:
117
-
image: gitea/gitea:{{< version >}}
113
+
image: gitea/gitea:@version@
118
114
container_name: gitea
119
115
environment:
120
116
- USER_UID=1000
···
165
161
166
162
services:
167
163
server:
168
-
image: gitea/gitea:{{< version >}}
164
+
image: gitea/gitea:@version@
169
165
container_name: gitea
170
166
environment:
171
167
- USER_UID=1000
···
221
217
+
222
218
services:
223
219
server:
224
-
image: gitea/gitea:{{< version >}}
220
+
image: gitea/gitea:@version@
225
221
container_name: gitea
226
222
restart: always
227
223
networks:
+2
-4
docs/content/doc/installation/with-docker.fr-fr.md
docs/content/installation/with-docker.fr-fr.md
+2
-4
docs/content/doc/installation/with-docker.fr-fr.md
docs/content/installation/with-docker.fr-fr.md
···
2
2
date: "2017-08-23T09:00:00+02:00"
3
3
title: "Installation avec Docker"
4
4
slug: "install-with-docker"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Docker"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "install-with-docker"
16
16
---
17
17
18
18
# Installation avec Docker
19
19
20
20
Nous fournissons des images Docker mises à jour automatiquement via le Docker Hub de notre organisation. C'est à vous, lors devotre déploiement, de vous assurez d'utiliser toujours la dernière version stable ou d'utiliser un autre service qui met à jour l'image Docker pour vous.
21
-
22
-
{{< toc >}}
23
21
24
22
## Données stockées sur l'hôte
25
23
+9
-11
docs/content/doc/installation/with-docker.zh-cn.md
docs/content/installation/with-docker.zh-cn.md
+9
-11
docs/content/doc/installation/with-docker.zh-cn.md
docs/content/installation/with-docker.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "使用 Docker 安装"
4
4
slug: "install-with-docker"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "使用 Docker 安装"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "install-with-docker"
16
16
---
17
17
···
21
21
22
22
该参考设置指导用户完成基于 `docker-compose` 的设置，但是 `docker-compose` 的安装不在本文档的范围之内。要安装 `docker-compose` 本身，请遵循官方[安装说明](https://docs.docker.com/compose/install/)。
23
23
24
-
{{< toc >}}
25
-
26
24
## 基本
27
25
28
-
最简单的设置只是创建一个卷和一个网络，然后将 `gitea/gitea:latest` 镜像作为服务启动。由于没有可用的数据库，因此可以使用 SQLite3 初始化数据库。创建一个类似 `gitea` 的目录，并将以下内容粘贴到名为 `docker-compose.yml` 的文件中。请注意，该卷应由配置文件中指定的 UID/GID 的用户/组拥有。如果您不授予卷正确的权限，则容器可能无法启动。另请注意，标签 `:latest` 将安装当前的开发版本。对于稳定的发行版，您可以使用 `:1` 或指定某个发行版，例如 `{{< version >}}`。
26
+
最简单的设置只是创建一个卷和一个网络，然后将 `gitea/gitea:latest` 镜像作为服务启动。由于没有可用的数据库，因此可以使用 SQLite3 初始化数据库。创建一个类似 `gitea` 的目录，并将以下内容粘贴到名为 `docker-compose.yml` 的文件中。请注意，该卷应由配置文件中指定的 UID/GID 的用户/组拥有。如果您不授予卷正确的权限，则容器可能无法启动。另请注意，标签 `:latest` 将安装当前的开发版本。对于稳定的发行版，您可以使用 `:1` 或指定某个发行版，例如 `@version@`。
29
27
30
28
```yaml
31
29
version: "3"
···
36
34
37
35
services:
38
36
server:
39
-
image: gitea/gitea:{{< version >}}
37
+
image: gitea/gitea:@version@
40
38
container_name: gitea
41
39
environment:
42
40
- USER_UID=1000
···
66
64
67
65
services:
68
66
server:
69
-
image: gitea/gitea:{{< version >}}
67
+
image: gitea/gitea:@version@
70
68
container_name: gitea
71
69
environment:
72
70
- USER_UID=1000
···
100
98
101
99
services:
102
100
server:
103
-
image: gitea/gitea:{{< version >}}
101
+
image: gitea/gitea:@version@
104
102
container_name: gitea
105
103
environment:
106
104
- USER_UID=1000
···
150
148
151
149
services:
152
150
server:
153
-
image: gitea/gitea:{{< version >}}
151
+
image: gitea/gitea:@version@
154
152
container_name: gitea
155
153
environment:
156
154
- USER_UID=1000
···
203
201
+
204
202
services:
205
203
server:
206
-
image: gitea/gitea:{{< version >}}
204
+
image: gitea/gitea:@version@
207
205
container_name: gitea
208
206
restart: always
209
207
networks:
···
252
250
- `DB_HOST`：**localhost:3306**：数据库主机地址和端口。
253
251
- `DB_NAME`：**gitea**：数据库名称。
254
252
- `DB_USER`：**root**：数据库用户名。
255
-
- `DB_PASSWD`：**"\<empty>"** ：数据库用户密码。如果您在密码中使用特殊字符，请使用“您的密码”进行引用。
253
+
- `DB_PASSWD`：**"_empty_"** ：数据库用户密码。如果您在密码中使用特殊字符，请使用“您的密码”进行引用。
256
254
- `INSTALL_LOCK`：**false**：禁止访问安装页面。
257
255
- `SECRET_KEY`：**""** ：全局密钥。这应该更改。如果它具有一个值并且 `INSTALL_LOCK` 为空，则 `INSTALL_LOCK` 将自动设置为 `true`。
258
256
- `DISABLE_REGISTRATION`：**false**：禁用注册，之后只有管理员才能为用户创建帐户。
+2
-4
docs/content/doc/installation/with-docker.zh-tw.md
docs/content/installation/with-docker.zh-tw.md
+2
-4
docs/content/doc/installation/with-docker.zh-tw.md
docs/content/installation/with-docker.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Docker 安裝"
4
4
slug: "install-with-docker"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "installation"
13
13
name: "Docker 安裝"
14
-
weight: 70
14
+
sidebar_position: 70
15
15
identifier: "install-with-docker"
16
16
---
17
17
18
18
# 用 Docker 安裝
19
-
20
-
{{< toc >}}
21
19
22
20
我們在 Docker Hub 提供了自動更新的映像檔，它會保持最新穩定版。根據您的部屬環境來使用最新版本或用其他服務來更新 Docker 映像檔。首先您需要下載映像檔：
23
21
+2
-2
docs/content/doc/packages.en-us.md
docs/content/packages.en-us.md
+2
-2
docs/content/doc/packages.en-us.md
docs/content/packages.en-us.md
+1
-2
docs/content/doc/search.de-de.md
docs/content/search.de-de.md
+1
-2
docs/content/doc/search.de-de.md
docs/content/search.de-de.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "Search"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+1
-2
docs/content/doc/search.en-us.md
docs/content/search.en-us.md
+1
-2
docs/content/doc/search.en-us.md
docs/content/search.en-us.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "Search"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+1
-2
docs/content/doc/search.fr-fr.md
docs/content/search.fr-fr.md
+1
-2
docs/content/doc/search.fr-fr.md
docs/content/search.fr-fr.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "Chercher"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+1
-2
docs/content/doc/search.nl-nl.md
docs/content/search.nl-nl.md
+1
-2
docs/content/doc/search.nl-nl.md
docs/content/search.nl-nl.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "Search"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+1
-2
docs/content/doc/search.pt-br.md
docs/content/search.pt-br.md
+1
-2
docs/content/doc/search.pt-br.md
docs/content/search.pt-br.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "Search"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+1
-2
docs/content/doc/search.zh-cn.md
docs/content/search.zh-cn.md
+1
-2
docs/content/doc/search.zh-cn.md
docs/content/search.zh-cn.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "搜索"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+1
-2
docs/content/doc/search.zh-tw.md
docs/content/search.zh-tw.md
+1
-2
docs/content/doc/search.zh-tw.md
docs/content/search.zh-tw.md
···
2
2
date: "2019-11-12T16:00:00+02:00"
3
3
title: "搜尋"
4
4
slug: "search"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
priority : 1
12
12
layout: "search"
13
13
---
14
-
15
14
16
15
This file exists solely to respond to /search URL with the related `search` layout template.
17
16
+2
-2
docs/content/doc/usage.en-us.md
docs/content/usage.en-us.md
+2
-2
docs/content/doc/usage.en-us.md
docs/content/usage.en-us.md
+2
-2
docs/content/doc/usage.zh-cn.md
docs/content/usage.zh-cn.md
+2
-2
docs/content/doc/usage.zh-cn.md
docs/content/usage.zh-cn.md
+2
-2
docs/content/doc/usage.zh-tw.md
docs/content/usage.zh-tw.md
+2
-2
docs/content/doc/usage.zh-tw.md
docs/content/usage.zh-tw.md
docs/content/doc/usage/_index.en-us.md
docs/content/usage/_index.en-us.md
docs/content/doc/usage/_index.en-us.md
docs/content/usage/_index.en-us.md
docs/content/doc/usage/_index.zh-cn.md
docs/content/usage/_index.zh-cn.md
docs/content/doc/usage/_index.zh-cn.md
docs/content/usage/_index.zh-cn.md
docs/content/doc/usage/_index.zh-tw.md
docs/content/usage/_index.zh-tw.md
docs/content/doc/usage/_index.zh-tw.md
docs/content/usage/_index.zh-tw.md
+2
-6
docs/content/doc/usage/actions/act-runner.en-us.md
docs/content/usage/actions/act-runner.en-us.md
+2
-6
docs/content/doc/usage/actions/act-runner.en-us.md
docs/content/usage/actions/act-runner.en-us.md
···
2
2
date: "2023-04-27T15:00:00+08:00"
3
3
title: "Act Runner"
4
4
slug: "act-runner"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Act Runner"
12
-
weight: 20
12
+
sidebar_position: 20
13
13
identifier: "actions-runner"
14
14
---
15
15
16
16
# Act Runner
17
17
18
18
This page will introduce the [act runner](https://gitea.com/gitea/act_runner) in detail, which is the runner of Gitea Actions.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
+5
-9
docs/content/doc/usage/actions/act-runner.zh-cn.md
docs/content/usage/actions/act-runner.zh-cn.md
+5
-9
docs/content/doc/usage/actions/act-runner.zh-cn.md
docs/content/usage/actions/act-runner.zh-cn.md
···
2
2
date: "2023-05-24T15:00:00+08:00"
3
3
title: "Act Runner"
4
4
slug: "act-runner"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Act Runner"
12
-
weight: 20
12
+
sidebar_position: 20
13
13
identifier: "actions-runner"
14
14
---
15
15
16
16
# Act Runner
17
17
18
18
本页面将详细介绍[Act Runner](https://gitea.com/gitea/act_runner)，这是Gitea Actions的Runner。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
215
211
enabled: true
216
212
dir: ""
217
213
# 使用步骤 1. 获取的 LAN IP
218
-
host: "192.168.8.17"
214
+
host: "192.168.8.17"
219
215
# 使用步骤 2. 获取的端口号
220
-
port: 8088
216
+
port: 8088
221
217
```
222
218
223
219
- 4.启动容器时, 将 Cache 端口映射至主机。
···
225
221
```bash
226
222
docker run \
227
223
--name gitea-docker-runner \
228
-
-p 8088:8088 \
224
+
-p 8088:8088 \
229
225
-d gitea/act_runner:nightly
230
226
```
231
227
+3
-7
docs/content/doc/usage/actions/comparison.en-us.md
docs/content/usage/actions/comparison.en-us.md
+3
-7
docs/content/doc/usage/actions/comparison.en-us.md
docs/content/usage/actions/comparison.en-us.md
···
2
2
date: "2023-04-27T15:00:00+08:00"
3
3
title: "Compared to GitHub Actions"
4
4
slug: "comparison"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Comparison"
12
-
weight: 30
12
+
sidebar_position: 30
13
13
identifier: "actions-comparison"
14
14
---
15
15
16
16
# Compared to GitHub Actions
17
17
18
18
Even though Gitea Actions is designed to be compatible with GitHub Actions, there are some differences between them.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Additional features
25
21
···
132
128
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
129
134
130
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" >}}).
131
+
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](administration/config-cheat-sheet.md#actions-actions).
136
132
137
133
### Context availability
138
134
+3
-7
docs/content/doc/usage/actions/comparison.zh-cn.md
docs/content/usage/actions/comparison.zh-cn.md
+3
-7
docs/content/doc/usage/actions/comparison.zh-cn.md
docs/content/usage/actions/comparison.zh-cn.md
···
2
2
date: "2023-05-24T15:00:00+08:00"
3
3
title: "与GitHub Actions的对比"
4
4
slug: "comparison"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "对比"
12
-
weight: 30
12
+
sidebar_position: 30
13
13
identifier: "actions-comparison"
14
14
---
15
15
16
16
# 与GitHub Actions的对比
17
17
18
18
尽管Gitea Actions旨在与GitHub Actions兼容，但它们之间存在一些差异。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 额外功能
25
21
···
132
128
这意味着`uses: actions/checkout@v3`将从[gitea.com/actions/checkout](https://gitea.com/actions/checkout)下载该Action，而不是[github.com/actions/checkout](https://github.com/actions/checkout)。
133
129
134
130
正如前面提到的，这是可配置的。
135
-
如果您希望您的运行程序默认从GitHub或您自己的Gitea实例下载动作，您可以通过设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单]({{< relref "doc/administration/config-cheat-sheet.zh-cn.md#actions-actions" >}})。
131
+
如果您希望您的运行程序默认从GitHub或您自己的Gitea实例下载动作，您可以通过设置`[actions].DEFAULT_ACTIONS_URL`进行配置。请参阅[配置备忘单](administration/config-cheat-sheet.md#actions-actions)。
136
132
137
133
### 上下文可用性
138
134
+2
-6
docs/content/doc/usage/actions/design.en-us.md
docs/content/usage/actions/design.en-us.md
+2
-6
docs/content/doc/usage/actions/design.en-us.md
docs/content/usage/actions/design.en-us.md
···
2
2
date: "2023-04-27T15:00:00+08:00"
3
3
title: "Design of Gitea Actions"
4
4
slug: "design"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Design"
12
-
weight: 40
12
+
sidebar_position: 40
13
13
identifier: "actions-design"
14
14
---
15
15
16
16
# Design of Gitea Actions
17
17
18
18
Gitea Actions has multiple components. This document describes them individually.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Act
25
21
+2
-6
docs/content/doc/usage/actions/design.zh-cn.md
docs/content/usage/actions/design.zh-cn.md
+2
-6
docs/content/doc/usage/actions/design.zh-cn.md
docs/content/usage/actions/design.zh-cn.md
···
2
2
date: "2023-05-24T15:00:00+08:00"
3
3
title: "Gitea Actions设计"
4
4
slug: "design"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "设计"
12
-
weight: 40
12
+
sidebar_position: 40
13
13
identifier: "actions-design"
14
14
---
15
15
16
16
# Gitea Actions设计
17
17
18
18
Gitea Actions由多个组件组成。本文档将对它们进行逐个描述。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## Act
25
21
+2
-6
docs/content/doc/usage/actions/faq.en-us.md
docs/content/usage/actions/faq.en-us.md
+2
-6
docs/content/doc/usage/actions/faq.en-us.md
docs/content/usage/actions/faq.en-us.md
···
2
2
date: "2023-04-27T15:00:00+08:00"
3
3
title: "Frequently Asked Questions of Gitea Actions"
4
4
slug: "faq"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "FAQ"
12
-
weight: 100
12
+
sidebar_position: 100
13
13
identifier: "actions-faq"
14
14
---
15
15
16
16
# Frequently Asked Questions of Gitea Actions
17
17
18
18
This page contains some common questions and answers about Gitea Actions.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Why is Actions not enabled by default?
25
21
+2
-6
docs/content/doc/usage/actions/faq.zh-cn.md
docs/content/usage/actions/faq.zh-cn.md
+2
-6
docs/content/doc/usage/actions/faq.zh-cn.md
docs/content/usage/actions/faq.zh-cn.md
···
2
2
date: "2023-05-24T15:00:00+08:00"
3
3
title: "Gitea Actions常见问题解答"
4
4
slug: "faq"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "常见问题"
12
-
weight: 100
12
+
sidebar_position: 100
13
13
identifier: "actions-faq"
14
14
---
15
15
16
16
# Gitea Actions常见问题解答
17
17
18
18
本页面包含一些关于Gitea Actions的常见问题和答案。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 为什么默认情况下不启用Actions？
25
21
+2
-6
docs/content/doc/usage/actions/overview.en-us.md
docs/content/usage/actions/overview.en-us.md
+2
-6
docs/content/doc/usage/actions/overview.en-us.md
docs/content/usage/actions/overview.en-us.md
···
2
2
date: "2023-04-27T15:00:00+08:00"
3
3
title: "Gitea Actions"
4
4
slug: "overview"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Overview"
12
-
weight: 1
12
+
sidebar_position: 1
13
13
identifier: "actions-overview"
14
14
---
15
15
16
16
# Gitea Actions
17
17
18
18
Starting with Gitea **1.19**, Gitea Actions are available as a built-in CI/CD solution.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Name
25
21
+2
-6
docs/content/doc/usage/actions/overview.zh-cn.md
docs/content/usage/actions/overview.zh-cn.md
+2
-6
docs/content/doc/usage/actions/overview.zh-cn.md
docs/content/usage/actions/overview.zh-cn.md
···
2
2
date: "2023-05-24T15:00:00+08:00"
3
3
title: "Gitea Actions"
4
4
slug: "overview"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Overview"
12
-
weight: 1
12
+
sidebar_position: 1
13
13
identifier: "actions-overview"
14
14
---
15
15
16
16
# Gitea Actions
17
17
18
18
从Gitea **1.19**版本开始，Gitea Actions成为了内置的CI/CD解决方案。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 名称
25
21
+6
-10
docs/content/doc/usage/actions/quickstart.en-us.md
docs/content/usage/actions/quickstart.en-us.md
+6
-10
docs/content/doc/usage/actions/quickstart.en-us.md
docs/content/usage/actions/quickstart.en-us.md
···
2
2
date: "2023-04-27T15:00:00+08:00"
3
3
title: "Quick Start"
4
4
slug: "quickstart"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "Quick Start"
12
-
weight: 10
12
+
sidebar_position: 10
13
13
identifier: "actions-quickstart"
14
14
---
15
15
16
16
# Quick Start
17
17
18
18
This page will guide you through the process of using Gitea Actions.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Set up Gitea
25
21
26
22
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.
23
+
You can follow the [documentation](installation/from-package.md) to set up a new instance or upgrade your existing one.
28
24
It doesn't matter how you install or run Gitea, as long as its version is 1.19.0 or higher.
29
25
30
26
Actions are disabled by default, so you need to add the following to the configuration file to enable it:
···
34
30
ENABLED=true
35
31
```
36
32
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" >}}).
33
+
If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions).
38
34
39
35
### Set up runner
40
36
···
89
85
90
86
91
87
92
-
You can find more information by visiting [Act runner]({{< relref "doc/usage/actions/act-runner.en-us.md" >}}).
88
+
You can find more information by visiting [Act runner](usage/actions/act-runner.md).
93
89
94
90
### Use Actions
95
91
···
133
129
Be careful, the demo file contains some emojis.
134
130
Please make sure your database supports them, especially when using MySQL.
135
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`.
136
-
See [Database Preparation]({{< relref "doc/installation/database-preparation.en-us.md#mysql" >}}) for more information.
132
+
See [Database Preparation](installation/database-preparation.md#mysql) for more information.
137
133
138
134
Alternatively, you can remove all emojis from the demo file and try again.
139
135
+6
-10
docs/content/doc/usage/actions/quickstart.zh-cn.md
docs/content/usage/actions/quickstart.zh-cn.md
+6
-10
docs/content/doc/usage/actions/quickstart.zh-cn.md
docs/content/usage/actions/quickstart.zh-cn.md
···
2
2
date: "2023-05-24T15:00:00+08:00"
3
3
title: "快速入门"
4
4
slug: "quickstart"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "actions"
11
11
name: "快速入门"
12
-
weight: 10
12
+
sidebar_position: 10
13
13
identifier: "actions-quickstart"
14
14
---
15
15
16
16
# 快速入门
17
17
18
18
本页面将指导您使用Gitea Actions的过程。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 设置Gitea
25
21
26
22
首先，您需要一个Gitea实例。
27
-
您可以按照[文档]({{< relref "doc/installation/from-package.zh-cn.md" >}}) 来设置一个新实例或升级现有实例。
23
+
您可以按照[文档](installation/from-package.md) 来设置一个新实例或升级现有实例。
28
24
无论您如何安装或运行Gitea，只要版本号是1.19.0或更高即可。
29
25
30
26
默认情况下，Actions是禁用的，因此您需要将以下内容添加到配置文件中以启用它：
···
34
30
ENABLED=true
35
31
```
36
32
37
-
如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表]({{< relref "doc/administration/config-cheat-sheet.zh-cn.md#actions-actions" >}})。
33
+
如果您想了解更多信息或在配置过程中遇到任何问题，请参考[配置速查表](administration/config-cheat-sheet.md#actions-actions)。
38
34
39
35
### 设置Runner
40
36
···
88
84
89
85
90
86
91
-
您可以通过访问[act runner]({{< relref "doc/usage/actions/act-runner.zh-cn.md" >}}) 获取更多信息。
87
+
您可以通过访问[act runner](usage/actions/act-runner.md) 获取更多信息。
92
88
93
89
### 使用Actions
94
90
···
132
128
请注意，演示文件中包含一些表情符号。
133
129
请确保您的数据库支持它们，特别是在使用MySQL时。
134
130
如果字符集不是`utf8mb4，将出现错误，例如`Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`。
135
-
有关更多信息，请参阅[数据库准备工作]({{< relref "doc/installation/database-preparation.zh-cn.md#mysql" >}})。
131
+
有关更多信息，请参阅[数据库准备工作](installation/database-preparation.md#mysql)。
136
132
137
133
或者，您可以从演示文件中删除所有表情符号，然后再尝试一次。
138
134
+2
-2
docs/content/doc/usage/agit-support.en-us.md
docs/content/usage/agit-support.en-us.md
+2
-2
docs/content/doc/usage/agit-support.en-us.md
docs/content/usage/agit-support.en-us.md
···
2
2
date: " 2022-09-01T20:50:42+0000"
3
3
title: "Agit Setup"
4
4
slug: "agit-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Agit Setup"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "agit-setup"
16
16
---
17
17
+2
-2
docs/content/doc/usage/agit-support.zh-cn.md
docs/content/usage/agit-support.zh-cn.md
+2
-2
docs/content/doc/usage/agit-support.zh-cn.md
docs/content/usage/agit-support.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "Agit 设置"
4
4
slug: "agit-setup"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Agit 设置"
14
-
weight: 12
14
+
sidebar_position: 12
15
15
identifier: "agit-setup"
16
16
---
17
17
+2
-4
docs/content/doc/usage/authentication.en-us.md
docs/content/usage/authentication.en-us.md
+2
-4
docs/content/doc/usage/authentication.en-us.md
docs/content/usage/authentication.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Authentication"
4
4
slug: "authentication"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Authentication"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "authentication"
16
16
---
17
17
18
18
# Authentication
19
-
20
-
{{< toc >}}
21
19
22
20
## LDAP (Lightweight Directory Access Protocol)
23
21
+2
-2
docs/content/doc/usage/authentication.zh-cn.md
docs/content/usage/authentication.zh-cn.md
+2
-2
docs/content/doc/usage/authentication.zh-cn.md
docs/content/usage/authentication.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "认证"
4
4
slug: "authentication"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "认证"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "authentication"
16
16
---
17
17
+2
-2
docs/content/doc/usage/authentication.zh-tw.md
docs/content/usage/authentication.zh-tw.md
+2
-2
docs/content/doc/usage/authentication.zh-tw.md
docs/content/usage/authentication.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "認證"
4
4
slug: "authentication"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "認證"
14
-
weight: 10
14
+
sidebar_position: 10
15
15
identifier: "authentication"
16
16
---
17
17
+2
-2
docs/content/doc/usage/clone-filter.en-us.md
docs/content/usage/clone-filter.en-us.md
+2
-2
docs/content/doc/usage/clone-filter.en-us.md
docs/content/usage/clone-filter.en-us.md
···
2
2
date: "2021-02-02"
3
3
title: "Clone filters (partial clone)"
4
4
slug: "clone-filters"
5
-
weight: 25
5
+
sidebar_position: 25
6
6
draft: false
7
7
toc: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Clone filters"
14
-
weight: 25
14
+
sidebar_position: 25
15
15
identifier: "clone-filters"
16
16
---
17
17
+2
-2
docs/content/doc/usage/clone-filter.zh-cn.md
docs/content/usage/clone-filter.zh-cn.md
+2
-2
docs/content/doc/usage/clone-filter.zh-cn.md
docs/content/usage/clone-filter.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "克隆过滤器 (部分克隆)"
4
4
slug: "clone-filters"
5
-
weight: 25
5
+
sidebar_position: 25
6
6
draft: false
7
7
toc: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "克隆过滤器"
14
-
weight: 25
14
+
sidebar_position: 25
15
15
identifier: "clone-filters"
16
16
---
17
17
+2
-2
docs/content/doc/usage/code-owners.en-us.md
docs/content/usage/code-owners.en-us.md
+2
-2
docs/content/doc/usage/code-owners.en-us.md
docs/content/usage/code-owners.en-us.md
···
2
2
date: "2023-05-24T16:00:00+00:00"
3
3
title: "Code Owners"
4
4
slug: "code-owners"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Code Owners"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "code-owners"
16
16
---
17
17
+2
-6
docs/content/doc/usage/incoming-email.en-us.md
docs/content/usage/incoming-email.en-us.md
+2
-6
docs/content/doc/usage/incoming-email.en-us.md
docs/content/usage/incoming-email.en-us.md
···
2
2
date: "2022-12-01T00:00:00+00:00"
3
3
title: "Incoming Email"
4
4
slug: "incoming-email"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
draft: false
7
7
toc: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Incoming Email"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "incoming-email"
16
16
---
17
17
18
18
# Incoming Email
19
19
20
20
Gitea supports the execution of several actions through incoming mails. This page describes how to set this up.
21
-
22
-
**Table of Contents**
23
-
24
-
{{< toc >}}
25
21
26
22
## Requirements
27
23
+2
-6
docs/content/doc/usage/incoming-email.zh-cn.md
docs/content/usage/incoming-email.zh-cn.md
+2
-6
docs/content/doc/usage/incoming-email.zh-cn.md
docs/content/usage/incoming-email.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "邮件接收"
4
4
slug: "incoming-email"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
draft: false
7
7
toc: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "邮件接收"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "incoming-email"
16
16
---
17
17
18
18
# 邮件接收
19
19
20
20
Gitea 支持通过接收邮件执行多种操作。本页面描述了如何进行设置。
21
-
22
-
**目录**
23
-
24
-
{{< toc >}}
25
21
26
22
## 要求
27
23
+2
-6
docs/content/doc/usage/issue-pull-request-templates.en-us.md
docs/content/usage/issue-pull-request-templates.en-us.md
+2
-6
docs/content/doc/usage/issue-pull-request-templates.en-us.md
docs/content/usage/issue-pull-request-templates.en-us.md
···
2
2
date: "2018-05-10T16:00:00+02:00"
3
3
title: "Issue and Pull Request templates"
4
4
slug: "issue-pull-request-templates"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Issue and Pull Request templates"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "issue-pull-request-templates"
16
16
---
17
17
18
18
# Issue and Pull Request Templates
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Some projects have a standard list of questions that users need to answer
25
21
when creating an issue or pull request. Gitea supports adding templates to the
+2
-6
docs/content/doc/usage/issue-pull-request-templates.zh-cn.md
docs/content/usage/issue-pull-request-templates.zh-cn.md
+2
-6
docs/content/doc/usage/issue-pull-request-templates.zh-cn.md
docs/content/usage/issue-pull-request-templates.zh-cn.md
···
2
2
date: "2022-09-07T16:00:00+08:00"
3
3
title: "工单与合并请求模板"
4
4
slug: "issue-pull-request-templates"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: true
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "工单与合并请求模板"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "issue-pull-request-templates"
16
16
---
17
17
18
18
# 从模板创建工单与合并请求
19
19
20
20
开发者可以利用问题模板创建工单与合并请求，其目的在于规范参与者的语言表达。
21
-
22
-
**目录**
23
-
24
-
{{< toc >}}
25
21
26
22
## 模板介绍
27
23
+2
-2
docs/content/doc/usage/labels.en-us.md
docs/content/usage/labels.en-us.md
+2
-2
docs/content/doc/usage/labels.en-us.md
docs/content/usage/labels.en-us.md
···
2
2
date: "2023-03-04T19:00:00+00:00"
3
3
title: "Labels"
4
4
slug: "labels"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Labels"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "labels"
16
16
---
17
17
+2
-2
docs/content/doc/usage/labels.zh-cn.md
docs/content/usage/labels.zh-cn.md
+2
-2
docs/content/doc/usage/labels.zh-cn.md
docs/content/usage/labels.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "标签"
4
4
slug: "labels"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "标签"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "labels"
16
16
---
17
17
+2
-6
docs/content/doc/usage/linked-references.en-us.md
docs/content/usage/linked-references.en-us.md
+2
-6
docs/content/doc/usage/linked-references.en-us.md
docs/content/usage/linked-references.en-us.md
···
2
2
date: "2019-11-21T17:00:00-03:00"
3
3
title: "Automatically Linked References"
4
4
slug: "automatically-linked-references"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Automatically Linked References"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "automatically-linked-references"
16
16
---
17
17
18
18
# Automatically Linked References in Issues, Pull Requests and Commit Messages
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
When an issue, pull request or comment is posted, the text description is parsed
25
21
in search for references. These references will be shown as links in the Issue View
+2
-6
docs/content/doc/usage/linked-references.zh-cn.md
docs/content/usage/linked-references.zh-cn.md
+2
-6
docs/content/doc/usage/linked-references.zh-cn.md
docs/content/usage/linked-references.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "自动链接引用"
4
4
slug: "automatically-linked-references"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "自动链接引用s"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "automatically-linked-references"
16
16
---
17
17
18
18
# 在工单、合并请求和提交消息中的自动链接引用
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
当发布工单、合并请求或评论时，文本描述会被解析以查找引用。这些引用将显示为工单视图中的链接，并且在某些情况下会触发特定的“操作”。
25
21
+2
-6
docs/content/doc/usage/merge-message-templates.en-us.md
docs/content/usage/merge-message-templates.en-us.md
+2
-6
docs/content/doc/usage/merge-message-templates.en-us.md
docs/content/usage/merge-message-templates.en-us.md
···
2
2
date: "2022-08-31T17:35:40+08:00"
3
3
title: "Merge Message templates"
4
4
slug: "merge-message-templates"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Merge Message templates"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "merge-message-templates"
16
16
---
17
17
18
18
# Merge Message templates
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## File names
25
21
+2
-6
docs/content/doc/usage/merge-message-templates.zh-cn.md
docs/content/usage/merge-message-templates.zh-cn.md
+2
-6
docs/content/doc/usage/merge-message-templates.zh-cn.md
docs/content/usage/merge-message-templates.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "合并消息模板"
4
4
slug: "merge-message-templates"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "合并消息模板"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "merge-message-templates"
16
16
---
17
17
18
18
# 合并消息模板
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 文件名
25
21
docs/content/doc/usage/packages/_index.en-us.md
docs/content/usage/packages/_index.en-us.md
docs/content/doc/usage/packages/_index.en-us.md
docs/content/usage/packages/_index.en-us.md
+3
-7
docs/content/doc/usage/packages/alpine.en-us.md
docs/content/usage/packages/alpine.en-us.md
+3
-7
docs/content/doc/usage/packages/alpine.en-us.md
docs/content/usage/packages/alpine.en-us.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "Alpine"
11
-
weight: 4
11
+
sidebar_position: 4
12
12
identifier: "alpine"
13
13
---
14
14
15
15
# Alpine Package Registry
16
16
17
17
Publish [Alpine](https://pkgs.alpinelinux.org/) packages for your user or organization.
18
-
19
-
**Table of Contents**
20
-
21
-
{{< toc >}}
22
18
23
19
## Requirements
24
20
···
40
36
| `branch` | The branch to use. |
41
37
| `repository` | The repository to use. |
42
38
43
-
If the registry is private, provide credentials in the url. You can use a password or a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}):
39
+
If the registry is private, provide credentials in the url. You can use a password or a [personal access token](development/api-usage.md#authentication):
44
40
45
41
```
46
42
https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/alpine/<branch>/<repository>
···
80
76
https://gitea.example.com/api/packages/testuser/alpine/v3.17/main
81
77
```
82
78
83
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
79
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
84
80
You cannot publish a file with the same name twice to a package. You must delete the existing package file first.
85
81
86
82
The server responds with the following HTTP Status codes.
+3
-7
docs/content/doc/usage/packages/alpine.zh-cn.md
docs/content/usage/packages/alpine.zh-cn.md
+3
-7
docs/content/doc/usage/packages/alpine.zh-cn.md
docs/content/usage/packages/alpine.zh-cn.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "Alpine"
11
-
weight: 4
11
+
sidebar_position: 4
12
12
identifier: "alpine"
13
13
---
14
14
15
15
# Alpine 软件包注册表
16
16
17
17
在您的用户或组织中发布 [Alpine](https://pkgs.alpinelinux.org/) 软件包。
18
-
19
-
**目录**
20
-
21
-
{{< toc >}}
22
18
23
19
## 要求
24
20
···
40
36
| `branch` | 要使用的分支名 |
41
37
| `repository` | 要使用的仓库名 |
42
38
43
-
如果注册表是私有的，请在 URL 中提供凭据。您可以使用密码或[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}}):
39
+
如果注册表是私有的，请在 URL 中提供凭据。您可以使用密码或[个人访问令牌](development/api-usage.md#通过-api-认证):
44
40
45
41
```
46
42
https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/alpine/<branch>/<repository>
···
80
76
https://gitea.example.com/api/packages/testuser/alpine/v3.17/main
81
77
```
82
78
83
-
如果您使用的是双重身份验证或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#authentication" >}})代替密码。
79
+
如果您使用的是双重身份验证或 OAuth，请使用[个人访问令牌](development/api-usage.md#authentication)代替密码。
84
80
您不能将具有相同名称的文件两次发布到一个包中。您必须首先删除现有的包文件。
85
81
86
82
服务器将以以下的 HTTP 状态码响应：
+3
-7
docs/content/doc/usage/packages/cargo.en-us.md
docs/content/usage/packages/cargo.en-us.md
+3
-7
docs/content/doc/usage/packages/cargo.en-us.md
docs/content/usage/packages/cargo.en-us.md
···
2
2
date: "2022-11-20T00:00:00+00:00"
3
3
title: "Cargo Package Registry"
4
4
slug: "cargo"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Cargo"
12
-
weight: 5
12
+
sidebar_position: 5
13
13
identifier: "cargo"
14
14
---
15
15
16
16
# Cargo Package Registry
17
17
18
18
Publish [Cargo](https://doc.rust-lang.org/stable/cargo/) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
74
70
75
71
| Parameter | Description |
76
72
| --------- | ----------- |
77
-
| `token` | Your [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) |
73
+
| `token` | Your [personal access token](development/api-usage.md#authentication) |
78
74
79
75
## Publish a package
80
76
+3
-7
docs/content/doc/usage/packages/cargo.zh-cn.md
docs/content/usage/packages/cargo.zh-cn.md
+3
-7
docs/content/doc/usage/packages/cargo.zh-cn.md
docs/content/usage/packages/cargo.zh-cn.md
···
2
2
date: "2022-11-20T00:00:00+00:00"
3
3
title: "Cargo 软件包注册表"
4
4
slug: "cargo"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Cargo"
12
-
weight: 5
12
+
sidebar_position: 5
13
13
identifier: "cargo"
14
14
---
15
15
16
16
# Cargo 软件包注册表
17
17
18
18
为您的用户或组织发布 [Cargo](https://doc.rust-lang.org/stable/cargo/) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
74
70
75
71
| 参数 | 描述 |
76
72
| ------- | ------------------------------------------------------------------------------------- |
77
-
| `token` | 您的[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}}) |
73
+
| `token` | 您的[个人访问令牌](development/api-usage.md#通过-api-认证) |
78
74
79
75
## 发布软件包
80
76
+2
-6
docs/content/doc/usage/packages/chef.en-us.md
docs/content/usage/packages/chef.en-us.md
+2
-6
docs/content/doc/usage/packages/chef.en-us.md
docs/content/usage/packages/chef.en-us.md
···
2
2
date: "2023-01-20T00:00:00+00:00"
3
3
title: "Chef Package Registry"
4
4
slug: "chef"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Chef"
12
-
weight: 5
12
+
sidebar_position: 5
13
13
identifier: "chef"
14
14
---
15
15
16
16
# Chef Package Registry
17
17
18
18
Publish [Chef](https://chef.io/) cookbooks for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
+2
-6
docs/content/doc/usage/packages/chef.zh-cn.md
docs/content/usage/packages/chef.zh-cn.md
+2
-6
docs/content/doc/usage/packages/chef.zh-cn.md
docs/content/usage/packages/chef.zh-cn.md
···
2
2
date: "2023-01-20T00:00:00+00:00"
3
3
title: "Chef 软件包注册表"
4
4
slug: "chef"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Chef"
12
-
weight: 5
12
+
sidebar_position: 5
13
13
identifier: "chef"
14
14
---
15
15
16
16
# Chef Package Registry
17
17
18
18
为您的用户或组织发布 [Chef](https://chef.io/) cookbooks。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
+3
-7
docs/content/doc/usage/packages/composer.en-us.md
docs/content/usage/packages/composer.en-us.md
+3
-7
docs/content/doc/usage/packages/composer.en-us.md
docs/content/usage/packages/composer.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Composer Package Registry"
4
4
slug: "composer"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Composer"
12
-
weight: 10
12
+
sidebar_position: 10
13
13
identifier: "composer"
14
14
---
15
15
16
16
# Composer Package Registry
17
17
18
18
Publish [Composer](https://getcomposer.org/) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
61
57
https://gitea.example.com/api/packages/testuser/composer?version=1.0.3
62
58
```
63
59
64
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
60
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
65
61
66
62
The server responds with the following HTTP Status codes.
67
63
+3
-7
docs/content/doc/usage/packages/composer.zh-cn.md
docs/content/usage/packages/composer.zh-cn.md
+3
-7
docs/content/doc/usage/packages/composer.zh-cn.md
docs/content/usage/packages/composer.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Composer 软件包注册表"
4
4
slug: "composer"
5
-
weight: 10
5
+
sidebar_position: 10
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Composer"
12
-
weight: 10
12
+
sidebar_position: 10
13
13
identifier: "composer"
14
14
---
15
15
16
16
# Composer 软件包注册表
17
17
18
18
为您的用户或组织发布 [Composer](https://getcomposer.org/) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
61
57
https://gitea.example.com/api/packages/testuser/composer?version=1.0.3
62
58
```
63
59
64
-
如果您使用 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码。
60
+
如果您使用 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码。
65
61
66
62
服务器将以以下 HTTP 状态码响应。
67
63
+3
-7
docs/content/doc/usage/packages/conan.en-us.md
docs/content/usage/packages/conan.en-us.md
+3
-7
docs/content/doc/usage/packages/conan.en-us.md
docs/content/usage/packages/conan.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Conan Package Registry"
4
4
slug: "conan"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Conan"
12
-
weight: 20
12
+
sidebar_position: 20
13
13
identifier: "conan"
14
14
---
15
15
···
17
17
18
18
Publish [Conan](https://conan.io/) packages for your user or organization.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Requirements
25
21
26
22
To work with the Conan package registry, you need to use the [conan](https://conan.io/downloads.html) command line tool to consume and publish packages.
···
38
34
| -----------| ----------- |
39
35
| `remote` | The remote name. |
40
36
| `username` | Your Gitea username. |
41
-
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. |
37
+
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password. |
42
38
| `owner` | The owner of the package. |
43
39
44
40
For example:
+3
-7
docs/content/doc/usage/packages/conan.zh-cn.md
docs/content/usage/packages/conan.zh-cn.md
+3
-7
docs/content/doc/usage/packages/conan.zh-cn.md
docs/content/usage/packages/conan.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Conan 软件包注册表"
4
4
slug: "conan"
5
-
weight: 20
5
+
sidebar_position: 20
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Conan"
12
-
weight: 20
12
+
sidebar_position: 20
13
13
identifier: "conan"
14
14
---
15
15
···
17
17
18
18
为您的用户或组织发布 [Conan](https://conan.io/) 软件包。
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 要求
25
21
26
22
要使用 [conan](https://conan.io/downloads.html) 软件包注册表，您需要使用 conan 命令行工具来消费和发布软件包。
···
38
34
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
39
35
| `remote` | 远程名称。 |
40
36
| `username` | 您的 Gitea 用户名。 |
41
-
| `password` | 您的 Gitea 密码。如果您使用 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码。 |
37
+
| `password` | 您的 Gitea 密码。如果您使用 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码。 |
42
38
| `owner` | 软件包的所有者。 |
43
39
44
40
例如:
+2
-6
docs/content/doc/usage/packages/conda.en-us.md
docs/content/usage/packages/conda.en-us.md
+2
-6
docs/content/doc/usage/packages/conda.en-us.md
docs/content/usage/packages/conda.en-us.md
···
2
2
date: "2022-12-28T00:00:00+00:00"
3
3
title: "Conda Package Registry"
4
4
slug: "conda"
5
-
weight: 25
5
+
sidebar_position: 25
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Conda"
12
-
weight: 25
12
+
sidebar_position: 25
13
13
identifier: "conda"
14
14
---
15
15
16
16
# Conda Package Registry
17
17
18
18
Publish [Conda](https://docs.conda.io/en/latest/) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
+2
-6
docs/content/doc/usage/packages/conda.zh-cn.md
docs/content/usage/packages/conda.zh-cn.md
+2
-6
docs/content/doc/usage/packages/conda.zh-cn.md
docs/content/usage/packages/conda.zh-cn.md
···
2
2
date: "2022-12-28T00:00:00+00:00"
3
3
title: "Conda 软件包注册表"
4
4
slug: "conda"
5
-
weight: 25
5
+
sidebar_position: 25
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Conda"
12
-
weight: 25
12
+
sidebar_position: 25
13
13
identifier: "conda"
14
14
---
15
15
16
16
# Conda 软件包注册表
17
17
18
18
为您的用户或组织发布 [Conda](https://docs.conda.io/en/latest/) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
+3
-7
docs/content/doc/usage/packages/container.en-us.md
docs/content/usage/packages/container.en-us.md
+3
-7
docs/content/doc/usage/packages/container.en-us.md
docs/content/usage/packages/container.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Container Registry"
4
4
slug: "container"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Container Registry"
12
-
weight: 30
12
+
sidebar_position: 30
13
13
identifier: "container"
14
14
---
15
15
···
18
18
Publish [Open Container Initiative](https://opencontainers.org/) compliant images for your user or organization.
19
19
The container registry follows the OCI specs and supports all compatible images like [Docker](https://www.docker.com/) and [Helm Charts](https://helm.sh/).
20
20
21
-
**Table of Contents**
22
-
23
-
{{< toc >}}
24
-
25
21
## Requirements
26
22
27
23
To work with the Container registry, you can use the tools for your specific image type.
···
35
31
docker login gitea.example.com
36
32
```
37
33
38
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
34
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
39
35
40
36
## Image naming convention
41
37
+3
-7
docs/content/doc/usage/packages/container.zh-cn.md
docs/content/usage/packages/container.zh-cn.md
+3
-7
docs/content/doc/usage/packages/container.zh-cn.md
docs/content/usage/packages/container.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "容器注册表"
4
4
slug: "container"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "容器"
12
-
weight: 30
12
+
sidebar_position: 30
13
13
identifier: "container"
14
14
---
15
15
···
18
18
为您的用户或组织发布符合 [Open Container Initiative(OCI)](https://opencontainers.org/) 规范的镜像。
19
19
该容器注册表遵循 OCI 规范，并支持所有兼容的镜像类型，如 [Docker](https://www.docker.com/) 和 [Helm Charts](https://helm.sh/)。
20
20
21
-
**目录**
22
-
23
-
{{< toc >}}
24
-
25
21
## 目录
26
22
27
23
要使用容器注册表，您可以使用适用于特定镜像类型的工具。
···
35
31
docker login gitea.example.com
36
32
```
37
33
38
-
如果您使用的是 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码进行身份验证。
34
+
如果您使用的是 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码进行身份验证。
39
35
40
36
## 镜像命名约定
41
37
+1
-5
docs/content/doc/usage/packages/cran.en-us.md
docs/content/usage/packages/cran.en-us.md
+1
-5
docs/content/doc/usage/packages/cran.en-us.md
docs/content/usage/packages/cran.en-us.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "CRAN"
11
-
weight: 35
11
+
sidebar_position: 35
12
12
identifier: "cran"
13
13
---
14
14
15
15
# CRAN Package Registry
16
16
17
17
Publish [R](https://www.r-project.org/) packages to a [CRAN](https://cran.r-project.org/)-like registry for your user or organization.
18
-
19
-
**Table of Contents**
20
-
21
-
{{< toc >}}
22
18
23
19
## Requirements
24
20
+1
-5
docs/content/doc/usage/packages/cran.zh-cn.md
docs/content/usage/packages/cran.zh-cn.md
+1
-5
docs/content/doc/usage/packages/cran.zh-cn.md
docs/content/usage/packages/cran.zh-cn.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "CRAN"
11
-
weight: 35
11
+
sidebar_position: 35
12
12
identifier: "cran"
13
13
---
14
14
15
15
# CRAN 软件包注册表
16
16
17
17
将 [R](https://www.r-project.org/) 软件包发布到您的用户或组织的类似 [CRAN](https://cran.r-project.org/) 的注册表。
18
-
19
-
**目录**
20
-
21
-
{{< toc >}}
22
18
23
19
## 要求
24
20
+3
-7
docs/content/doc/usage/packages/debian.en-us.md
docs/content/usage/packages/debian.en-us.md
+3
-7
docs/content/doc/usage/packages/debian.en-us.md
docs/content/usage/packages/debian.en-us.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "Debian"
11
-
weight: 35
11
+
sidebar_position: 35
12
12
identifier: "debian"
13
13
---
14
14
15
15
# Debian Package Registry
16
16
17
17
Publish [Debian](https://www.debian.org/distrib/packages) packages for your user or organization.
18
-
19
-
**Table of Contents**
20
-
21
-
{{< toc >}}
22
18
23
19
## Requirements
24
20
···
40
36
| `distribution` | The distribution to use. |
41
37
| `component` | The component to use. |
42
38
43
-
If the registry is private, provide credentials in the url. You can use a password or a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}):
39
+
If the registry is private, provide credentials in the url. You can use a password or a [personal access token](development/api-usage.md#authentication):
44
40
45
41
```shell
46
42
echo "deb https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/debian {distribution} {component}" | sudo tee -a /etc/apt/sources.list.d/gitea.list
···
80
76
https://gitea.example.com/api/packages/testuser/debian/pool/bionic/main/upload
81
77
```
82
78
83
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
79
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
84
80
You cannot publish a file with the same name twice to a package. You must delete the existing package version first.
85
81
86
82
The server responds with the following HTTP Status codes.
+3
-7
docs/content/doc/usage/packages/debian.zh-cn.md
docs/content/usage/packages/debian.zh-cn.md
+3
-7
docs/content/doc/usage/packages/debian.zh-cn.md
docs/content/usage/packages/debian.zh-cn.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "Debian"
11
-
weight: 35
11
+
sidebar_position: 35
12
12
identifier: "debian"
13
13
---
14
14
15
15
# Debian 软件包注册表
16
16
17
17
为您的用户或组织发布 [Debian](https://www.debian.org/distrib/packages) 软件包。
18
-
19
-
**目录**
20
-
21
-
{{< toc >}}
22
18
23
19
## 要求
24
20
···
40
36
| `distribution` | 要使用的发行版 |
41
37
| `component` | 要使用的组件 |
42
38
43
-
如果注册表是私有的，请在 URL 中提供凭据。您可以使用密码或[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})：
39
+
如果注册表是私有的，请在 URL 中提供凭据。您可以使用密码或[个人访问令牌](development/api-usage.md#通过-api-认证)：
44
40
45
41
```shell
46
42
echo "deb https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/debian {distribution} {component}" | sudo tee -a /etc/apt/sources.list.d/gitea.list
···
80
76
https://gitea.example.com/api/packages/testuser/debian/pool/bionic/main/upload
81
77
```
82
78
83
-
如果您使用 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码。
79
+
如果您使用 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码。
84
80
您无法向软件包中多次发布具有相同名称的文件。您必须首先删除现有的软件包版本。
85
81
86
82
服务器将使用以下 HTTP 状态代码进行响应。
+4
-8
docs/content/doc/usage/packages/generic.en-us.md
docs/content/usage/packages/generic.en-us.md
+4
-8
docs/content/doc/usage/packages/generic.en-us.md
docs/content/usage/packages/generic.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Generic Package Registry"
4
4
slug: "generic"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Generic"
12
-
weight: 40
12
+
sidebar_position: 40
13
13
identifier: "generic"
14
14
---
15
15
···
17
17
18
18
Publish generic files, like release binaries or other output, for your user or organization.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Authenticate to the package registry
25
21
26
-
To authenticate to the Package Registry, you need to provide [custom HTTP headers or use HTTP Basic authentication]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}).
22
+
To authenticate to the Package Registry, you need to provide [custom HTTP headers or use HTTP Basic authentication](development/api-usage.md#authentication).
27
23
28
24
## Publish a package
29
25
···
49
45
https://gitea.example.com/api/packages/testuser/generic/test_package/1.0.0/file.bin
50
46
```
51
47
52
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
48
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
53
49
54
50
The server responds with the following HTTP Status codes.
55
51
+4
-8
docs/content/doc/usage/packages/generic.zh-cn.md
docs/content/usage/packages/generic.zh-cn.md
+4
-8
docs/content/doc/usage/packages/generic.zh-cn.md
docs/content/usage/packages/generic.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "通用软件包注册表"
4
4
slug: "generic"
5
-
weight: 40
5
+
sidebar_position: 40
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "通用"
12
-
weight: 40
12
+
sidebar_position: 40
13
13
identifier: "generic"
14
14
---
15
15
···
17
17
18
18
发布通用文件，如发布二进制文件或其他输出，供您的用户或组织使用。
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 身份验证软件包注册表
25
21
26
-
要身份验证软件包注册表，您需要提供[自定义 HTTP 头或使用 HTTP 基本身份验证]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})。
22
+
要身份验证软件包注册表，您需要提供[自定义 HTTP 头或使用 HTTP 基本身份验证](development/api-usage.md#通过-api-认证)。
27
23
28
24
## 发布软件包
29
25
···
49
45
https://gitea.example.com/api/packages/testuser/generic/test_package/1.0.0/file.bin
50
46
```
51
47
52
-
如果您使用 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码。
48
+
如果您使用 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码。
53
49
54
50
服务器将使用以下 HTTP 状态代码进行响应。
55
51
+4
-8
docs/content/doc/usage/packages/go.en-us.md
docs/content/usage/packages/go.en-us.md
+4
-8
docs/content/doc/usage/packages/go.en-us.md
docs/content/usage/packages/go.en-us.md
···
2
2
date: "2023-05-10T00:00:00+00:00"
3
3
title: "Go Package Registry"
4
4
slug: "go"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Go"
12
-
weight: 45
12
+
sidebar_position: 45
13
13
identifier: "go"
14
14
---
15
15
···
17
17
18
18
Publish Go packages for your user or organization.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Publish a package
25
21
26
22
To publish a Go package perform a HTTP `PUT` operation with the package content in the request body.
···
35
31
| --------- | ----------- |
36
32
| `owner` | The owner of the package. |
37
33
38
-
To authenticate to the package registry, you need to provide [custom HTTP headers or use HTTP Basic authentication]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}):
34
+
To authenticate to the package registry, you need to provide [custom HTTP headers or use HTTP Basic authentication](development/api-usage.md#authentication):
39
35
40
36
```shell
41
37
curl --user your_username:your_password_or_token \
···
43
39
https://gitea.example.com/api/packages/testuser/go/upload
44
40
```
45
41
46
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
42
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
47
43
48
44
The server responds with the following HTTP Status codes.
49
45
+4
-8
docs/content/doc/usage/packages/go.zh-cn.md
docs/content/usage/packages/go.zh-cn.md
+4
-8
docs/content/doc/usage/packages/go.zh-cn.md
docs/content/usage/packages/go.zh-cn.md
···
2
2
date: "2023-05-10T00:00:00+00:00"
3
3
title: "Go 软件包注册表"
4
4
slug: "go"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Go"
12
-
weight: 45
12
+
sidebar_position: 45
13
13
identifier: "go"
14
14
---
15
15
···
17
17
18
18
为您的用户或组织发布 Go 软件包。
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 发布软件包
25
21
26
22
要发布 Go 软件包，请执行 HTTP `PUT` 操作，并将软件包内容放入请求主体中。
···
35
31
| ------- | -------------- |
36
32
| `owner` | 软件包的所有者 |
37
33
38
-
要身份验证到软件包注册表，您需要提供[自定义 HTTP 头或使用 HTTP 基本身份验证]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})：
34
+
要身份验证到软件包注册表，您需要提供[自定义 HTTP 头或使用 HTTP 基本身份验证](development/api-usage.md#通过-api-认证)：
39
35
40
36
```shell
41
37
curl --user your_username:your_password_or_token \
···
43
39
https://gitea.example.com/api/packages/testuser/go/upload
44
40
```
45
41
46
-
如果您使用的是 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码进行身份验证。
42
+
如果您使用的是 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码进行身份验证。
47
43
48
44
服务器将使用以下 HTTP 状态代码进行响应。
49
45
+3
-7
docs/content/doc/usage/packages/helm.en-us.md
docs/content/usage/packages/helm.en-us.md
+3
-7
docs/content/doc/usage/packages/helm.en-us.md
docs/content/usage/packages/helm.en-us.md
···
2
2
date: "2022-04-14T00:00:00+00:00"
3
3
title: "Helm Chart Registry"
4
4
slug: "helm"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Helm"
12
-
weight: 50
12
+
sidebar_position: 50
13
13
identifier: "helm"
14
14
---
15
15
16
16
# Helm Chart Registry
17
17
18
18
Publish [Helm](https://helm.sh/) charts for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
43
39
| Parameter | Description |
44
40
| ------------ | ----------- |
45
41
| `username` | Your Gitea username. |
46
-
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. |
42
+
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password. |
47
43
| `repo` | The name for the repository. |
48
44
| `chart_file` | The Helm Chart archive. |
49
45
| `owner` | The owner of the package. |
+3
-7
docs/content/doc/usage/packages/helm.zh-cn.md
docs/content/usage/packages/helm.zh-cn.md
+3
-7
docs/content/doc/usage/packages/helm.zh-cn.md
docs/content/usage/packages/helm.zh-cn.md
···
2
2
date: "2022-04-14T00:00:00+00:00"
3
3
title: "Helm Chart 注册表"
4
4
slug: "helm"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Helm"
12
-
weight: 50
12
+
sidebar_position: 50
13
13
identifier: "helm"
14
14
---
15
15
16
16
# Helm Chart 注册表
17
17
18
18
为您的用户或组织发布 [Helm](https://helm.sh/) charts。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
43
39
| 参数 | 描述 |
44
40
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
45
41
| `username` | 您的Gitea用户名 |
46
-
| `password` | 您的Gitea密码。如果您使用的是2FA或OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码进行身份验证。 |
42
+
| `password` | 您的Gitea密码。如果您使用的是2FA或OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码进行身份验证。 |
47
43
| `repo` | 仓库名称 |
48
44
| `chart_file` | Helm Chart 归档文件 |
49
45
| `owner` | 软件包的所有者 |
+3
-7
docs/content/doc/usage/packages/maven.en-us.md
docs/content/usage/packages/maven.en-us.md
+3
-7
docs/content/doc/usage/packages/maven.en-us.md
docs/content/usage/packages/maven.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Maven Package Registry"
4
4
slug: "maven"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Maven"
12
-
weight: 60
12
+
sidebar_position: 60
13
13
identifier: "maven"
14
14
---
15
15
16
16
# Maven Package Registry
17
17
18
18
Publish [Maven](https://maven.apache.org) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
71
67
72
68
| Parameter | Description |
73
69
| -------------- | ----------- |
74
-
| `access_token` | Your [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}). |
70
+
| `access_token` | Your [personal access token](development/api-usage.md#authentication). |
75
71
| `owner` | The owner of the package. |
76
72
77
73
### Gradle variant
+3
-7
docs/content/doc/usage/packages/maven.zh-cn.md
docs/content/usage/packages/maven.zh-cn.md
+3
-7
docs/content/doc/usage/packages/maven.zh-cn.md
docs/content/usage/packages/maven.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Maven 软件包注册表"
4
4
slug: "maven"
5
-
weight: 60
5
+
sidebar_position: 60
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Maven"
12
-
weight: 60
12
+
sidebar_position: 60
13
13
identifier: "maven"
14
14
---
15
15
16
16
# Maven 软件包注册表
17
17
18
18
为您的用户或组织发布 [Maven](https://maven.apache.org) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
71
67
72
68
| 参数 | 描述 |
73
69
| -------------- | ------------------------------------------------------------------------------------- |
74
-
| `access_token` | 您的[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}}) |
70
+
| `access_token` | 您的[个人访问令牌](development/api-usage.md#通过-api-认证) |
75
71
| `owner` | 软件包的所有者 |
76
72
77
73
### Gradle variant
+3
-7
docs/content/doc/usage/packages/npm.en-us.md
docs/content/usage/packages/npm.en-us.md
+3
-7
docs/content/doc/usage/packages/npm.en-us.md
docs/content/usage/packages/npm.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "npm Package Registry"
4
4
slug: "npm"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "npm"
12
-
weight: 70
12
+
sidebar_position: 70
13
13
identifier: "npm"
14
14
---
15
15
16
16
# npm Package Registry
17
17
18
18
Publish [npm](https://www.npmjs.com/) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
42
38
| ------------ | ----------- |
43
39
| `scope` | The scope of the packages. |
44
40
| `owner` | The owner of the package. |
45
-
| `token` | Your [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}). |
41
+
| `token` | Your [personal access token](development/api-usage.md#authentication). |
46
42
47
43
For example:
48
44
+3
-7
docs/content/doc/usage/packages/npm.zh-cn.md
docs/content/usage/packages/npm.zh-cn.md
+3
-7
docs/content/doc/usage/packages/npm.zh-cn.md
docs/content/usage/packages/npm.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "npm 软件包注册表"
4
4
slug: "npm"
5
-
weight: 70
5
+
sidebar_position: 70
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "npm"
12
-
weight: 70
12
+
sidebar_position: 70
13
13
identifier: "npm"
14
14
---
15
15
16
16
# npm Package Registry
17
17
18
18
为您的用户或组织发布 [npm](https://www.npmjs.com/) 包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
42
38
| ------- | --------------------------------------------------------------------------------------- |
43
39
| `scope` | 软件包的作用域 |
44
40
| `owner` | 软件包的所有者 |
45
-
| `token` | 您的[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})。 |
41
+
| `token` | 您的[个人访问令牌](development/api-usage.md#通过-api-认证)。 |
46
42
47
43
例如：
48
44
+4
-8
docs/content/doc/usage/packages/nuget.en-us.md
docs/content/usage/packages/nuget.en-us.md
+4
-8
docs/content/doc/usage/packages/nuget.en-us.md
docs/content/usage/packages/nuget.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "NuGet Package Registry"
4
4
slug: "nuget"
5
-
weight: 80
5
+
sidebar_position: 80
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "NuGet"
12
-
weight: 80
12
+
sidebar_position: 80
13
13
identifier: "nuget"
14
14
---
15
15
···
17
17
18
18
Publish [NuGet](https://www.nuget.org/) packages for your user or organization. The package registry supports the V2 and V3 API protocol and you can work with [NuGet Symbol Packages](https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg) too.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Requirements
25
21
26
22
To work with the NuGet package registry, you can use command-line interface tools as well as NuGet features in various IDEs like Visual Studio.
···
39
35
| ------------- | ----------- |
40
36
| `source_name` | The desired source name. |
41
37
| `username` | Your Gitea username. |
42
-
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. |
38
+
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password. |
43
39
| `owner` | The owner of the package. |
44
40
45
41
For example:
···
48
44
dotnet nuget add source --name gitea --username testuser --password password123 https://gitea.example.com/api/packages/testuser/nuget/index.json
49
45
```
50
46
51
-
You can add the source without credentials and use the [`--api-key`](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-push) parameter when publishing packages. In this case you need to provide a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}).
47
+
You can add the source without credentials and use the [`--api-key`](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-push) parameter when publishing packages. In this case you need to provide a [personal access token](development/api-usage.md#authentication).
52
48
53
49
## Publish a package
54
50
+4
-8
docs/content/doc/usage/packages/nuget.zh-cn.md
docs/content/usage/packages/nuget.zh-cn.md
+4
-8
docs/content/doc/usage/packages/nuget.zh-cn.md
docs/content/usage/packages/nuget.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "NuGet 软件包注册表"
4
4
slug: "nuget"
5
-
weight: 80
5
+
sidebar_position: 80
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "NuGet"
12
-
weight: 80
12
+
sidebar_position: 80
13
13
identifier: "nuget"
14
14
---
15
15
···
17
17
18
18
发布适用于您的用户或组织的 [NuGet](https://www.nuget.org/) 软件包。软件包注册表支持 V2 和 V3 API 协议，并且您还可以使用 [NuGet 符号软件包](https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg)。
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 要求
25
21
26
22
要使用 NuGet 软件包注册表，您可以使用命令行界面工具，以及各种集成开发环境（IDE）中的 NuGet 功能，如 Visual Studio。有关 NuGet 客户端的更多信息，请参[阅官方文档](https://docs.microsoft.com/en-us/nuget/install-nuget-client-tools)。
···
38
34
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
39
35
| `source_name` | 所需源名称 |
40
36
| `username` | 您的Gitea用户名 |
41
-
| `password` | 您的Gitea密码。如果您使用2FA或OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})代替密码。 |
37
+
| `password` | 您的Gitea密码。如果您使用2FA或OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)代替密码。 |
42
38
| `owner` | 软件包的所有者 |
43
39
44
40
例如：
···
47
43
dotnet nuget add source --name gitea --username testuser --password password123 https://gitea.example.com/api/packages/testuser/nuget/index.json
48
44
```
49
45
50
-
您可以在不提供凭据的情况下添加源，并在发布软件包时使用--api-key参数。在这种情况下，您需要提供[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})。
46
+
您可以在不提供凭据的情况下添加源，并在发布软件包时使用--api-key参数。在这种情况下，您需要提供[个人访问令牌](development/api-usage.md#通过-api-认证)。
51
47
52
48
## 发布软件包
53
49
+23
-27
docs/content/doc/usage/packages/overview.en-us.md
docs/content/usage/packages/overview.en-us.md
+23
-27
docs/content/doc/usage/packages/overview.en-us.md
docs/content/usage/packages/overview.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "Package Registry"
4
4
slug: "overview"
5
-
weight: 1
5
+
sidebar_position: 1
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Overview"
12
-
weight: 1
12
+
sidebar_position: 1
13
13
identifier: "packages-overview"
14
14
---
15
15
···
17
17
18
18
Starting with Gitea **1.17**, the Package Registry can be used as a public or private registry for common package managers.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Supported package managers
25
21
26
22
The following package managers are currently supported:
27
23
28
24
| Name | Language | Package client |
29
25
| ---- | -------- | -------------- |
30
-
| [Alpine]({{< relref "doc/usage/packages/alpine.en-us.md" >}}) | - | `apk` |
31
-
| [Cargo]({{< relref "doc/usage/packages/cargo.en-us.md" >}}) | Rust | `cargo` |
32
-
| [Chef]({{< relref "doc/usage/packages/chef.en-us.md" >}}) | - | `knife` |
33
-
| [Composer]({{< relref "doc/usage/packages/composer.en-us.md" >}}) | PHP | `composer` |
34
-
| [Conan]({{< relref "doc/usage/packages/conan.en-us.md" >}}) | C++ | `conan` |
35
-
| [Conda]({{< relref "doc/usage/packages/conda.en-us.md" >}}) | - | `conda` |
36
-
| [Container]({{< relref "doc/usage/packages/container.en-us.md" >}}) | - | any OCI compliant client |
37
-
| [CRAN]({{< relref "doc/usage/packages/cran.en-us.md" >}}) | R | - |
38
-
| [Debian]({{< relref "doc/usage/packages/debian.en-us.md" >}}) | - | `apt` |
39
-
| [Generic]({{< relref "doc/usage/packages/generic.en-us.md" >}}) | - | any HTTP client |
40
-
| [Go]({{< relref "doc/usage/packages/go.en-us.md" >}}) | Go | `go` |
41
-
| [Helm]({{< relref "doc/usage/packages/helm.en-us.md" >}}) | - | any HTTP client, `cm-push` |
42
-
| [Maven]({{< relref "doc/usage/packages/maven.en-us.md" >}}) | Java | `mvn`, `gradle` |
43
-
| [npm]({{< relref "doc/usage/packages/npm.en-us.md" >}}) | JavaScript | `npm`, `yarn`, `pnpm` |
44
-
| [NuGet]({{< relref "doc/usage/packages/nuget.en-us.md" >}}) | .NET | `nuget` |
45
-
| [Pub]({{< relref "doc/usage/packages/pub.en-us.md" >}}) | Dart | `dart`, `flutter` |
46
-
| [PyPI]({{< relref "doc/usage/packages/pypi.en-us.md" >}}) | Python | `pip`, `twine` |
47
-
| [RPM]({{< relref "doc/usage/packages/rpm.en-us.md" >}}) | - | `yum`, `dnf`, `zypper` |
48
-
| [RubyGems]({{< relref "doc/usage/packages/rubygems.en-us.md" >}}) | Ruby | `gem`, `Bundler` |
49
-
| [Swift]({{< relref "doc/usage/packages/rubygems.en-us.md" >}}) | Swift | `swift` |
50
-
| [Vagrant]({{< relref "doc/usage/packages/vagrant.en-us.md" >}}) | - | `vagrant` |
26
+
| [Alpine](usage/packages/alpine.md) | - | `apk` |
27
+
| [Cargo](usage/packages/cargo.md) | Rust | `cargo` |
28
+
| [Chef](usage/packages/chef.md) | - | `knife` |
29
+
| [Composer](usage/packages/composer.md) | PHP | `composer` |
30
+
| [Conan](usage/packages/conan.md) | C++ | `conan` |
31
+
| [Conda](usage/packages/conda.md) | - | `conda` |
32
+
| [Container](usage/packages/container.md) | - | any OCI compliant client |
33
+
| [CRAN](usage/packages/cran.md) | R | - |
34
+
| [Debian](usage/packages/debian.md) | - | `apt` |
35
+
| [Generic](usage/packages/generic.md) | - | any HTTP client |
36
+
| [Go](usage/packages/go.md) | Go | `go` |
37
+
| [Helm](usage/packages/helm.md) | - | any HTTP client, `cm-push` |
38
+
| [Maven](usage/packages/maven.md) | Java | `mvn`, `gradle` |
39
+
| [npm](usage/packages/npm.md) | JavaScript | `npm`, `yarn`, `pnpm` |
40
+
| [NuGet](usage/packages/nuget.md) | .NET | `nuget` |
41
+
| [Pub](usage/packages/pub.md) | Dart | `dart`, `flutter` |
42
+
| [PyPI](usage/packages/pypi.md) | Python | `pip`, `twine` |
43
+
| [RPM](usage/packages/rpm.md) | - | `yum`, `dnf`, `zypper` |
44
+
| [RubyGems](usage/packages/rubygems.md) | Ruby | `gem`, `Bundler` |
45
+
| [Swift](usage/packages/rubygems.md) | Swift | `swift` |
46
+
| [Vagrant](usage/packages/vagrant.md) | - | `vagrant` |
51
47
52
48
**The following paragraphs only apply if Packages are not globally disabled!**
53
49
-109
docs/content/doc/usage/packages/overview.zh-cn.md
-109
docs/content/doc/usage/packages/overview.zh-cn.md
···
1
-
---
2
-
date: "2021-07-20T00:00:00+00:00"
3
-
title: "软件包注册表"
4
-
slug: "overview"
5
-
weight: 1
6
-
draft: false
7
-
toc: false
8
-
menu:
9
-
sidebar:
10
-
parent: "packages"
11
-
name: "Overview"
12
-
weight: 1
13
-
identifier: "packages-overview"
14
-
---
15
-
16
-
# 软件包注册表
17
-
18
-
从Gitea **1.17**版本开始，软件包注册表可以用作常见软件包管理器的公共或私有注册表。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
-
## 支持的软件包管理器
25
-
26
-
目前支持以下软件包管理器：
27
-
28
-
| Name | Language | Package client |
29
-
| ------------------------------------------------------------------- | ---------- | ------------------------- |
30
-
| [Alpine]({{< relref "doc/usage/packages/alpine.zh-cn.md" >}}) | - | `apk` |
31
-
| [Cargo]({{< relref "doc/usage/packages/cargo.zh-cn.md" >}}) | Rust | `cargo` |
32
-
| [Chef]({{< relref "doc/usage/packages/chef.zh-cn.md" >}}) | - | `knife` |
33
-
| [Composer]({{< relref "doc/usage/packages/composer.zh-cn.md" >}}) | PHP | `composer` |
34
-
| [Conan]({{< relref "doc/usage/packages/conan.zh-cn.md" >}}) | C++ | `conan` |
35
-
| [Conda]({{< relref "doc/usage/packages/conda.zh-cn.md" >}}) | - | `conda` |
36
-
| [Container]({{< relref "doc/usage/packages/container.zh-cn.md" >}}) | - | 任何符合OCI规范的客户端 |
37
-
| [CRAN]({{< relref "doc/usage/packages/cran.zh-cn.md" >}}) | R | - |
38
-
| [Debian]({{< relref "doc/usage/packages/debian.zh-cn.md" >}}) | - | `apt` |
39
-
| [Generic]({{< relref "doc/usage/packages/generic.zh-cn.md" >}}) | - | 任何HTTP客户端 |
40
-
| [Go]({{< relref "doc/usage/packages/go.zh-cn.md" >}}) | Go | `go` |
41
-
| [Helm]({{< relref "doc/usage/packages/helm.zh-cn.md" >}}) | - | 任何HTTP客户端, `cm-push` |
42
-
| [Maven]({{< relref "doc/usage/packages/maven.zh-cn.md" >}}) | Java | `mvn`, `gradle` |
43
-
| [npm]({{< relref "doc/usage/packages/npm.zh-cn.md" >}}) | JavaScript | `npm`, `yarn`, `pnpm` |
44
-
| [NuGet]({{< relref "doc/usage/packages/nuget.zh-cn.md" >}}) | .NET | `nuget` |
45
-
| [Pub]({{< relref "doc/usage/packages/pub.zh-cn.md" >}}) | Dart | `dart`, `flutter` |
46
-
| [PyPI]({{< relref "doc/usage/packages/pypi.zh-cn.md" >}}) | Python | `pip`, `twine` |
47
-
| [RPM]({{< relref "doc/usage/packages/rpm.zh-cn.md" >}}) | - | `yum`, `dnf`, `zypper` |
48
-
| [RubyGems]({{< relref "doc/usage/packages/rubygems.zh-cn.md" >}}) | Ruby | `gem`, `Bundler` |
49
-
| [Swift]({{< relref "doc/usage/packages/rubygems.zh-cn.md" >}}) | Swift | `swift` |
50
-
| [Vagrant]({{< relref "doc/usage/packages/vagrant.zh-cn.md" >}}) | - | `vagrant` |
51
-
52
-
**以下段落仅适用于未全局禁用软件包的情况！**
53
-
54
-
## 仓库 x 软件包
55
-
56
-
软件包始终属于所有者（用户或组织），而不是仓库。
57
-
要将（已上传的）软件包链接到仓库，请打开该软件包的设置页面，并选择要将此软件包链接到的仓库。
58
-
将链接到整个软件包，而不仅是单个版本。
59
-
60
-
链接软件包将导致在仓库的软件包列表中显示该软件包，并在软件包页面上显示到仓库的链接（以及到仓库工单的链接）。
61
-
62
-
## 访问限制
63
-
64
-
| 软件包所有者类型 | 用户 | 组织 |
65
-
| ---------------- | ---------------------------------------- | ------------------------------------------ |
66
-
| **读取** 访问 | 公开，如果用户也是公开的；否则仅限此用户 | 公开，如果组织是公开的，否则仅限组织成员 |
67
-
| **写入** 访问 | 仅软件包所有者 | 具有组织中的管理员或写入访问权限的组织成员 |
68
-
69
-
注意：这些访问限制可能会[变化](https://github.com/go-gitea/gitea/issues/19270)，将通过专门的组织团队权限添加更细粒度的控制。
70
-
71
-
## 创建或上传软件包
72
-
73
-
根据软件包类型，使用相应的软件包管理器。请查看特定软件包管理器的子页面以获取说明。
74
-
75
-
## 查看软件包
76
-
77
-
您可以在仓库页面上查看仓库的软件包。
78
-
79
-
1. 转到仓库主页。
80
-
2. 在导航栏中选择**软件包**
81
-
82
-
要查看有关软件包的更多详细信息，请选择软件包的名称。
83
-
84
-
## 下载软件包
85
-
86
-
要从仓库下载软件包：
87
-
88
-
1. 在导航栏中选择**软件包**
89
-
2. 选择软件包的名称以查看详细信息。
90
-
3. 在 **Assets** 部分，选择要下载的软件包文件的名称。
91
-
92
-
## 删除软件包
93
-
94
-
在将软件包发布到软件包注册表后，您无法编辑软件包。相反，您必须删除并重新创建它。
95
-
96
-
要从仓库中删除软件包：
97
-
98
-
1. 在导航栏中选择**软件包**
99
-
2. 选择软件包的名称以查看详细信息。
100
-
3. 单击**删除软件包**以永久删除软件包。
101
-
102
-
## 禁用软件包注册表
103
-
104
-
包注册表已自动启用。要在单个存储库中禁用它：
105
-
106
-
1. 在导航栏中选择**设置**。
107
-
2. 禁用**启用仓库软件包注册表**.
108
-
109
-
禁用软件包注册表不会删除先前发布的软件包。
+3
-7
docs/content/doc/usage/packages/pub.en-us.md
docs/content/usage/packages/pub.en-us.md
+3
-7
docs/content/doc/usage/packages/pub.en-us.md
docs/content/usage/packages/pub.en-us.md
···
2
2
date: "2022-07-31T00:00:00+00:00"
3
3
title: "Pub Package Registry"
4
4
slug: "pub"
5
-
weight: 90
5
+
sidebar_position: 90
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Pub"
12
-
weight: 90
12
+
sidebar_position: 90
13
13
identifier: "pub"
14
14
---
15
15
16
16
# Pub Package Registry
17
17
18
18
Publish [Pub](https://dart.dev/guides/packages) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
39
35
| ------------ | ----------- |
40
36
| `owner` | The owner of the package. |
41
37
42
-
You need to provide your [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}).
38
+
You need to provide your [personal access token](development/api-usage.md#authentication).
43
39
44
40
## Publish a package
45
41
+3
-7
docs/content/doc/usage/packages/pub.zh-cn.md
docs/content/usage/packages/pub.zh-cn.md
+3
-7
docs/content/doc/usage/packages/pub.zh-cn.md
docs/content/usage/packages/pub.zh-cn.md
···
2
2
date: "2022-07-31T00:00:00+00:00"
3
3
title: "Pub 软件包注册表"
4
4
slug: "pub"
5
-
weight: 90
5
+
sidebar_position: 90
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Pub"
12
-
weight: 90
12
+
sidebar_position: 90
13
13
identifier: "pub"
14
14
---
15
15
16
16
# Pub 软件包注册表
17
17
18
18
为您的用户或组织发布 [Pub](https://dart.dev/guides/packages) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
39
35
| ------- | -------------- |
40
36
| `owner` | 软件包的所有者 |
41
37
42
-
您需要提供您的[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})。
38
+
您需要提供您的[个人访问令牌](development/api-usage.md#通过-api-认证)。
43
39
44
40
## 发布软件包
45
41
+3
-7
docs/content/doc/usage/packages/pypi.en-us.md
docs/content/usage/packages/pypi.en-us.md
+3
-7
docs/content/doc/usage/packages/pypi.en-us.md
docs/content/usage/packages/pypi.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "PyPI Package Registry"
4
4
slug: "pypi"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "PyPI"
12
-
weight: 100
12
+
sidebar_position: 100
13
13
identifier: "pypi"
14
14
---
15
15
16
16
# PyPI Package Registry
17
17
18
18
Publish [PyPI](https://pypi.org/) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
43
39
| ------------ | ----------- |
44
40
| `owner` | The owner of the package. |
45
41
| `username` | Your Gitea username. |
46
-
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. |
42
+
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password. |
47
43
48
44
## Publish a package
49
45
+3
-7
docs/content/doc/usage/packages/pypi.zh-cn.md
docs/content/usage/packages/pypi.zh-cn.md
+3
-7
docs/content/doc/usage/packages/pypi.zh-cn.md
docs/content/usage/packages/pypi.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "PyPI 软件包注册表"
4
4
slug: "pypi"
5
-
weight: 100
5
+
sidebar_position: 100
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "PyPI"
12
-
weight: 100
12
+
sidebar_position: 100
13
13
identifier: "pypi"
14
14
---
15
15
16
16
# PyPI 软件包注册表
17
17
18
18
为您的用户或组织发布 [PyPI](https://pypi.org/) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
43
39
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
44
40
| `owner` | 软件包的所有者 |
45
41
| `username` | 您的 Gitea 用户名 |
46
-
| `password` | 您的 Gitea 密码。如果您使用 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码 |
42
+
| `password` | 您的 Gitea 密码。如果您使用 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码 |
47
43
48
44
## 发布软件包
49
45
+3
-7
docs/content/doc/usage/packages/rpm.en-us.md
docs/content/usage/packages/rpm.en-us.md
+3
-7
docs/content/doc/usage/packages/rpm.en-us.md
docs/content/usage/packages/rpm.en-us.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "RPM"
11
-
weight: 105
11
+
sidebar_position: 105
12
12
identifier: "rpm"
13
13
---
14
14
···
16
16
17
17
Publish [RPM](https://rpm.org/) packages for your user or organization.
18
18
19
-
**Table of Contents**
20
-
21
-
{{< toc >}}
22
-
23
19
## Requirements
24
20
25
21
To work with the RPM registry, you need to use a package manager like `yum`, `dnf` or `zypper` to consume packages.
···
38
34
| ----------- | ----------- |
39
35
| `owner` | The owner of the package. |
40
36
41
-
If the registry is private, provide credentials in the url. You can use a password or a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}):
37
+
If the registry is private, provide credentials in the url. You can use a password or a [personal access token](development/api-usage.md#authentication):
42
38
43
39
```shell
44
40
dnf config-manager --add-repo https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/rpm.repo
···
66
62
https://gitea.example.com/api/packages/testuser/rpm/upload
67
63
```
68
64
69
-
If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password.
65
+
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
70
66
You cannot publish a file with the same name twice to a package. You must delete the existing package version first.
71
67
72
68
The server responds with the following HTTP Status codes.
+3
-7
docs/content/doc/usage/packages/rpm.zh-cn.md
docs/content/usage/packages/rpm.zh-cn.md
+3
-7
docs/content/doc/usage/packages/rpm.zh-cn.md
docs/content/usage/packages/rpm.zh-cn.md
···
8
8
sidebar:
9
9
parent: "packages"
10
10
name: "RPM"
11
-
weight: 105
11
+
sidebar_position: 105
12
12
identifier: "rpm"
13
13
---
14
14
···
16
16
17
17
为您的用户或组织发布 [RPM](https://rpm.org/) 软件包。
18
18
19
-
**目录**
20
-
21
-
{{< toc >}}
22
-
23
19
## 要求
24
20
25
21
要使用RPM注册表，您需要使用像 `yum`, `dnf` 或 `zypper` 这样的软件包管理器来消费软件包。
···
38
34
| ------- | -------------- |
39
35
| `owner` | 软件包的所有者 |
40
36
41
-
如果注册表是私有的，请在URL中提供凭据。您可以使用密码或[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})：
37
+
如果注册表是私有的，请在URL中提供凭据。您可以使用密码或[个人访问令牌](development/api-usage.md#通过-api-认证)：
42
38
43
39
```shell
44
40
dnf config-manager --add-repo https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/rpm.repo
···
66
62
https://gitea.example.com/api/packages/testuser/rpm/upload
67
63
```
68
64
69
-
如果您使用 2FA 或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})替代密码。您无法将具有相同名称的文件两次发布到软件包中。您必须先删除现有的软件包版本。
65
+
如果您使用 2FA 或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)替代密码。您无法将具有相同名称的文件两次发布到软件包中。您必须先删除现有的软件包版本。
70
66
71
67
服务器将以以下HTTP状态码响应。
72
68
+3
-7
docs/content/doc/usage/packages/rubygems.en-us.md
docs/content/usage/packages/rubygems.en-us.md
+3
-7
docs/content/doc/usage/packages/rubygems.en-us.md
docs/content/usage/packages/rubygems.en-us.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "RubyGems Package Registry"
4
4
slug: "rubygems"
5
-
weight: 110
5
+
sidebar_position: 110
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "RubyGems"
12
-
weight: 110
12
+
sidebar_position: 110
13
13
identifier: "rubygems"
14
14
---
15
15
···
17
17
18
18
Publish [RubyGems](https://guides.rubygems.org/) packages for your user or organization.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Requirements
25
21
26
22
To work with the RubyGems package registry, you need to use the [gem](https://guides.rubygems.org/command-reference/) command line tool to consume and publish packages.
···
37
33
| Parameter | Description |
38
34
| ------------- | ----------- |
39
35
| `owner` | The owner of the package. |
40
-
| `token` | Your [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}). |
36
+
| `token` | Your [personal access token](development/api-usage.md#authentication). |
41
37
42
38
For example:
43
39
+3
-7
docs/content/doc/usage/packages/rubygems.zh-cn.md
docs/content/usage/packages/rubygems.zh-cn.md
+3
-7
docs/content/doc/usage/packages/rubygems.zh-cn.md
docs/content/usage/packages/rubygems.zh-cn.md
···
2
2
date: "2021-07-20T00:00:00+00:00"
3
3
title: "RubyGems 软件包注册表"
4
4
slug: "rubygems"
5
-
weight: 110
5
+
sidebar_position: 110
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "RubyGems"
12
-
weight: 110
12
+
sidebar_position: 110
13
13
identifier: "rubygems"
14
14
---
15
15
···
17
17
18
18
为您的用户或组织发布 [RubyGems](https://guides.rubygems.org/) 软件包。
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 要求
25
21
26
22
要使用RubyGems软件包注册表，您需要使用 [gem](https://guides.rubygems.org/command-reference/) 命令行工具来消费和发布软件包。
···
37
33
| 参数 | 描述 |
38
34
| ------- | ------------------------------------------------------------------------------------- |
39
35
| `owner` | 软件包的所有者 |
40
-
| `token` | 您的[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}}) |
36
+
| `token` | 您的[个人访问令牌](development/api-usage.md#通过-api-认证) |
41
37
42
38
例如：
43
39
+4
-8
docs/content/doc/usage/packages/storage.en-us.md
docs/content/usage/packages/storage.en-us.md
+4
-8
docs/content/doc/usage/packages/storage.en-us.md
docs/content/usage/packages/storage.en-us.md
···
2
2
date: "2022-11-01T00:00:00+00:00"
3
3
title: "Storage"
4
4
slug: "storage"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Storage"
12
-
weight: 2
12
+
sidebar_position: 2
13
13
identifier: "storage"
14
14
---
15
15
···
17
17
18
18
This document describes the storage of the package registry and how it can be managed.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Deduplication
25
21
26
22
The package registry has a build-in deduplication of uploaded blobs.
···
32
28
The blobs get not removed at this moment, so they still require space on the filesystem.
33
29
When a new package gets uploaded the existing blobs may get referenced again.
34
30
35
-
These unreferenced blobs get deleted by a [clean up job]({{< relref "doc/administration/config-cheat-sheet.en-us.md#cron---cleanup-expired-packages-croncleanup_packages" >}}).
31
+
These unreferenced blobs get deleted by a [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages).
36
32
The config setting `OLDER_THAN` configures how long unreferenced blobs are kept before they get deleted.
37
33
38
34
## Cleanup Rules
···
72
68
73
69
### How the cleanup rules work
74
70
75
-
The cleanup rules are part of the [clean up job]({{< relref "doc/administration/config-cheat-sheet.en-us.md#cron---cleanup-expired-packages-croncleanup_packages" >}}) and run periodically.
71
+
The cleanup rules are part of the [clean up job](administration/config-cheat-sheet.md#cron---cleanup-expired-packages-croncleanup_packages) and run periodically.
76
72
77
73
The cleanup rule:
78
74
+2
-6
docs/content/doc/usage/packages/storage.zh-cn.md
docs/content/usage/packages/storage.zh-cn.md
+2
-6
docs/content/doc/usage/packages/storage.zh-cn.md
docs/content/usage/packages/storage.zh-cn.md
···
2
2
date: "2022-11-01T00:00:00+00:00"
3
3
title: "存储"
4
4
slug: "storage"
5
-
weight: 5
5
+
sidebar_position: 5
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Storage"
12
-
weight: 2
12
+
sidebar_position: 2
13
13
identifier: "storage"
14
14
---
15
15
16
16
# 存储
17
17
18
18
本文档描述了软件包注册表的存储方式以及如何管理存储。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 去重
25
21
+4
-8
docs/content/doc/usage/packages/swift.en-us.md
docs/content/usage/packages/swift.en-us.md
+4
-8
docs/content/doc/usage/packages/swift.en-us.md
docs/content/usage/packages/swift.en-us.md
···
2
2
date: "2023-01-10T00:00:00+00:00"
3
3
title: "Swift Package Registry"
4
4
slug: "swift"
5
-
weight: 95
5
+
sidebar_position: 95
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Swift"
12
-
weight: 95
12
+
sidebar_position: 95
13
13
identifier: "swift"
14
14
---
15
15
···
17
17
18
18
Publish [Swift](https://www.swift.org/) packages for your user or organization.
19
19
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
-
24
20
## Requirements
25
21
26
22
To work with the Swift package registry, you need to use [swift](https://www.swift.org/getting-started/) to consume and a HTTP client (like `curl`) to publish packages.
···
37
33
| ------------ | ----------- |
38
34
| `owner` | The owner of the package. |
39
35
| `username` | Your Gitea username. |
40
-
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. |
36
+
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password. |
41
37
42
38
The login is optional and only needed if the package registry is private.
43
39
···
62
58
| Placeholder | Description |
63
59
| ----------- | ----------- |
64
60
| `username` | Your Gitea username. |
65
-
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) instead of the password. |
61
+
| `password` | Your Gitea password. If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password. |
66
62
| `owner` | The owner of the package. |
67
63
| `scope` | The package scope. |
68
64
| `name` | The package name. |
+4
-8
docs/content/doc/usage/packages/swift.zh-cn.md
docs/content/usage/packages/swift.zh-cn.md
+4
-8
docs/content/doc/usage/packages/swift.zh-cn.md
docs/content/usage/packages/swift.zh-cn.md
···
2
2
date: "2023-01-10T00:00:00+00:00"
3
3
title: "Swift 软件包注册表"
4
4
slug: "swift"
5
-
weight: 95
5
+
sidebar_position: 95
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Swift"
12
-
weight: 95
12
+
sidebar_position: 95
13
13
identifier: "swift"
14
14
---
15
15
···
17
17
18
18
为您的用户或组织发布 [Swift](https://www.swift.org/) 软件包。
19
19
20
-
**目录**
21
-
22
-
{{< toc >}}
23
-
24
20
## 要求
25
21
26
22
要使用 Swift 软件包注册表，您需要使用 [swift](https://www.swift.org/getting-started/) 消费软件包，并使用 HTTP 客户端（如 `curl`）发布软件包。
···
37
33
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
38
34
| `owner` | 软件包的所有者。 |
39
35
| `username` | 您的 Gitea 用户名。 |
40
-
| `password` | 您的 Gitea 密码。如果您使用两步验证或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})代替密码。 |
36
+
| `password` | 您的 Gitea 密码。如果您使用两步验证或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)代替密码。 |
41
37
42
38
登录是可选的，只有在软件包注册表是私有的情况下才需要。
43
39
···
62
58
| 占位符 | 描述 |
63
59
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
64
60
| `username` | 您的 Gitea 用户名。 |
65
-
| `password` | 您的 Gitea 密码。如果您使用两步验证或 OAuth，请使用[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})代替密码。 |
61
+
| `password` | 您的 Gitea 密码。如果您使用两步验证或 OAuth，请使用[个人访问令牌](development/api-usage.md#通过-api-认证)代替密码。 |
66
62
| `owner` | 软件包的所有者。 |
67
63
| `scope` | 软件包的作用域。 |
68
64
| `name` | 软件包的名称。 |
+3
-7
docs/content/doc/usage/packages/vagrant.en-us.md
docs/content/usage/packages/vagrant.en-us.md
+3
-7
docs/content/doc/usage/packages/vagrant.en-us.md
docs/content/usage/packages/vagrant.en-us.md
···
2
2
date: "2022-08-23T00:00:00+00:00"
3
3
title: "Vagrant Package Registry"
4
4
slug: "vagrant"
5
-
weight: 120
5
+
sidebar_position: 120
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Vagrant"
12
-
weight: 120
12
+
sidebar_position: 120
13
13
identifier: "vagrant"
14
14
---
15
15
16
16
# Vagrant Package Registry
17
17
18
18
Publish [Vagrant](https://www.vagrantup.com/) packages for your user or organization.
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
## Requirements
25
21
···
70
66
```
71
67
72
68
This will install the latest version of the package. To add a specific version, use the `--box-version` parameter.
73
-
If the registry is private you can pass your [personal access token]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}) in the `VAGRANT_CLOUD_TOKEN` environment variable.
69
+
If the registry is private you can pass your [personal access token](development/api-usage.md#authentication) in the `VAGRANT_CLOUD_TOKEN` environment variable.
74
70
75
71
## Supported commands
76
72
+3
-7
docs/content/doc/usage/packages/vagrant.zh-cn.md
docs/content/usage/packages/vagrant.zh-cn.md
+3
-7
docs/content/doc/usage/packages/vagrant.zh-cn.md
docs/content/usage/packages/vagrant.zh-cn.md
···
2
2
date: "2022-08-23T00:00:00+00:00"
3
3
title: "Vagrant 软件包注册表"
4
4
slug: "vagrant"
5
-
weight: 120
5
+
sidebar_position: 120
6
6
draft: false
7
7
toc: false
8
8
menu:
9
9
sidebar:
10
10
parent: "packages"
11
11
name: "Vagrant"
12
-
weight: 120
12
+
sidebar_position: 120
13
13
identifier: "vagrant"
14
14
---
15
15
16
16
# Vagrant 软件包注册表
17
17
18
18
为您的用户或组织发布 [Vagrant](https://www.vagrantup.com/) 软件包。
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
## 要求
25
21
···
70
66
```
71
67
72
68
这将安装软件包的最新版本。要添加特定版本，请使用` --box-version` 参数。
73
-
如果注册表是私有的，您可以将您的[个人访问令牌]({{< relref "doc/development/api-usage.zh-cn.md#通过-api-认证" >}})传递给 `VAGRANT_CLOUD_TOKEN` 环境变量。
69
+
如果注册表是私有的，您可以将您的[个人访问令牌](development/api-usage.md#通过-api-认证)传递给 `VAGRANT_CLOUD_TOKEN` 环境变量。
74
70
75
71
## 支持的命令
76
72
+2
-6
docs/content/doc/usage/permissions.en-us.md
docs/content/usage/permissions.en-us.md
+2
-6
docs/content/doc/usage/permissions.en-us.md
docs/content/usage/permissions.en-us.md
···
2
2
date: "2021-12-13:10:10+08:00"
3
3
title: "Permissions"
4
4
slug: "permissions"
5
-
weight: 14
5
+
sidebar_position: 14
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Permissions"
14
-
weight: 14
14
+
sidebar_position: 14
15
15
identifier: "permissions"
16
16
---
17
17
18
18
# Permissions
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea supports permissions for repository so that you can give different access for different people. At first, we need to know about `Unit`.
25
21
+2
-6
docs/content/doc/usage/permissions.zh-cn.md
docs/content/usage/permissions.zh-cn.md
+2
-6
docs/content/doc/usage/permissions.zh-cn.md
docs/content/usage/permissions.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "权限"
4
4
slug: "permissions"
5
-
weight: 14
5
+
sidebar_position: 14
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "权限"
14
-
weight: 14
14
+
sidebar_position: 14
15
15
identifier: "permissions"
16
16
---
17
17
18
18
# 权限
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea 支持对仓库进行权限管理，这样您就可以为不同的人员提供不同的访问权限。首先，我们需要了解 `单元（Unit）`。
25
21
+2
-2
docs/content/doc/usage/profile-readme.en-us.md
docs/content/usage/profile-readme.en-us.md
+2
-2
docs/content/doc/usage/profile-readme.en-us.md
docs/content/usage/profile-readme.en-us.md
···
2
2
date: "2023-03-02T21:00:00+05:00"
3
3
title: "Profile READMEs"
4
4
slug: "profile-readme"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
menu:
9
9
sidebar:
10
10
parent: "usage"
11
11
name: "Profile READMEs"
12
-
weight: 12
12
+
sidebar_position: 12
13
13
identifier: "profile-readme"
14
14
---
15
15
+2
-2
docs/content/doc/usage/profile-readme.zh-cn.md
docs/content/usage/profile-readme.zh-cn.md
+2
-2
docs/content/doc/usage/profile-readme.zh-cn.md
docs/content/usage/profile-readme.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "个人资料 README"
4
4
slug: "profile-readme"
5
-
weight: 12
5
+
sidebar_position: 12
6
6
toc: false
7
7
draft: false
8
8
menu:
9
9
sidebar:
10
10
parent: "usage"
11
11
name: "个人资料 README"
12
-
weight: 12
12
+
sidebar_position: 12
13
13
identifier: "profile-readme"
14
14
---
15
15
+2
-2
docs/content/doc/usage/pull-request.en-us.md
docs/content/usage/pull-request.en-us.md
+2
-2
docs/content/doc/usage/pull-request.en-us.md
docs/content/usage/pull-request.en-us.md
···
2
2
date: "2018-06-01T19:00:00+02:00"
3
3
title: "Pull Request"
4
4
slug: "pull-request"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Pull Request"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "pull-request"
16
16
---
17
17
+2
-2
docs/content/doc/usage/pull-request.zh-cn.md
docs/content/usage/pull-request.zh-cn.md
+2
-2
docs/content/doc/usage/pull-request.zh-cn.md
docs/content/usage/pull-request.zh-cn.md
···
2
2
date: "2018-06-01T19:00:00+02:00"
3
3
title: "合并请求"
4
4
slug: "pull-request"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Pull Request"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "pull-request"
16
16
---
17
17
+2
-2
docs/content/doc/usage/pull-request.zh-tw.md
docs/content/usage/pull-request.zh-tw.md
+2
-2
docs/content/doc/usage/pull-request.zh-tw.md
docs/content/usage/pull-request.zh-tw.md
···
2
2
date: "2018-06-01T19:00:00+02:00"
3
3
title: "合併請求"
4
4
slug: "pull-request"
5
-
weight: 13
5
+
sidebar_position: 13
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "合併請求"
14
-
weight: 13
14
+
sidebar_position: 13
15
15
identifier: "pull-request"
16
16
---
17
17
+3
-7
docs/content/doc/usage/push.en-us.md
docs/content/usage/push.en-us.md
+3
-7
docs/content/doc/usage/push.en-us.md
docs/content/usage/push.en-us.md
···
2
2
date: "2020-07-06T16:00:00+02:00"
3
3
title: "Push"
4
4
slug: "push"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
12
12
sidebar:
13
13
parent: "usage"
14
14
name: "Push"
15
-
weight: 15
15
+
sidebar_position: 15
16
16
identifier: "push"
17
17
---
18
-
19
-
**Table of Contents**
20
-
21
-
{{< toc >}}
22
18
23
19
There are some additional features when pushing commits to Gitea server.
24
20
···
55
51
56
52
## Enabling Push To Create
57
53
58
-
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.en-us.md#repository-repository" >}}).
54
+
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](administration/config-cheat-sheet.md#repository-repository).
59
55
60
56
## Using Push To Create
61
57
+3
-7
docs/content/doc/usage/push.zh-cn.md
docs/content/usage/push.zh-cn.md
+3
-7
docs/content/doc/usage/push.zh-cn.md
docs/content/usage/push.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "推送"
4
4
slug: "push"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
12
12
sidebar:
13
13
parent: "usage"
14
14
name: "推送"
15
-
weight: 15
15
+
sidebar_position: 15
16
16
identifier: "push"
17
17
---
18
-
19
-
**目录**
20
-
21
-
{{< toc >}}
22
18
23
19
在将提交推送到 Gitea 服务器时，还有一些额外的功能。
24
20
···
53
49
54
50
## 启用推送创建
55
51
56
-
在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表]({{< relref "doc/administration/config-cheat-sheet.zh-cn.md#repository-repository" >}}) 中了解有关这两个选项的更多信息。
52
+
在 `app.ini` 文件中，将 `ENABLE_PUSH_CREATE_USER` 设置为 `true`，如果您希望允许用户在自己的用户帐户和所属的组织中创建仓库，将 `ENABLE_PUSH_CREATE_ORG` 设置为 `true`。重新启动 Gitea 以使更改生效。您可以在 [配置速查表](administration/config-cheat-sheet.md#repository-repository) 中了解有关这两个选项的更多信息。
57
53
58
54
## 使用推送创建
59
55
+3
-7
docs/content/doc/usage/push.zh-tw.md
docs/content/usage/push.zh-tw.md
+3
-7
docs/content/doc/usage/push.zh-tw.md
docs/content/usage/push.zh-tw.md
···
2
2
date: "2020-07-06T16:00:00+02:00"
3
3
title: "使用: Push"
4
4
slug: "push"
5
-
weight: 15
5
+
sidebar_position: 15
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Push"
14
-
weight: 15
14
+
sidebar_position: 15
15
15
identifier: "push"
16
16
---
17
-
18
-
**Table of Contents**
19
-
20
-
{{< toc >}}
21
17
22
18
There are some additional features when pushing commits to Gitea server.
23
19
···
54
50
55
51
## Enabling Push To Create
56
52
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" >}}).
53
+
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](administration/config-cheat-sheet.md#repository-repository).
58
54
59
55
## Using Push To Create
60
56
+2
-6
docs/content/doc/usage/repo-mirror.en-us.md
docs/content/usage/repo-mirror.en-us.md
+2
-6
docs/content/doc/usage/repo-mirror.en-us.md
docs/content/usage/repo-mirror.en-us.md
···
2
2
date: "2021-05-13T00:00:00-00:00"
3
3
title: "Repository Mirror"
4
4
slug: "repo-mirror"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Repository Mirror"
14
-
weight: 45
14
+
sidebar_position: 45
15
15
identifier: "repo-mirror"
16
16
---
17
17
18
18
# Repository Mirror
19
19
20
20
Repository mirroring allows for the mirroring of repositories to and from external sources. You can use it to mirror branches, tags, and commits between repositories.
21
-
22
-
**Table of Contents**
23
-
24
-
{{< toc >}}
25
21
26
22
## Use cases
27
23
+2
-6
docs/content/doc/usage/repo-mirror.zh-cn.md
docs/content/usage/repo-mirror.zh-cn.md
+2
-6
docs/content/doc/usage/repo-mirror.zh-cn.md
docs/content/usage/repo-mirror.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "仓库镜像"
4
4
slug: "repo-mirror"
5
-
weight: 45
5
+
sidebar_position: 45
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "仓库镜像"
14
-
weight: 45
14
+
sidebar_position: 45
15
15
identifier: "repo-mirror"
16
16
---
17
17
18
18
# 仓库镜像
19
19
20
20
仓库镜像允许将仓库与外部源之间进行镜像。您可以使用它在仓库之间镜像分支、标签和提交。
21
-
22
-
**目录**
23
-
24
-
{{< toc >}}
25
21
26
22
## 使用场景
27
23
+2
-2
docs/content/doc/usage/secrets.en-us.md
docs/content/usage/secrets.en-us.md
+2
-2
docs/content/doc/usage/secrets.en-us.md
docs/content/usage/secrets.en-us.md
···
2
2
date: "2022-12-19T21:26:00+08:00"
3
3
title: "Secrets"
4
4
slug: "secrets"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
draft: false
7
7
toc: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Secrets"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "usage-secrets"
16
16
---
17
17
+2
-2
docs/content/doc/usage/secrets.zh-cn.md
docs/content/usage/secrets.zh-cn.md
+2
-2
docs/content/doc/usage/secrets.zh-cn.md
docs/content/usage/secrets.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "密钥管理"
4
4
slug: "secrets"
5
-
weight: 50
5
+
sidebar_position: 50
6
6
draft: false
7
7
toc: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "密钥管理"
14
-
weight: 50
14
+
sidebar_position: 50
15
15
identifier: "usage-secrets"
16
16
---
17
17
+2
-6
docs/content/doc/usage/template-repositories.en-us.md
docs/content/usage/template-repositories.en-us.md
+2
-6
docs/content/doc/usage/template-repositories.en-us.md
docs/content/usage/template-repositories.en-us.md
···
2
2
date: "2019-11-28:00:00+02:00"
3
3
title: "Template Repositories"
4
4
slug: "template-repositories"
5
-
weight: 14
5
+
sidebar_position: 14
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Template Repositories"
14
-
weight: 14
14
+
sidebar_position: 14
15
15
identifier: "template-repositories"
16
16
---
17
17
18
18
# Template Repositories
19
-
20
-
**Table of Contents**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea `1.11.0` and above includes template repositories, and one feature implemented with them is auto-expansion of specific variables within your template files.
25
21
+2
-6
docs/content/doc/usage/template-repositories.zh-cn.md
docs/content/usage/template-repositories.zh-cn.md
+2
-6
docs/content/doc/usage/template-repositories.zh-cn.md
docs/content/usage/template-repositories.zh-cn.md
···
2
2
date: "2023-05-23T09:00:00+08:00"
3
3
title: "模板仓库"
4
4
slug: "template-repositories"
5
-
weight: 14
5
+
sidebar_position: 14
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "模板仓库"
14
-
weight: 14
14
+
sidebar_position: 14
15
15
identifier: "template-repositories"
16
16
---
17
17
18
18
# 模板仓库
19
-
20
-
**目录**
21
-
22
-
{{< toc >}}
23
19
24
20
Gitea `1.11.0` 及以上版本引入了模板仓库，并且其中一个实现的功能是自动展开模板文件中的特定变量。
25
21
+2
-2
docs/content/doc/usage/webhooks.en-us.md
docs/content/usage/webhooks.en-us.md
+2
-2
docs/content/doc/usage/webhooks.en-us.md
docs/content/usage/webhooks.en-us.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Webhooks"
4
4
slug: "webhooks"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Webhooks"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "webhooks"
16
16
---
17
17
+2
-2
docs/content/doc/usage/webhooks.zh-cn.md
docs/content/usage/webhooks.zh-cn.md
+2
-2
docs/content/doc/usage/webhooks.zh-cn.md
docs/content/usage/webhooks.zh-cn.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Webhooks"
4
4
slug: "webhooks"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Webhooks"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "webhooks"
16
16
---
17
17
+2
-2
docs/content/doc/usage/webhooks.zh-tw.md
docs/content/usage/webhooks.zh-tw.md
+2
-2
docs/content/doc/usage/webhooks.zh-tw.md
docs/content/usage/webhooks.zh-tw.md
···
2
2
date: "2016-12-01T16:00:00+02:00"
3
3
title: "Webhook"
4
4
slug: "webhooks"
5
-
weight: 30
5
+
sidebar_position: 30
6
6
toc: false
7
7
draft: false
8
8
aliases:
···
11
11
sidebar:
12
12
parent: "usage"
13
13
name: "Webhook"
14
-
weight: 30
14
+
sidebar_position: 30
15
15
identifier: "webhooks"
16
16
---
17
17
+273
docs/content/index.fr-fr.md
+273
docs/content/index.fr-fr.md
···
1
+
---
2
+
date: "2017-08-23T09:00:00+02:00"
3
+
title: "Documentation"
4
+
slug: /
5
+
sidebar_position: 10
6
+
toc: false
7
+
draft: false
8
+
---
9
+
10
+
# A propos de Gitea
11
+
12
+
Gitea est un service Git auto-hébergé très simple à installer et à utiliser. Il est similaire à GitHub, Bitbucket ou Gitlab. Le développement initial provient sur [Gogs] (http://gogs.io), mais nous l'avons forké puis renommé Gitea. Si vous souhaitez en savoir plus sur les raisons pour lesquelles nous avons fait cela, lisez [cette publication] (https://blog.gitea.com/welcome-to-gitea/) sur le blog.
13
+
14
+
## Objectif
15
+
16
+
Le but de ce projet est de fournir de la manière la plus simple, la plus rapide et sans complication un service Git auto-hébergé. Grâce à Go, cela peut se faire via un binaire indépendant fonctionnant sur toutes les plateformes que Go prend en charge, y compris Linux, macOS et Windows, même sur des architectures comme ARM ou PowerPC.
17
+
18
+
## Fonctionalités
19
+
20
+
- Tableau de bord de l'utilisateur
21
+
- Choix du contexte (organisation ou utilisateur actuel)
22
+
- Chronologie de l'activité
23
+
- Révisions (_Commits_)
24
+
- Tickets
25
+
- Demande d'ajout (_Pull request_)
26
+
- Création de dépôts
27
+
- Liste des dépôts
28
+
- Liste de vos organisations
29
+
- Liste des dépôts miroires
30
+
- Tableau de bord des tickets
31
+
- Choix du contexte (organisation ou utilisateur actuel)
32
+
- Filtres
33
+
- Ouvert
34
+
- Fermé
35
+
- Vos dépôts
36
+
- Tickets assignés
37
+
- Vos tickets
38
+
- Dépôts
39
+
- Options de tri
40
+
- Plus vieux
41
+
- Dernière mise à jour
42
+
- Nombre de commentaires
43
+
- Tableau de bord des demandes d'ajout
44
+
- Identique au tableau de bord des tickets
45
+
- Types de dépôt
46
+
- Miroire
47
+
- Normal
48
+
- Migré
49
+
- Notifications (courriel et web)
50
+
- Lu
51
+
- Non lu
52
+
- Épinglé
53
+
- Page d'exploration
54
+
- Utilisateurs
55
+
- Dépôts
56
+
- Organisations
57
+
- Moteur de recherche
58
+
- Interface personnalisables
59
+
- Fichiers publiques remplaçables (logo, css, etc)
60
+
- Protection CSRF et XSS
61
+
- Support d'HTTPS
62
+
- Configuration des types et de la taille maximale des fichiers téléversés
63
+
- Journalisation (_Log_)
64
+
- Configuration
65
+
- Base de données
66
+
- MySQL
67
+
- PostgreSQL
68
+
- SQLite3
69
+
- MSSQL
70
+
- [TiDB](https://github.com/pingcap/tidb) (MySQL protocol)
71
+
- Fichier de configuration
72
+
- Voir [ici](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini)
73
+
- Panel d'administration
74
+
- Statistiques
75
+
- Actions
76
+
- Suppression des comptes inactifs
77
+
- Suppression des dépôts archivés
78
+
- Suppression des dépôts pour lesquels il manque leurs fichiers
79
+
- Exécution du _garbage collector_ sur les dépôts
80
+
- Ré-écriture des clefs SSH
81
+
- Resynchronisation des hooks
82
+
- Recreation des dépôts manquants
83
+
- Status du server
84
+
- Temps de disponibilité
85
+
- Mémoire
86
+
- Nombre de goroutines
87
+
- et bien plus...
88
+
- Gestion des utilisateurs
89
+
- Recherche
90
+
- Tri
91
+
- Dernière connexion
92
+
- Méthode d'authentification
93
+
- Nombre maximum de dépôts
94
+
- Désactivation du compte
95
+
- Permissions d'administration
96
+
- Permission pour crééer des hooks
97
+
- Permission pour crééer des organisations
98
+
- Permission pour importer des dépôts
99
+
- Gestion des organisations
100
+
- Membres
101
+
- Équipes
102
+
- Avatar
103
+
- Hooks
104
+
- Gestion des depôts
105
+
- Voir toutes les informations pour un dépôt donné et gérer tous les dépôts
106
+
- Méthodes d'authentification
107
+
- OAuth
108
+
- PAM
109
+
- LDAP
110
+
- SMTP
111
+
- Visualisation de la configuration
112
+
- Tout ce que contient le fichier de configuration
113
+
- Alertes du système
114
+
- Quand quelque chose d'inattendu survient
115
+
- Surveillance
116
+
- Processus courrants
117
+
- Tâches CRON
118
+
- Mise à jour des dépôts miroires
119
+
- Vérification de l'état des dépôts
120
+
- Vérification des statistiques des dépôts
121
+
- Nettoyage des anciennes archives
122
+
- Variables d'environement
123
+
- Options de ligne de commande
124
+
- Internationalisation ([21 langues](https://github.com/go-gitea/gitea/tree/master/options/locale))
125
+
- Courriel
126
+
- Notifications
127
+
- Confirmation d'inscription
128
+
- Ré-initialisation du mot de passe
129
+
- Support de _reverse proxy_
130
+
- _subpaths_ inclus
131
+
- Utilisateurs
132
+
- Profil
133
+
- Nom
134
+
- Prénom
135
+
- Courriel
136
+
- Site internet
137
+
- Date de création
138
+
- Abonnés et abonnements
139
+
- Organisations
140
+
- Dépôts
141
+
- Activité
142
+
- Dépôts suivis
143
+
- Paramètres
144
+
- Identiques au profil avec en plus les éléments ci-dessous
145
+
- Rendre l'adresse de courriel privée
146
+
- Avatar
147
+
- Gravatar
148
+
- Libravatar
149
+
- Personnalisé
150
+
- Mot de passe
151
+
- Courriels multiples
152
+
- Clefs SSH
153
+
- Applications connectées
154
+
- Authentification à double facteurs
155
+
- Identités OAuth2 attachées
156
+
- Suppression du compte
157
+
- Dépôts
158
+
- Clone à partir de SSH / HTTP / HTTPS
159
+
- Git LFS
160
+
- Suivre, Voter, Fork
161
+
- Voir les personnes qui suivent, les votes et les forks
162
+
- Code
163
+
- Navigation entre les branches
164
+
- Création ou téléversement de fichier depuis le navigateur
165
+
- URLs pour clôner le dépôt
166
+
- Téléchargement
167
+
- ZIP
168
+
- TAR.GZ
169
+
- Édition en ligne
170
+
- Éditeur Markdown
171
+
- Éditeur de texte
172
+
- Coloration syntaxique
173
+
- Visualisation des Diffs
174
+
- Visualisation
175
+
- Possibilité de choisir où sauvegarder la révision
176
+
- Historiques des fichiers
177
+
- Suppression de fichiers
178
+
- Voir le fichier brut
179
+
- Tickets
180
+
- Modèle de ticket
181
+
- Jalons
182
+
- Étiquettes
183
+
- Affecter des tickets
184
+
- Filtres
185
+
- Ouvert
186
+
- Ferme
187
+
- Personne assignée
188
+
- Créer par vous
189
+
- Qui vous mentionne
190
+
- Tri
191
+
- Plus vieux
192
+
- Dernière mise à jour
193
+
- Nombre de commentaires
194
+
- Moteur de recherche
195
+
- Commentaires
196
+
- Joindre des fichiers
197
+
- Demande d’ajout (_Pull request_)
198
+
- Les mêmes fonctionnalités que pour les tickets
199
+
- Révisions (_Commits_)
200
+
- Representation graphique des révisions
201
+
- Révisions par branches
202
+
- Moteur de recherche
203
+
- Voir les différences
204
+
- Voir les numéro de révision SHA
205
+
- Voir l'auteur
206
+
- Naviguer dans les fichiers d'une révision donnée
207
+
- Publication
208
+
- Pièces jointes
209
+
- Titre
210
+
- Contenu
211
+
- Suppression
212
+
- Définir comme une pré-publication
213
+
- Choix de la branche
214
+
- Wiki
215
+
- Import
216
+
- Éditeur Markdown
217
+
- Paramètres
218
+
- Options
219
+
- Nom
220
+
- Description
221
+
- Privé / Publique
222
+
- Site internet
223
+
- Wiki
224
+
- Activé / Désactivé
225
+
- Interne / externe
226
+
- Tickets
227
+
- Activé / Désactivé
228
+
- Interne / externe
229
+
- URL personnalisable pour une meilleur intégration avec un gestionnaire de tickets externe
230
+
- Activer / désactiver les demandes d'ajout (_Pull request_)
231
+
- Transfert du dépôt
232
+
- Suppression du wiki
233
+
- Suppression du dépôt
234
+
- Collaboration
235
+
- Lecture / Écriture / Administration
236
+
- Branches
237
+
- Branche par défaut
238
+
- Protection
239
+
- Webhooks
240
+
- Git hooks
241
+
- Clefs de déploiement
242
+
243
+
## Configuration requise
244
+
245
+
- Un simple Raspberry Pi est assez puissant pour les fonctionnalités de base.
246
+
- Un processeur double coeurs et 1Gb de RAM est une bonne base pour une utilisation en équipe.
247
+
- Gitea est censé être exécuté avec un compte utilisateur dédié et non root, aucun autre mode de fonctionnement n'est pris en charge. (**NOTE**: Dans le cas où vous l'exécutez avec votre propre compte d'utilisateur et que le serveur SSH intégré est désactivé, Gitea modifie le fichier `~ /.ssh /authorized_keys` afin que vous ne soyez **plus capable** de vous connecter interactivement).
248
+
249
+
## Navigateurs supportés
250
+
251
+
- Chrome, Firefox, Safari, Edge
252
+
253
+
## Composants
254
+
255
+
- Framework web : [Chi](http://github.com/go-chi/chi)
256
+
- ORM: [XORM](https://xorm.io)
257
+
- Interface graphique :
258
+
- [jQuery](https://jquery.com)
259
+
- [Fomantic UI](https://fomantic-ui.com)
260
+
- [Vue3](https://vuejs.org)
261
+
- [CodeMirror](https://codemirror.net)
262
+
- [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
263
+
- [Monaco Editor](https://microsoft.github.io/monaco-editor)
264
+
- ... (package.json)
265
+
- Connecteurs de base de données :
266
+
- [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
267
+
- [github.com/lib/pq](https://github.com/lib/pq)
268
+
- [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
269
+
- [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
270
+
271
+
## Logiciels et services
272
+
273
+
- [Drone](https://github.com/drone/drone) (Intégration continue)
+2
-3
docs/content/page/index.de-de.md
docs/content/index.de-de.md
+2
-3
docs/content/page/index.de-de.md
docs/content/index.de-de.md
+2
-3
docs/content/page/index.en-us.md
docs/content/index.en-us.md
+2
-3
docs/content/page/index.en-us.md
docs/content/index.en-us.md
-274
docs/content/page/index.fr-fr.md
-274
docs/content/page/index.fr-fr.md
···
1
-
---
2
-
date: "2017-08-23T09:00:00+02:00"
3
-
title: "Documentation"
4
-
slug: "documentation"
5
-
url: "/fr-fr/"
6
-
weight: 10
7
-
toc: false
8
-
draft: false
9
-
---
10
-
11
-
# A propos de Gitea
12
-
13
-
Gitea est un service Git auto-hébergé très simple à installer et à utiliser. Il est similaire à GitHub, Bitbucket ou Gitlab. Le développement initial provient sur [Gogs] (http://gogs.io), mais nous l'avons forké puis renommé Gitea. Si vous souhaitez en savoir plus sur les raisons pour lesquelles nous avons fait cela, lisez [cette publication] (https://blog.gitea.com/welcome-to-gitea/) sur le blog.
14
-
15
-
## Objectif
16
-
17
-
Le but de ce projet est de fournir de la manière la plus simple, la plus rapide et sans complication un service Git auto-hébergé. Grâce à Go, cela peut se faire via un binaire indépendant fonctionnant sur toutes les plateformes que Go prend en charge, y compris Linux, macOS et Windows, même sur des architectures comme ARM ou PowerPC.
18
-
19
-
## Fonctionalités
20
-
21
-
- Tableau de bord de l'utilisateur
22
-
- Choix du contexte (organisation ou utilisateur actuel)
23
-
- Chronologie de l'activité
24
-
- Révisions (_Commits_)
25
-
- Tickets
26
-
- Demande d'ajout (_Pull request_)
27
-
- Création de dépôts
28
-
- Liste des dépôts
29
-
- Liste de vos organisations
30
-
- Liste des dépôts miroires
31
-
- Tableau de bord des tickets
32
-
- Choix du contexte (organisation ou utilisateur actuel)
33
-
- Filtres
34
-
- Ouvert
35
-
- Fermé
36
-
- Vos dépôts
37
-
- Tickets assignés
38
-
- Vos tickets
39
-
- Dépôts
40
-
- Options de tri
41
-
- Plus vieux
42
-
- Dernière mise à jour
43
-
- Nombre de commentaires
44
-
- Tableau de bord des demandes d'ajout
45
-
- Identique au tableau de bord des tickets
46
-
- Types de dépôt
47
-
- Miroire
48
-
- Normal
49
-
- Migré
50
-
- Notifications (courriel et web)
51
-
- Lu
52
-
- Non lu
53
-
- Épinglé
54
-
- Page d'exploration
55
-
- Utilisateurs
56
-
- Dépôts
57
-
- Organisations
58
-
- Moteur de recherche
59
-
- Interface personnalisables
60
-
- Fichiers publiques remplaçables (logo, css, etc)
61
-
- Protection CSRF et XSS
62
-
- Support d'HTTPS
63
-
- Configuration des types et de la taille maximale des fichiers téléversés
64
-
- Journalisation (_Log_)
65
-
- Configuration
66
-
- Base de données
67
-
- MySQL
68
-
- PostgreSQL
69
-
- SQLite3
70
-
- MSSQL
71
-
- [TiDB](https://github.com/pingcap/tidb) (MySQL protocol)
72
-
- Fichier de configuration
73
-
- Voir [ici](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini)
74
-
- Panel d'administration
75
-
- Statistiques
76
-
- Actions
77
-
- Suppression des comptes inactifs
78
-
- Suppression des dépôts archivés
79
-
- Suppression des dépôts pour lesquels il manque leurs fichiers
80
-
- Exécution du _garbage collector_ sur les dépôts
81
-
- Ré-écriture des clefs SSH
82
-
- Resynchronisation des hooks
83
-
- Recreation des dépôts manquants
84
-
- Status du server
85
-
- Temps de disponibilité
86
-
- Mémoire
87
-
- Nombre de goroutines
88
-
- et bien plus...
89
-
- Gestion des utilisateurs
90
-
- Recherche
91
-
- Tri
92
-
- Dernière connexion
93
-
- Méthode d'authentification
94
-
- Nombre maximum de dépôts
95
-
- Désactivation du compte
96
-
- Permissions d'administration
97
-
- Permission pour crééer des hooks
98
-
- Permission pour crééer des organisations
99
-
- Permission pour importer des dépôts
100
-
- Gestion des organisations
101
-
- Membres
102
-
- Équipes
103
-
- Avatar
104
-
- Hooks
105
-
- Gestion des depôts
106
-
- Voir toutes les informations pour un dépôt donné et gérer tous les dépôts
107
-
- Méthodes d'authentification
108
-
- OAuth
109
-
- PAM
110
-
- LDAP
111
-
- SMTP
112
-
- Visualisation de la configuration
113
-
- Tout ce que contient le fichier de configuration
114
-
- Alertes du système
115
-
- Quand quelque chose d'inattendu survient
116
-
- Surveillance
117
-
- Processus courrants
118
-
- Tâches CRON
119
-
- Mise à jour des dépôts miroires
120
-
- Vérification de l'état des dépôts
121
-
- Vérification des statistiques des dépôts
122
-
- Nettoyage des anciennes archives
123
-
- Variables d'environement
124
-
- Options de ligne de commande
125
-
- Internationalisation ([21 langues](https://github.com/go-gitea/gitea/tree/master/options/locale))
126
-
- Courriel
127
-
- Notifications
128
-
- Confirmation d'inscription
129
-
- Ré-initialisation du mot de passe
130
-
- Support de _reverse proxy_
131
-
- _subpaths_ inclus
132
-
- Utilisateurs
133
-
- Profil
134
-
- Nom
135
-
- Prénom
136
-
- Courriel
137
-
- Site internet
138
-
- Date de création
139
-
- Abonnés et abonnements
140
-
- Organisations
141
-
- Dépôts
142
-
- Activité
143
-
- Dépôts suivis
144
-
- Paramètres
145
-
- Identiques au profil avec en plus les éléments ci-dessous
146
-
- Rendre l'adresse de courriel privée
147
-
- Avatar
148
-
- Gravatar
149
-
- Libravatar
150
-
- Personnalisé
151
-
- Mot de passe
152
-
- Courriels multiples
153
-
- Clefs SSH
154
-
- Applications connectées
155
-
- Authentification à double facteurs
156
-
- Identités OAuth2 attachées
157
-
- Suppression du compte
158
-
- Dépôts
159
-
- Clone à partir de SSH / HTTP / HTTPS
160
-
- Git LFS
161
-
- Suivre, Voter, Fork
162
-
- Voir les personnes qui suivent, les votes et les forks
163
-
- Code
164
-
- Navigation entre les branches
165
-
- Création ou téléversement de fichier depuis le navigateur
166
-
- URLs pour clôner le dépôt
167
-
- Téléchargement
168
-
- ZIP
169
-
- TAR.GZ
170
-
- Édition en ligne
171
-
- Éditeur Markdown
172
-
- Éditeur de texte
173
-
- Coloration syntaxique
174
-
- Visualisation des Diffs
175
-
- Visualisation
176
-
- Possibilité de choisir où sauvegarder la révision
177
-
- Historiques des fichiers
178
-
- Suppression de fichiers
179
-
- Voir le fichier brut
180
-
- Tickets
181
-
- Modèle de ticket
182
-
- Jalons
183
-
- Étiquettes
184
-
- Affecter des tickets
185
-
- Filtres
186
-
- Ouvert
187
-
- Ferme
188
-
- Personne assignée
189
-
- Créer par vous
190
-
- Qui vous mentionne
191
-
- Tri
192
-
- Plus vieux
193
-
- Dernière mise à jour
194
-
- Nombre de commentaires
195
-
- Moteur de recherche
196
-
- Commentaires
197
-
- Joindre des fichiers
198
-
- Demande d’ajout (_Pull request_)
199
-
- Les mêmes fonctionnalités que pour les tickets
200
-
- Révisions (_Commits_)
201
-
- Representation graphique des révisions
202
-
- Révisions par branches
203
-
- Moteur de recherche
204
-
- Voir les différences
205
-
- Voir les numéro de révision SHA
206
-
- Voir l'auteur
207
-
- Naviguer dans les fichiers d'une révision donnée
208
-
- Publication
209
-
- Pièces jointes
210
-
- Titre
211
-
- Contenu
212
-
- Suppression
213
-
- Définir comme une pré-publication
214
-
- Choix de la branche
215
-
- Wiki
216
-
- Import
217
-
- Éditeur Markdown
218
-
- Paramètres
219
-
- Options
220
-
- Nom
221
-
- Description
222
-
- Privé / Publique
223
-
- Site internet
224
-
- Wiki
225
-
- Activé / Désactivé
226
-
- Interne / externe
227
-
- Tickets
228
-
- Activé / Désactivé
229
-
- Interne / externe
230
-
- URL personnalisable pour une meilleur intégration avec un gestionnaire de tickets externe
231
-
- Activer / désactiver les demandes d'ajout (_Pull request_)
232
-
- Transfert du dépôt
233
-
- Suppression du wiki
234
-
- Suppression du dépôt
235
-
- Collaboration
236
-
- Lecture / Écriture / Administration
237
-
- Branches
238
-
- Branche par défaut
239
-
- Protection
240
-
- Webhooks
241
-
- Git hooks
242
-
- Clefs de déploiement
243
-
244
-
## Configuration requise
245
-
246
-
- Un simple Raspberry Pi est assez puissant pour les fonctionnalités de base.
247
-
- Un processeur double coeurs et 1Gb de RAM est une bonne base pour une utilisation en équipe.
248
-
- Gitea est censé être exécuté avec un compte utilisateur dédié et non root, aucun autre mode de fonctionnement n'est pris en charge. (**NOTE**: Dans le cas où vous l'exécutez avec votre propre compte d'utilisateur et que le serveur SSH intégré est désactivé, Gitea modifie le fichier `~ /.ssh /authorized_keys` afin que vous ne soyez **plus capable** de vous connecter interactivement).
249
-
250
-
## Navigateurs supportés
251
-
252
-
- Chrome, Firefox, Safari, Edge
253
-
254
-
## Composants
255
-
256
-
- Framework web : [Chi](http://github.com/go-chi/chi)
257
-
- ORM: [XORM](https://xorm.io)
258
-
- Interface graphique :
259
-
- [jQuery](https://jquery.com)
260
-
- [Fomantic UI](https://fomantic-ui.com)
261
-
- [Vue3](https://vuejs.org)
262
-
- [CodeMirror](https://codemirror.net)
263
-
- [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
264
-
- [Monaco Editor](https://microsoft.github.io/monaco-editor)
265
-
- ... (package.json)
266
-
- Connecteurs de base de données :
267
-
- [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
268
-
- [github.com/lib/pq](https://github.com/lib/pq)
269
-
- [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
270
-
- [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
271
-
272
-
## Logiciels et services
273
-
274
-
- [Drone](https://github.com/drone/drone) (Intégration continue)
+2
-3
docs/content/page/index.zh-cn.md
docs/content/index.zh-cn.md
+2
-3
docs/content/page/index.zh-cn.md
docs/content/index.zh-cn.md
+2
-3
docs/content/page/index.zh-tw.md
docs/content/index.zh-tw.md
+2
-3
docs/content/page/index.zh-tw.md
docs/content/index.zh-tw.md
+105
docs/content/usage/packages/overview.zh-cn.md
+105
docs/content/usage/packages/overview.zh-cn.md
···
1
+
---
2
+
date: "2021-07-20T00:00:00+00:00"
3
+
title: "软件包注册表"
4
+
slug: "overview"
5
+
sidebar_position: 1
6
+
draft: false
7
+
toc: false
8
+
menu:
9
+
sidebar:
10
+
parent: "packages"
11
+
name: "Overview"
12
+
sidebar_position: 1
13
+
identifier: "packages-overview"
14
+
---
15
+
16
+
# 软件包注册表
17
+
18
+
从Gitea **1.17**版本开始，软件包注册表可以用作常见软件包管理器的公共或私有注册表。
19
+
20
+
## 支持的软件包管理器
21
+
22
+
目前支持以下软件包管理器：
23
+
24
+
| Name | Language | Package client |
25
+
| ------------------------------------------------------------------- | ---------- | ------------------------- |
26
+
| [Alpine](usage/packages/alpine.md) | - | `apk` |
27
+
| [Cargo](usage/packages/cargo.md) | Rust | `cargo` |
28
+
| [Chef](usage/packages/chef.md) | - | `knife` |
29
+
| [Composer](usage/packages/composer.md) | PHP | `composer` |
30
+
| [Conan](usage/packages/conan.md) | C++ | `conan` |
31
+
| [Conda](usage/packages/conda.md) | - | `conda` |
32
+
| [Container](usage/packages/container.md) | - | 任何符合OCI规范的客户端 |
33
+
| [CRAN](usage/packages/cran.md) | R | - |
34
+
| [Debian](usage/packages/debian.md) | - | `apt` |
35
+
| [Generic](usage/packages/generic.md) | - | 任何HTTP客户端 |
36
+
| [Go](usage/packages/go.md) | Go | `go` |
37
+
| [Helm](usage/packages/helm.md) | - | 任何HTTP客户端, `cm-push` |
38
+
| [Maven](usage/packages/maven.md) | Java | `mvn`, `gradle` |
39
+
| [npm](usage/packages/npm.md) | JavaScript | `npm`, `yarn`, `pnpm` |
40
+
| [NuGet](usage/packages/nuget.md) | .NET | `nuget` |
41
+
| [Pub](usage/packages/pub.md) | Dart | `dart`, `flutter` |
42
+
| [PyPI](usage/packages/pypi.md) | Python | `pip`, `twine` |
43
+
| [RPM](usage/packages/rpm.md) | - | `yum`, `dnf`, `zypper` |
44
+
| [RubyGems](usage/packages/rubygems.md) | Ruby | `gem`, `Bundler` |
45
+
| [Swift](usage/packages/rubygems.md) | Swift | `swift` |
46
+
| [Vagrant](usage/packages/vagrant.md) | - | `vagrant` |
47
+
48
+
**以下段落仅适用于未全局禁用软件包的情况！**
49
+
50
+
## 仓库 x 软件包
51
+
52
+
软件包始终属于所有者（用户或组织），而不是仓库。
53
+
要将（已上传的）软件包链接到仓库，请打开该软件包的设置页面，并选择要将此软件包链接到的仓库。
54
+
将链接到整个软件包，而不仅是单个版本。
55
+
56
+
链接软件包将导致在仓库的软件包列表中显示该软件包，并在软件包页面上显示到仓库的链接（以及到仓库工单的链接）。
57
+
58
+
## 访问限制
59
+
60
+
| 软件包所有者类型 | 用户 | 组织 |
61
+
| ---------------- | ---------------------------------------- | ------------------------------------------ |
62
+
| **读取** 访问 | 公开，如果用户也是公开的；否则仅限此用户 | 公开，如果组织是公开的，否则仅限组织成员 |
63
+
| **写入** 访问 | 仅软件包所有者 | 具有组织中的管理员或写入访问权限的组织成员 |
64
+
65
+
注意：这些访问限制可能会[变化](https://github.com/go-gitea/gitea/issues/19270)，将通过专门的组织团队权限添加更细粒度的控制。
66
+
67
+
## 创建或上传软件包
68
+
69
+
根据软件包类型，使用相应的软件包管理器。请查看特定软件包管理器的子页面以获取说明。
70
+
71
+
## 查看软件包
72
+
73
+
您可以在仓库页面上查看仓库的软件包。
74
+
75
+
1. 转到仓库主页。
76
+
2. 在导航栏中选择**软件包**
77
+
78
+
要查看有关软件包的更多详细信息，请选择软件包的名称。
79
+
80
+
## 下载软件包
81
+
82
+
要从仓库下载软件包：
83
+
84
+
1. 在导航栏中选择**软件包**
85
+
2. 选择软件包的名称以查看详细信息。
86
+
3. 在 **Assets** 部分，选择要下载的软件包文件的名称。
87
+
88
+
## 删除软件包
89
+
90
+
在将软件包发布到软件包注册表后，您无法编辑软件包。相反，您必须删除并重新创建它。
91
+
92
+
要从仓库中删除软件包：
93
+
94
+
1. 在导航栏中选择**软件包**
95
+
2. 选择软件包的名称以查看详细信息。
96
+
3. 单击**删除软件包**以永久删除软件包。
97
+
98
+
## 禁用软件包注册表
99
+
100
+
包注册表已自动启用。要在单个存储库中禁用它：
101
+
102
+
1. 在导航栏中选择**设置**。
103
+
2. 禁用**启用仓库软件包注册表**.
104
+
105
+
禁用软件包注册表不会删除先前发布的软件包。
-5
docs/layouts/_default/index.json
-5
docs/layouts/_default/index.json
-12
docs/layouts/alias.html
-12
docs/layouts/alias.html
···
1
-
<!DOCTYPE html>
2
-
<html{{ with site.LanguageCode | default site.Language.Lang }} lang="{{ . }}"{{ end }}>
3
-
<head>
4
-
<title>{{ .Permalink }}</title>
5
-
<link rel="canonical" href="{{ .Permalink }}">
6
-
<meta name="robots" content="noindex">
7
-
<noscript><meta http-equiv="refresh" content="0; url={{ .Permalink }}"></noscript>
8
-
<script>
9
-
window.location = "{{ .Permalink }}" + window.location.search + window.location.hash;
10
-
</script>
11
-
</head>
12
-
</html>
-38
docs/layouts/doc/search.html
-38
docs/layouts/doc/search.html
···
1
-
{{ partial "header.html" . }}
2
-
{{ partial "navbar.html" . }}
3
-
4
-
<section class="section">
5
-
<div class="container is-centered page">
6
-
<div class="columns">
7
-
<div class="column is-one-quarter">
8
-
{{ partial "menu" . }}
9
-
</div>
10
-
<div class="column">
11
-
<div class=" content">
12
-
<section class="resume-section p-3 p-lg-5 d-flex flex-column">
13
-
<div class="my-auto" >
14
-
<div id="search-results"></div>
15
-
</div>
16
-
</section>
17
-
<!-- this template is sucked in by search.js and appended to the search-results div above. So editing here will adjust style -->
18
-
<script id="search-result-template" type="text/x-js-template">
19
-
<div id="summary-${key}">
20
-
<h4><a href="${link}">${title}</a></h4>
21
-
<p>${snippet}</p>
22
-
${ isset tags }<p>Tags: ${tags}</p>${ end }
23
-
${ isset categories }<p>Categories: ${categories}</p>${ end }
24
-
<hr/>
25
-
</div>
26
-
</script>
27
-
</div>
28
-
</div>
29
-
</div>
30
-
</div>
31
-
</section>
32
-
33
-
<script src="https://cdnjs.cloudflare.com/ajax/libs/fuse.js/3.4.5/fuse.min.js"></script>
34
-
<script src="https://cdnjs.cloudflare.com/ajax/libs/mark.js/8.11.1/mark.min.js"></script>
35
-
<script>document.LANG = "{{ .Language.Lang }}";</script>
36
-
{{ $script := resources.Get "js/search.js" | minify | fingerprint -}}
37
-
<script src="{{ $script.Permalink }}" {{ printf "integrity=%q" $script.Data.Integrity | safeHTMLAttr }}></script>
38
-
{{ partial "footer.html" . }}
-23
docs/layouts/index.html
-23
docs/layouts/index.html
···
1
-
{{ partial "header.html" . }}
2
-
{{ partial "navbar.html" . }}
3
-
4
-
<div class="container content">
5
-
<div class="row">
6
-
<div class="col-md-3">
7
-
{{ partial "menu" . }}
8
-
</div>
9
-
<div class="col-md-9">
10
-
{{ range where .Site.Pages "Type" "page" }}
11
-
{{ .Content }}
12
-
{{ end }}
13
-
14
-
{{ if .Site.DisqusShortname }}
15
-
<div class="col-xs-12">
16
-
{{ partial "disqus.html" . }}
17
-
</div>
18
-
{{ end }}
19
-
</div>
20
-
</div>
21
-
</div>
22
-
23
-
{{ partial "footer.html" . }}
-1
docs/layouts/shortcodes/go-version.html
-1
docs/layouts/shortcodes/go-version.html
···
1
-
{{ .Site.Params.goVersion }}
-1
docs/layouts/shortcodes/min-go-version.html
-1
docs/layouts/shortcodes/min-go-version.html
···
1
-
{{ .Site.Params.minGoVersion }}
-1
docs/layouts/shortcodes/min-node-version.html
-1
docs/layouts/shortcodes/min-node-version.html
···
1
-
{{ .Site.Params.minNodeVersion }}
-1
docs/layouts/shortcodes/version.html
-1
docs/layouts/shortcodes/version.html
···
1
-
{{ .Site.Params.version }}
-6
docs/static/_headers
-6
docs/static/_headers
···
1
-
/*
2
-
Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; font-src 'self' data: https://cdnjs.cloudflare.com https://fonts.gstatic.com
3
-
X-Frame-Options: DENY
4
-
X-Xss-Protection: 1; mode=block
5
-
X-Content-Type-Options: nosniff
6
-
Referrer-Policy: strict-origin-when-cross-origin
-19
docs/static/_redirects
-19
docs/static/_redirects
···
1
-
https://gitea-docs.netlify.com/* https://docs.gitea.io/:splat 302!
2
-
3
-
/ /fr-fr/ 302! Language=fr
4
-
/ /nl-nl/ 302! Language=nl
5
-
/ /pt-br/ 302! Language=pt-br
6
-
/ /zh-cn/ 302! Language=zh-cn
7
-
/ /zh-tw/ 302! Language=zh-tw
8
-
/ /en-us/ 302!
9
-
10
-
/en-us/ci-cd/ /en-us/integrations/ 302!
11
-
/en-us/third-party-tools/ /en-us/integrations/ 302!
12
-
/zh-cn/third-party-tools/ /zh-cn/integrations/ 302!
13
-
/en-us/make/ /en-us/hacking-on-gitea/ 302!
14
-
/zh-cn/make/ /zh-cn/hacking-on-gitea/ 302!
15
-
/fr-fr/make/ /fr-fr/hacking-on-gitea/ 302!
16
-
/en-us/upgrade/ /en-us/upgrade-from-gitea/ 302!
17
-
/fr-fr/upgrade/ /fr-fr/upgrade-from-gitea/ 302!
18
-
/zh-cn/upgrade/ /zh-cn/upgrade-from-gitea/ 302!
19
-
/zh-tw/upgrade/ /zh-tw/upgrade-from-gitea/ 302!
-53
docs/static/cloudron.svg
-53
docs/static/cloudron.svg
···
1
-
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2
-
<!-- Created with Inkscape (http://www.inkscape.org/) -->
3
-
<svg xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://creativecommons.org/ns#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" width="155" height="37" id="svg4152" version="1.1" inkscape:version="0.91 r13725" viewBox="0 0 155 37" sodipodi:docname="button.svg" inkscape:export-filename="/home/nebulon/Cloudron/Assets/button_64.png" inkscape:export-xdpi="155.6129" inkscape:export-ydpi="155.6129">
4
-
<defs id="defs4154"/>
5
-
<sodipodi:namedview id="base" pagecolor="#ffffff" bordercolor="#666666" borderopacity="1.0" inkscape:pageopacity="1" inkscape:pageshadow="2" inkscape:zoom="3.6203867" inkscape:cx="121.3823" inkscape:cy="1.1988893" inkscape:current-layer="g4481" showgrid="true" inkscape:document-units="px" inkscape:grid-bbox="true" inkscape:window-width="1280" inkscape:window-height="736" inkscape:window-x="0" inkscape:window-y="27" inkscape:window-maximized="1" showguides="false"/>
6
-
<metadata id="metadata4157">
7
-
<rdf:RDF>
8
-
<cc:Work rdf:about="">
9
-
<dc:format>image/svg+xml</dc:format>
10
-
<dc:type rdf:resource="http://purl.org/dc/dcmitype/StillImage"/>
11
-
<dc:title/>
12
-
</cc:Work>
13
-
</rdf:RDF>
14
-
</metadata>
15
-
<g id="layer1" inkscape:label="Layer 1" inkscape:groupmode="layer" transform="translate(0,-27)">
16
-
<g id="g5138">
17
-
<rect inkscape:export-ydpi="67.349998" inkscape:export-xdpi="67.349998" ry="3.2883968" y="27.493248" x="0.49324799" height="36.013504" width="154.0135" id="rect4424" style="opacity:1;fill:none;fill-opacity:1;stroke:#03a9f4;stroke-width:0.98649561;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"/>
18
-
<g transform="translate(-17.67767,3.2702403)" id="g4467">
19
-
<g id="g4382" transform="matrix(0.59473169,0,0,0.59473169,31.04719,102.48374)" inkscape:export-xdpi="67.349998" inkscape:export-ydpi="67.349998">
20
-
<g id="g4496">
21
-
<path inkscape:export-ydpi="67.349998" inkscape:export-xdpi="67.349998" transform="matrix(0.8660254,-0.49999999,0.49999999,0.8660254,51.102849,-7.8015133)" d="m 29.166669,-109.50348 c 1.200386,2.08567 1.17988,17.183595 -0.02617,19.265993 -1.206046,2.082397 -14.291486,9.613601 -16.697919,9.610333 -2.406432,-0.0033 -15.4713664,-7.56999 -16.671752,-9.655655 -1.2003857,-2.085666 -1.1798799,-17.183591 0.026167,-19.265991 1.2060467,-2.0824 14.2914862,-9.6136 16.6979192,-9.61033 2.406432,0.003 15.471366,7.56999 16.671752,9.65565 z" inkscape:randomized="0" inkscape:rounded="0.12490573" inkscape:flatsided="true" sodipodi:arg2="0.0013581913" sodipodi:arg1="-0.52224059" sodipodi:r2="16.307295" sodipodi:r1="19.266006" sodipodi:cy="-99.893143" sodipodi:cx="12.46875" sodipodi:sides="6" id="path4162" style="opacity:1;fill:#03a9f4;fill-opacity:1;stroke:none;stroke-width:1.10000002;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" sodipodi:type="star"/>
22
-
<rect style="opacity:1;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:2.29999995;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" id="rect4168-1-1" width="8.7434387" height="8.7434387" x="2.2207832" y="-104.9176" ry="2.4183984" inkscape:transform-center-x="0.40624986"/>
23
-
<g id="g4491" transform="translate(0,0.14463441)">
24
-
<rect ry="2.4183986" y="-98.734459" x="9.0890703" height="8.7434387" width="8.7434387" id="rect4168-1-1-7" style="opacity:1;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:2.29999995;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"/>
25
-
<rect ry="2.4183986" y="-111.39002" x="9.0890703" height="8.7434387" width="8.7434387" id="rect4168-1-1-7-2" style="opacity:1;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:2.29999995;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"/>
26
-
</g>
27
-
</g>
28
-
</g>
29
-
</g>
30
-
<g style="fill:#03a9f4;fill-opacity:1" transform="translate(0,-12.132814)" id="g4481">
31
-
<g style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" id="text4135">
32
-
<path d="m 41.656508,62.625017 c -2.555847,0 -3.639656,-1.261747 -3.639656,-4.173473 0,-2.927901 1.083809,-4.173472 3.639656,-4.173472 1.16469,0 2.216146,0.274996 3.122016,0.679402 l 0,-1.391157 c -0.970575,-0.38823 -2.07056,-0.64705 -3.299955,-0.64705 -2.280851,0 -5.014637,0.954399 -5.014637,5.532277 0,4.577879 2.733786,5.532278 5.014637,5.532278 1.229395,0 2.32938,-0.25882 3.299955,-0.64705 l 0,-1.391157 c -0.90587,0.404406 -1.957326,0.679402 -3.122016,0.679402 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4149"/>
33
-
<path d="m 47.031573,52.708976 0,11.145436 1.488215,0 0,-11.145436 -1.488215,0 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4151"/>
34
-
<path d="m 54.478208,55.669229 c -1.730858,0 -3.801418,0.727932 -3.801418,4.157297 0,3.429365 2.07056,4.157296 3.801418,4.157296 1.730859,0 3.801419,-0.727931 3.801419,-4.157296 0,-3.429365 -2.07056,-4.157297 -3.801419,-4.157297 z m 0,7.004317 c -1.213218,0 -2.313203,-0.339701 -2.313203,-2.84702 0,-2.507319 1.099985,-2.84702 2.313203,-2.84702 1.213219,0 2.313204,0.339701 2.313204,2.84702 0,2.507319 -1.099985,2.84702 -2.313204,2.84702 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4153"/>
35
-
<path d="m 65.458345,55.782463 0,4.78817 c 0,1.472039 -0.598521,2.119089 -1.924974,2.119089 -1.342629,0 -1.94115,-0.64705 -1.94115,-2.119089 l 0,-4.78817 -1.472039,0 0,4.674936 c 0,2.248499 1.245572,3.542599 3.413189,3.542599 2.167618,0 3.413189,-1.2941 3.413189,-3.542599 l 0,-4.674936 -1.488215,0 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4155"/>
36
-
<path d="m 69.133133,59.713292 c 0,3.720538 2.232322,4.27053 3.574951,4.27053 3.089664,0 3.332308,-2.005855 3.332308,-2.620552 l 0,-8.654294 -1.472039,0 0,3.186721 c -0.566169,-0.161763 -1.132338,-0.242644 -1.730859,-0.242644 -1.68233,0 -3.704361,0.711755 -3.704361,4.060239 z m 1.472039,0 c 0,-2.410261 1.083808,-2.749963 2.232322,-2.749963 0.598521,0 1.180866,0.113234 1.730859,0.339702 l 0,4.157296 c 0,0.808813 -0.630874,1.213219 -1.860269,1.213219 -0.986751,0 -2.102912,-0.339701 -2.102912,-2.960254 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4157"/>
37
-
<path d="m 79.727313,57.351559 c 0.630874,-0.161762 1.488215,-0.323525 2.442614,-0.339701 l 0,-1.358805 c -2.167618,0 -3.849948,0.77646 -3.930829,0.808813 l 0,7.392546 1.488215,0 0,-6.502853 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4159"/>
38
-
<path d="m 86.957085,55.669229 c -1.730859,0 -3.801419,0.727932 -3.801419,4.157297 0,3.429365 2.07056,4.157296 3.801419,4.157296 1.730858,0 3.801418,-0.727931 3.801418,-4.157296 0,-3.429365 -2.07056,-4.157297 -3.801418,-4.157297 z m 0,7.004317 c -1.213219,0 -2.313204,-0.339701 -2.313204,-2.84702 0,-2.507319 1.099985,-2.84702 2.313204,-2.84702 1.213218,0 2.313203,0.339701 2.313203,2.84702 0,2.507319 -1.099985,2.84702 -2.313203,2.84702 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4161"/>
39
-
<path d="m 94.118867,63.854412 0,-6.551381 c 0.501464,-0.161763 1.16469,-0.291173 1.892621,-0.291173 1.617625,0 1.827916,0.77646 1.827916,1.536744 l 0,5.30581 1.488215,0 0,-5.208753 c 0,-1.876445 -1.213218,-3.008782 -3.251426,-3.008782 -1.892621,0 -3.380836,0.808812 -3.445541,0.841165 l 0,7.37637 1.488215,0 z" style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:16.17625046px;line-height:100%;font-family:'Maven Pro';-inkscape-font-specification:'Maven Pro, Medium';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4163"/>
40
-
</g>
41
-
<g style="font-style:normal;font-weight:normal;font-size:32.19625854px;line-height:125%;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#03a9f4;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1" id="text4477">
42
-
<path d="m 105.24414,53.529928 0,-1.351991 1.41487,0 0,1.351991 -1.41487,0 z m 0,10.312865 0,-8.504969 1.41487,0 0,8.504969 -1.41487,0 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4156"/>
43
-
<path d="m 114.23645,63.842793 0,-5.392245 q 0,-0.841064 -0.16507,-1.304829 -0.16507,-0.463764 -0.52665,-0.668135 -0.36158,-0.204371 -1.06115,-0.204371 -1.02186,0 -1.61139,0.699577 -0.58953,0.699577 -0.58953,1.941523 l 0,4.92848 -1.41487,0 0,-6.689213 q 0,-1.485619 -0.0472,-1.815756 l 1.33628,0 q 0.008,0.0393 0.0157,0.212231 0.008,0.172929 0.0157,0.400881 0.0157,0.220092 0.0314,0.841065 l 0.0236,0 q 0.48735,-0.880367 1.12404,-1.241946 0.64455,-0.369439 1.59566,-0.369439 1.39916,0 2.04371,0.699576 0.65242,0.691717 0.65242,2.295242 l 0,5.667359 -1.42274,0 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4158"/>
44
-
<path d="m 124.17987,61.492529 q 0,1.202643 -0.9118,1.855057 -0.90395,0.652415 -2.53892,0.652415 -1.5878,0 -2.45245,-0.518788 -0.85678,-0.526647 -1.11618,-1.634966 l 1.24981,-0.243673 q 0.18079,0.683856 0.74674,1.006133 0.56595,0.314417 1.57208,0.314417 1.07688,0 1.57209,-0.330137 0.50306,-0.330138 0.50306,-0.990413 0,-0.503066 -0.34586,-0.817483 -0.34585,-0.314416 -1.11618,-0.518787 l -1.01399,-0.267254 q -1.21836,-0.314417 -1.73715,-0.613113 -0.51093,-0.306556 -0.80176,-0.738879 -0.29084,-0.432322 -0.29084,-1.061156 0,-1.163341 0.82535,-1.768593 0.8332,-0.613112 2.421,-0.613112 1.40702,0 2.23236,0.495206 0.83321,0.495206 1.0533,1.587804 l -1.27339,0.157208 q -0.11791,-0.56595 -0.63669,-0.864646 -0.51093,-0.306556 -1.37558,-0.306556 -0.95897,0 -1.41487,0.290836 -0.45591,0.290835 -0.45591,0.880366 0,0.361579 0.18865,0.597391 0.18865,0.235813 0.55809,0.400882 0.36944,0.165068 1.55637,0.455904 1.12404,0.282975 1.61924,0.526647 0.49521,0.235813 0.77818,0.526648 0.29084,0.290836 0.44805,0.675996 0.1572,0.3773 0.1572,0.864646 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4160"/>
45
-
<path d="m 129.11621,63.779909 q -0.69957,0.18865 -1.43059,0.18865 -1.69785,0 -1.69785,-1.925801 l 0,-5.67522 -0.98255,0 0,-1.029714 1.03757,0 0.4166,-1.902221 0.94325,0 0,1.902221 1.57209,0 0,1.029714 -1.57209,0 0,5.368663 q 0,0.613113 0.19651,0.864646 0.20438,0.243673 0.69958,0.243673 0.28298,0 0.81748,-0.110046 l 0,1.045435 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4164"/>
46
-
<path d="m 132.48047,64.000001 q -1.28124,0 -1.9258,-0.675996 -0.64455,-0.675996 -0.64455,-1.855058 0,-1.320549 0.86464,-2.027987 0.87251,-0.707437 2.80617,-0.7546 l 1.91008,-0.03144 0,-0.463765 q 0,-1.037574 -0.44018,-1.485618 -0.44018,-0.448044 -1.38343,-0.448044 -0.95111,0 -1.38344,0.322277 -0.43232,0.322277 -0.51878,1.029715 l -1.47776,-0.133627 q 0.36158,-2.295241 3.41142,-2.295241 1.60352,0 2.41314,0.738879 0.80963,0.731018 0.80963,2.122311 l 0,3.662954 q 0,0.628833 0.16507,0.95111 0.16506,0.314416 0.62883,0.314416 0.20437,0 0.46376,-0.05502 l 0,0.880366 q -0.5345,0.125767 -1.09259,0.125767 -0.78605,0 -1.14762,-0.408742 -0.35372,-0.416602 -0.40089,-1.296968 l -0.0472,0 q -0.54237,0.974691 -1.26553,1.383433 -0.71529,0.400881 -1.74501,0.400881 z m 0.32228,-1.061156 q 0.77818,0 1.38343,-0.353719 0.60525,-0.353718 0.95111,-0.966831 0.35372,-0.620973 0.35372,-1.273387 l 0,-0.699577 -1.5485,0.03144 q -0.99827,0.01572 -1.51706,0.204371 -0.51093,0.188649 -0.78604,0.58167 -0.27512,0.393021 -0.27512,1.029715 0,0.691716 0.36944,1.069016 0.3773,0.3773 1.06902,0.3773 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4166"/>
47
-
<path d="m 139.27187,63.842793 0,-11.664856 1.41488,0 0,11.664856 -1.41488,0 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4168"/>
48
-
<path d="m 142.85622,63.842793 0,-11.664856 1.41488,0 0,11.664856 -1.41488,0 z" style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:16.09812927px;line-height:125%;font-family:Arimo;-inkscape-font-specification:'Arimo, Normal';text-align:start;writing-mode:lr-tb;text-anchor:start;fill:#03a9f4;fill-opacity:1" id="path4170"/>
49
-
</g>
50
-
</g>
51
-
</g>
52
-
</g>
53
-
</svg>
docs/static/gitea-push-hint.png
docs/static/gitea-push-hint.png
This is a binary file and will not be displayed.
-23
docs/static/open-in-gitpod.svg
-23
docs/static/open-in-gitpod.svg
···
1
-
<svg width="160" height="45" fill="none" xmlns="http://www.w3.org/2000/svg">
2
-
<g filter="url(#filter0_d)">
3
-
<rect x="2" y="2" width="156" height="40" rx="16" fill="#F9F9F9"/>
4
-
<path fill-rule="evenodd" clip-rule="evenodd" d="M30.425 11.174c.604 1.114.233 2.53-.83 3.164l-6.986 4.166a.378.378 0 00-.18.325v6.748c0 .134.069.258.18.325l5.714 3.407c.11.066.244.066.354 0l5.714-3.407a.378.378 0 00.18-.325V21.29l-4.986 2.936c-1.067.628-2.416.231-3.015-.886-.6-1.118-.22-2.532.846-3.16l7.008-4.127c2.048-1.206 4.576.345 4.576 2.806v6.718c0 1.803-.924 3.467-2.42 4.36l-5.713 3.407a4.596 4.596 0 01-4.734 0l-5.714-3.408C18.924 29.044 18 27.38 18 25.576V18.83c0-1.803.924-3.467 2.42-4.36l6.985-4.165c1.063-.634 2.415-.245 3.02.87z" fill="url(#paint0_linear)"/>
5
-
<path fill="#F9F9F9" d="M47 12.5h95v-1H47z"/>
6
-
<path d="M52.538 27.752c2.744 0 4.844-1.876 4.844-5.152 0-3.108-2.1-5.152-4.844-5.152s-4.802 2.002-4.802 5.152c0 3.29 2.058 5.152 4.802 5.152zm0-1.554c-1.736 0-2.912-1.316-2.912-3.598 0-2.226 1.162-3.598 2.912-3.598s2.954 1.4 2.954 3.598c0 2.31-1.218 3.598-2.954 3.598zm7.89 4.158V27.22c0-.196-.013-.378-.055-.658.434.7 1.022 1.19 2.17 1.19 1.736 0 3.066-1.414 3.066-3.626 0-2.17-1.19-3.682-2.996-3.682-1.078 0-1.806.476-2.24 1.204.042-.28.056-.462.056-.672v-.308H58.72v9.688h1.708zm1.695-3.948c-1.036 0-1.764-.938-1.764-2.31 0-1.414.742-2.296 1.764-2.296 1.092 0 1.75.952 1.75 2.296 0 1.372-.7 2.31-1.75 2.31zm7.866 1.344c1.848 0 3.052-1.078 3.192-2.478h-1.736c-.112.714-.714 1.134-1.456 1.134-1.036 0-1.722-.826-1.736-1.904h4.97v-.378c0-2.226-1.204-3.682-3.29-3.682-1.988 0-3.43 1.47-3.43 3.626 0 2.366 1.442 3.682 3.486 3.682zm-1.75-4.48c.098-.896.756-1.554 1.68-1.554.924 0 1.526.63 1.554 1.554H68.24zm8.006 4.228v-4.004c0-.952.616-1.694 1.456-1.694.798 0 1.288.63 1.288 1.638v4.06h1.708v-4.312c0-1.68-.896-2.744-2.408-2.744-1.078 0-1.722.518-2.1 1.204.042-.266.056-.476.056-.672v-.308h-1.708V27.5h1.708zm8.911-7.868h1.792V17.84h-1.792v1.792zm.042 1.036V27.5h1.708v-6.832h-1.708zm5.097 6.832v-4.004c0-.952.616-1.694 1.456-1.694.798 0 1.288.63 1.288 1.638v4.06h1.708v-4.312c0-1.68-.896-2.744-2.408-2.744-1.078 0-1.722.518-2.1 1.204.042-.266.056-.476.056-.672v-.308h-1.708V27.5h1.708zm13.238.252c1.526 0 2.52-.658 2.982-1.54-.07.322-.098.644-.098.98v.308h1.68v-5.222h-4.34v1.554h2.66v.07c0 1.4-1.134 2.296-2.59 2.296-1.792 0-3.024-1.372-3.024-3.598s1.26-3.598 3.066-3.598c1.302 0 2.17.756 2.296 1.736h1.89c-.182-1.904-1.764-3.29-4.214-3.29-2.954 0-4.928 2.128-4.928 5.152 0 3.136 1.848 5.152 4.62 5.152zm6.063-8.12h1.792V17.84h-1.792v1.792zm.042 1.036V27.5h1.708v-6.832h-1.708zm6.413 6.958c.434 0 .84-.07 1.008-.126v-1.288c-.168.028-.35.042-.518.042-.728 0-1.008-.42-1.008-1.134v-3.094h1.68v-1.358h-1.68v-2.464h-1.708v2.464h-1.554v1.358h1.554v3.346c0 1.526.77 2.254 2.226 2.254zm3.961 2.73V27.22c0-.196-.014-.378-.056-.658.434.7 1.022 1.19 2.17 1.19 1.736 0 3.066-1.414 3.066-3.626 0-2.17-1.19-3.682-2.996-3.682-1.078 0-1.806.476-2.24 1.204.042-.28.056-.462.056-.672v-.308h-1.708v9.688h1.708zm1.694-3.948c-1.036 0-1.764-.938-1.764-2.31 0-1.414.742-2.296 1.764-2.296 1.092 0 1.75.952 1.75 2.296 0 1.372-.7 2.31-1.75 2.31zm7.88 1.344c2.058 0 3.514-1.372 3.514-3.64 0-2.24-1.456-3.668-3.514-3.668-2.044 0-3.5 1.428-3.5 3.668 0 2.268 1.442 3.64 3.5 3.64zm0-1.344c-1.064 0-1.764-.84-1.764-2.296 0-1.484.728-2.31 1.764-2.31 1.05 0 1.778.826 1.778 2.31 0 1.456-.714 2.296-1.778 2.296zm7.551 1.344c1.26 0 1.876-.686 2.142-1.19-.056.238-.056.42-.056.658v.28h1.708v-9.8h-1.708v3.276c0 .21 0 .42.056.672-.392-.658-1.05-1.204-2.114-1.204-1.596 0-3.15 1.218-3.15 3.668 0 2.408 1.316 3.64 3.122 3.64zm.406-1.344c-1.022 0-1.792-.896-1.792-2.31 0-1.358.77-2.296 1.792-2.296s1.778.896 1.778 2.296c0 1.372-.756 2.31-1.778 2.31z" fill="#12100C"/>
7
-
</g>
8
-
<defs>
9
-
<linearGradient id="paint0_linear" x1="33.806" y1="13.629" x2="22.389" y2="30.86" gradientUnits="userSpaceOnUse">
10
-
<stop stop-color="#FFB45B"/>
11
-
<stop offset="1" stop-color="#FF8A00"/>
12
-
</linearGradient>
13
-
<filter id="filter0_d" x="0" y=".5" width="160" height="44" filterUnits="userSpaceOnUse" color-interpolation-filters="sRGB">
14
-
<feFlood flood-opacity="0" result="BackgroundImageFix"/>
15
-
<feColorMatrix in="SourceAlpha" values="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 127 0"/>
16
-
<feOffset dy=".5"/>
17
-
<feGaussianBlur stdDeviation="1"/>
18
-
<feColorMatrix values="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0.1 0"/>
19
-
<feBlend in2="BackgroundImageFix" result="effect1_dropShadow"/>
20
-
<feBlend in="SourceGraphic" in2="effect1_dropShadow" result="shape"/>
21
-
</filter>
22
-
</defs>
23
-
</svg>
