mirror of
https://gitea.com/gitea/docs.git
synced 2026-09-18 20:18:52 +00:00
Backport #23993 by @6543 close #23521 Signed-off-by: 6543 <[email protected]> Co-authored-by: 6543 <[email protected]> Co-authored-by: delvh <[email protected]> Co-authored-by: a1012112796 <[email protected]> Co-authored-by: wxiaoguang <[email protected]>
This commit is contained in:
committed by
GitHub
co-authored by
6543
delvh
a1012112796
wxiaoguang
parent
5a393dfbac
commit
3b5d7f8d06
@@ -118,6 +118,14 @@ The correct path for the template(s) will be relative to the `CustomPath`
|
||||
2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file)
|
||||
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.
|
||||
|
||||
## Does Gitea have a "GitHub/GitLab pages" feature?
|
||||
|
||||
Gitea doesn't provide a built-in Pages server. You need a dedicated domain to serve static pages to avoid CSRF security risks.
|
||||
|
||||
For simple usage, you can use a reverse proxy to rewrite & serve static contents from Gitea's raw file URLs.
|
||||
|
||||
And there are already available third-party services, like a standalone [pages server](https://codeberg.org/Codeberg/pages-server) or a [caddy plugin](https://github.com/42wim/caddy-gitea), that can provide the required functionality.
|
||||
|
||||
## Active user vs login prohibited user
|
||||
|
||||
In Gitea, an "active" user refers to a user that has activated their account via email.
|
||||
|
||||
Reference in New Issue
Block a user