You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the `CustomPath` folder can't be found despite checking `gitea help`, check the `GITEA_CUSTOM`
41
41
environment variable; this can be used to override the default path to something else.
@@ -87,14 +87,14 @@ directory at the top of this document).
87
87
Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://golang.org/pkg/html/template/),
88
88
which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory.
89
89
90
-
To obtain any embedded file (including templates), the [`gitea embedded` tool]({{< relref "doc/advanced/cmd-embedded.en-us.md" >}}) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/master/templates) directory of Gitea source (Note: the example link is from the `master` 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]({{< relref "doc/advanced/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).
91
91
92
92
Be aware that any statement contained inside `{{` and `}}` are Gitea's template syntax and
93
93
shouldn't be touched without fully understanding these components.
94
94
95
95
### Customizing startpage / homepage
96
96
97
-
Copy [`home.tmpl`](https://github.com/go-gitea/gitea/blob/master/templates/home.tmpl) for your version of Gitea from `templates` to `$GITEA_CUSTOM/templates`.
97
+
Copy [`home.tmpl`](https://github.com/go-gitea/gitea/blob/main/templates/home.tmpl) for your version of Gitea from `templates` to `$GITEA_CUSTOM/templates`.
98
98
Edit as you wish.
99
99
Dont forget to restart your gitea to apply the changes.
100
100
@@ -113,7 +113,7 @@ For more information, see [Adding Legal Pages](https://docs.gitea.io/en-us/addin
113
113
You can add new tabs in the same way, putting them in `extra_tabs.tmpl`.
114
114
The exact HTML needed to match the style of other tabs is in the file
115
115
`templates/repo/header.tmpl`
116
-
([source in GitHub](https://github.com/go-gitea/gitea/blob/master/templates/repo/header.tmpl))
116
+
([source in GitHub](https://github.com/go-gitea/gitea/blob/main/templates/repo/header.tmpl))
117
117
118
118
### Other additions to the page
119
119
@@ -258,7 +258,7 @@ Then restart gitea and open a STL file on your gitea instance.
258
258
259
259
The `$GITEA_CUSTOM/templates/mail` folder allows changing the body of every mail of Gitea.
Override by making a copy of the file under `$GITEA_CUSTOM/templates/mail` using a
264
264
full path structure matching source.
@@ -282,7 +282,7 @@ To add custom .gitignore, add a file with existing [.gitignore rules](https://gi
282
282
283
283
### Labels
284
284
285
-
To add a custom label set, add a file that follows the [label format](https://github.com/go-gitea/gitea/blob/master/options/label/Default) to `$GITEA_CUSTOM/options/label`
285
+
To add a custom label set, add a file that follows the [label format](https://github.com/go-gitea/gitea/blob/main/options/label/Default) to `$GITEA_CUSTOM/options/label`
286
286
`#hex-color label name ; label description`
287
287
288
288
### Licenses
@@ -293,7 +293,7 @@ To add a custom license, add a file with the license text to `$GITEA_CUSTOM/opti
293
293
294
294
Locales are managed via our [crowdin](https://crowdin.com/project/gitea).
295
295
You can override a locale by placing an altered locale file in `$GITEA_CUSTOM/options/locale`.
296
-
Gitea's default locale files can be found in the [`options/locale`](https://github.com/go-gitea/gitea/tree/master/options/locale) source folder and these should be used as examples for your changes.
296
+
Gitea's default locale files can be found in the [`options/locale`](https://github.com/go-gitea/gitea/tree/main/options/locale) source folder and these should be used as examples for your changes.
297
297
298
298
To add a completely new locale, as well as placing the file in the above location, you will need to add the new lang and name to the `[i18n]` section in your `app.ini`. Keep in mind that Gitea will use those settings as **overrides**, so if you want to keep the other languages as well you will need to copy/paste the default values and add your own to them.
Copy file name to clipboardExpand all lines: docs/content/doc/developers/hacking-on-gitea.en-us.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ from within the `$GOPATH`, hence the `go get` approach is no longer recommended.
86
86
87
87
## Forking Gitea
88
88
89
-
Download the master Gitea source code as above. Then, fork the
89
+
Download the main Gitea source code as above. Then, fork the
90
90
[Gitea repository](https://github.com/go-gitea/gitea) on GitHub,
91
91
and either switch the git remote origin for your fork or add your fork as another remote:
92
92
@@ -123,7 +123,7 @@ TAGS="bindata sqlite sqlite_unlock_notify" make build
123
123
124
124
The `build` target will execute both `frontend` and `backend` sub-targets. If the `bindata` tag is present, the frontend files will be compiled into the binary. It is recommended to leave out the tag when doing frontend development so that changes will be reflected.
125
125
126
-
See `make help` for all available `make` targets. Also see [`.drone.yml`](https://github.com/go-gitea/gitea/blob/master/.drone.yml) to see how our continuous integration works.
126
+
See `make help` for all available `make` targets. Also see [`.drone.yml`](https://github.com/go-gitea/gitea/blob/main/.drone.yml) to see how our continuous integration works.
127
127
128
128
## Building continuously
129
129
@@ -276,7 +276,7 @@ require `git lfs` to be installed. Other database tests are available but
Copy file name to clipboardExpand all lines: docs/content/doc/developers/migrations.en-us.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ repository data from other git host platforms to Gitea or, in the future, migrat
20
20
git host platforms.
21
21
Currently, migrations from Github, Gitlab, and other Gitea instances are implemented.
22
22
23
-
First of all, Gitea defines some standard objects in packages [modules/migrations/base](https://github.com/go-gitea/gitea/tree/master/modules/migrations/base).
23
+
First of all, Gitea defines some standard objects in packages [modules/migrations/base](https://github.com/go-gitea/gitea/tree/main/modules/migrations/base).
24
24
They are `Repository`, `Milestone`, `Release`, `ReleaseAsset`, `Label`, `Issue`, `Comment`, `PullRequest`, `Reaction`, `Review`, `ReviewComment`.
25
25
26
26
## Downloader Interfaces
@@ -31,11 +31,11 @@ To migrate from a new git host platform, there are two steps to be updated.
31
31
- You should implement a `DownloaderFactory` which will be used to detect if the URL matches and create the above `Downloader`.
32
32
- You'll need to register the `DownloaderFactory` via `RegisterDownloaderFactory` on `init()`.
33
33
34
-
You can find these interfaces in [downloader.go](https://github.com/go-gitea/gitea/blob/master/modules/migrations/base/downloader.go).
34
+
You can find these interfaces in [downloader.go](https://github.com/go-gitea/gitea/blob/main/modules/migrations/base/downloader.go).
35
35
36
36
## Uploader Interface
37
37
38
38
Currently, only a `GiteaLocalUploader` is implemented, so we only save downloaded
39
39
data via this `Uploader` to the local Gitea instance. Other uploaders are not supported at this time.
40
40
41
-
You can find these interfaces in [uploader.go](https://github.com/go-gitea/gitea/blob/master/modules/migrations/base/uploader.go).
41
+
You can find these interfaces in [uploader.go](https://github.com/go-gitea/gitea/blob/main/modules/migrations/base/uploader.go).
Copy file name to clipboardExpand all lines: docs/content/doc/installation/with-docker-rootless.en-us.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -266,7 +266,7 @@ docker-compose up -d
266
266
267
267
## Managing Deployments With Environment Variables
268
268
269
-
In addition to the environment variables above, any settings in `app.ini` can be set or overridden with an environment variable of the form: `GITEA__SECTION_NAME__KEY_NAME`. These settings are applied each time the docker container starts. Full information [here](https://github.com/go-gitea/gitea/tree/master/contrib/environment-to-ini).
269
+
In addition to the environment variables above, any settings in `app.ini` can be set or overridden with an environment variable of the form: `GITEA__SECTION_NAME__KEY_NAME`. These settings are applied each time the docker container starts. Full information [here](https://github.com/go-gitea/gitea/tree/main/contrib/environment-to-ini).
270
270
271
271
These environment variables can be passed to the docker container in `docker-compose.yml`. The following example will enable an smtp mail server if the required env variables `GITEA__mailer__FROM`, `GITEA__mailer__HOST`, `GITEA__mailer__PASSWD` are set on the host or in a `.env` file in the same directory as `docker-compose.yml`:
0 commit comments