1 day ago · 5 min read1076 words · Tech · hide · 0 comments

My GitLab server is running on a virtual machine behind a Traefik reverse proxy. This saves me money, since I don’t have to rent additional IP addresses, but it also means that GitLab pages does not work properly. It requires it’s own dedicated IP for custom domain hosting. To make the handling of the routes a little bit more git-like, I created a repo, placed a YAML file containing the Traefik routes for GitLab pages into it and used Traefiks HTTP Provider to poll the YAML through a very simple python HTTP server from GitLabs package registry. Steps Prepare: Create a repo and place the traefik.yml routes file (see below) into it Use GitLab CI, the JSON schema and the validation script to ensure proper syntax (see below) Configure branches and package registry settings properly to prevent unauthorized changes Let the pipeline run to create a generic package containing the YAML file Setup webserver: Create a deploy token with read_package_registry permission Craft the GitLab API…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.