Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/42wim/caddy-gitea
Github pages (and more) for gitea using caddy
https://github.com/42wim/caddy-gitea
caddy-plugin gitea
Last synced: 8 days ago
JSON representation
Github pages (and more) for gitea using caddy
- Host: GitHub
- URL: https://github.com/42wim/caddy-gitea
- Owner: 42wim
- License: apache-2.0
- Created: 2022-10-30T12:07:18.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2023-07-30T20:27:46.000Z (over 1 year ago)
- Last Synced: 2024-10-23T07:54:08.310Z (17 days ago)
- Topics: caddy-plugin, gitea
- Language: Go
- Homepage:
- Size: 105 KB
- Stars: 117
- Watchers: 5
- Forks: 8
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-gitea - Caddy Gitea Plugin - Caddy2 plugin enables GitHub pages-like features in Gitea, requiring a wildcard CNAME to your Gitea host. (Applications / Web Hosting)
- awesome-gitea - Caddy Gitea Plugin (42wim/caddy-gitea) - Caddy2 plugin enables GitHub pages-like features in Gitea, requiring a wildcard CNAME to your Gitea host. (Applications / Web Hosting)
README
# caddy-gitea
[Gitea](https://gitea.io) plugin for [Caddy v2](https://github.com/caddyserver/caddy).
This allows you to have github pages (with more features) in Gitea.
This also requires you to setup a wildcard CNAME to your gitea host.
For now markdown files (with `.md` extension) will also be automatically generated to HTML.
- [caddy-gitea](#caddy-gitea)
- [Getting started](#getting-started)
- [Caddy config](#caddy-config)
- [DNS config](#dns-config)
- [Gitea config](#gitea-config)
- [gitea-pages repo](#gitea-pages-repo)
- [any repo with configurable allowed branch/tag/commits](#any-repo-with-configurable-allowed-branchtagcommits)
- [any repo with all branches/tags/commits exposed](#any-repo-with-all-branchestagscommits-exposed)
- [Building caddy](#building-caddy)
## Getting started
### Caddy config
The Caddyfile below creates a webserver listening on :3000 which will interact with gitea on using `agiteatoken` as the token.
The agiteatoken should be a token from gitea that has the necessary read rights on the repo's that you want to expose.
```Caddyfile
{
order gitea before file_server
}
:3000
gitea {
server https://yourgitea.yourdomain.com
token agiteatoken
domain pages.yourdomain.com #this is optional
}
```
### DNS config
This works with a wildcard domain. So you'll need to make a *.pages.yourdomain.com CNAME to the server you'll be running caddy on.
(this doesn't need to be the same server as gitea).
Depending on the gitea config below you'll be able to access your pages using:
- (org is the organization or username)
- (org is the organization or username)
-
-
- (if you have created a gitea-pages repo it'll be served on the root)
### Gitea config
There are multiple options to expose your repo's as a page, that you can use both at the same time.
- creating a gitea-pages repo with a gitea-pages branch and a gitea-pages topic
- adding a gitea-pages branch to any repo of choice and a gitea-pages topic
- adding a gitea-pages-allowall topic to your repo (easiest, but less secure)
#### gitea-pages repo
e.g. we'll use the `yourorg` org.
1. create a `gitea-pages` repo in `yourorg` org
2. Add a `gitea-pages` topic to this `gitea-pages` repo (this is used to opt-in your repo),
3. Create a `gitea-pages` branch in this `gitea-pages` repo.
4. Put your content in this branch. (eg file.html)
Your content will now be available on
#### any repo with configurable allowed branch/tag/commits
e.g. we'll use the `yourrepo` repo in the `yourorg` org and there is a `file.html` in the `master` branch and a `otherfile.html` in the `dev` branch. The `master` branch is your default branch.
1. Add a `gitea-pages` topic to the `yourrepo` repo (this is used to opt-in your repo).
2. Create a `gitea-pages` branch in this `yourrepo` repo.
3. Put a `gitea-pages.toml` file in this `gitea-pages` branch of `yourrepo` repo. (more info about the content below)
The `gitea-pages.toml` file will contain the git reference (branch/tag/commit) you allow to be exposed.
To allow everything use the example below:
```toml
allowedrefs=["*"]
```
To only allow main and dev:
```toml
allowedrefs=["main","dev"]
```
- Your `file.html` in the `master` branch will now be available on
- Your `file.html` in the `master` branch will now be available on
- Your `otherfile.html` in the `dev` branch will now be available on
- Your `otherfile.html` in the `dev` branch will now be available on
#### any repo with all branches/tags/commits exposed
e.g. we'll use the `yourrepo` repo in the `yourorg` org and there is a `file.html` in the `master` branch and a `otherfile.html` in the `dev` branch. The `master` branch is your default branch.
1. Add a `gitea-pages-allowall` topic to the `yourrepo` repo (this is used to opt-in your repo).
- Your `file.html` in the `master` branch will now be available on
- Your `file.html` in the `master` branch will now be available on
- Your `otherfile.html` in the `dev` branch will now be available on
- Your `otherfile.html` in the `dev` branch will now be available on
## Building caddy
As this is a 3rd party plugin you'll need to build caddy (or use the binaries).
To build with this plugin you'll need to have go1.19 installed.
```go
go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest #this will install xcaddy in ~/go/bin
~/go/bin/xcaddy build --with github.com/42wim/[email protected]
```