Overview

This is an all-in-one pages server for Gitea. It works and uses similar/same conventions as Github Pages.

You can operate it in 2 modes, either simple (default) or classic (similar to how Github Pages operates).

simple:

In simple mode no special DNS setup is required and the access to the hosted sides are always according to the pattern

http(s)://<your-server-hostname>/<organization>/<repository>

classic:

In classic mode the access to the pages goes according to these two patterns:

http(s)://<organization>.<your-server-hostname>/<repository>

or

http(s)://<organization>.<your-server-hostname>

The latter url scheme with serves the content of the repo named <organization>.gitea-pages of the organization (with default settings).

Classic mode requires that you setup a wildcard CNAME in DNS for your gitea pages host (see below for more details). You also need a wildcard HTTPS certificate if you want to run with HTTPS.

Usage

To run the server in simple mode you need a minimal configuration (filename Caddyfile) like this (replace your-gitea-server and gitea_access_token):

{
    order gitea-pages before file_server
}
:8080
gitea-pages {
    server https://your-gitea-server
    token gitea-access-token
}

Afterward you can simply run:

./caddy run --config Caddyfile

If you build/use the docker container you can run it like this:

# Create a Caddyfile (configuration file) first !
docker run -v $(pwd)/Caddyfile:/etc/caddy/Caddyfile -p 8080:8080 gitea-pages

Configuration

These are the possible configuration options with their defaults:

{
    order gitea-pages before file_server
}
:8080
gitea-pages {
    server https://your-gitea-server
    token gitea-access-token
    pages_branch gitea-pages
    postfix_pages_repository gitea-pages
    url_scheme simple
}
log {
    level debug
}

Option	Description
server	The URL of your Gitea server.
token	Your access token for the Gitea API. This token is used to authenticate requests made to the Gitea server.
pages_branch	The branch in your repository that contains the static files for your website or documentation. By default, this would be the branch "gitea-pages"
postfix_pages_repository	The (domain) postfix used for the pages repository. (This could be the domain where your site will be accessible, such as "gitea.io".)
url_scheme	The URL scheme to use for the pages. "simple" or "classic

For example, if you want to assemble the same "look and feel" then on github you could set following settings in the config:

pages_branch	gh-pages
postfix_pages_repository	github.io
url_scheme	classic

Development

The project is implemented as an extension for Caddy . More details can be found at: https://caddyserver.com/docs/extending-caddy

Build

To build the server xcaddy need to be installed.

# Installing xcaddy
go install github.com/caddyserver/xcaddy/cmd/xcaddy@latest

To build the server binary simply run

# Build a specific version
xcaddy build --with github.com/simongregorebner/caddy-gitea@v0.0.1

# Build with specific commit (that was pushed to github)
xcaddy build --with github.com/simongregorebner/caddy-gitea@f4a6a77

# Build locally
xcaddy build --with github.com/simongregorebner/caddy-gitea=.

Docker

To build the server and create a docker image you can use:

docker build -t gitea-pages .

# cross platform build
docker build --platform=linux/amd64 -t gitea-pages .

Testing

If you are running/testing the server in simple mode:

curl "http://localhost:8080/<organization>/<repository>[/index.html | /<path>]"

If running in classic mode:

# testing organization repo
curl -H "Host: <organisation>.<your testserver name>" "http://localhost:8080/"
# testing a specific repo of the organization
curl -H "Host: <organisation>.<your testserver name>" "http://localhost:8080/<repository>"

Acknowledgements

This project is an extremely simplified rewrite of the https://github.com/42wim/caddy-gitea project.