Compare commits

...

2 Commits

Author SHA1 Message Date
183e77ea61 feat: Restrict the CI to Go files
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
2024-01-13 17:58:21 +01:00
3af531fdcc docs: Document the alt CNAME approach 2024-01-13 17:54:02 +01:00
2 changed files with 22 additions and 1 deletions

View File

@ -1,11 +1,20 @@
x-anchors:
golang_filter: &golang_filter
- path:
include: [ "**/*.go" ]
steps: steps:
build: build:
image: "golang:1.21.5-alpine" image: "golang:1.21.5-alpine"
commands: commands:
- go build ./cmd/rio - go build ./cmd/rio
- go test $(go list ./... | grep -v /vendor/) - go test $(go list ./... | grep -v /vendor/)
when:
- <<: *golang_filter
lint: lint:
image: "golang:1.21.5-alpine" image: "golang:1.21.5-alpine"
commands: commands:
- go fmt $(go list ./... | grep -v /vendor/) - go fmt $(go list ./... | grep -v /vendor/)
- go vet $(go list ./... | grep -v /vendor/) - go vet $(go list ./... | grep -v /vendor/)
when:
- <<: *golang_filter

View File

@ -72,6 +72,18 @@ _acme-challenge.cooldomain.rio. 3600 IN CNAME cooldomain.rio.pages.example
This additionally requires your repository to have a file named `CNAME` that contains This additionally requires your repository to have a file named `CNAME` that contains
the domain to use (`cooldomain.rio` in this case). the domain to use (`cooldomain.rio` in this case).
### Alternate CNAME Domains
If there is a situation where you want to use a CNAME redirect on a (sub-) domain,
where having a CNAME is not feasible, you can configure an "alternate CNAME".
This is a special TXT record that contains the "CNAME" you want to specify.
```
; Example for Bind
cooldomain.rio. 3600 IN A <IPv4 of rio>
_rio-cname.cooldomain.rio. 3600 IN TXT "cname=user.pages.example.org"
```
### Repository Redirects ### Repository Redirects
If you have multiple repositories with pages (and you use a CNAME), you can additionally If you have multiple repositories with pages (and you use a CNAME), you can additionally