From 9e1e49f16f44a54a7e735995b3ba0b3a718d5961 Mon Sep 17 00:00:00 2001 From: "Arthur K." Date: Wed, 11 Jun 2025 18:07:22 +0300 Subject: [PATCH] chore: stuff for local deployment --- .github/FUNDING.yml | 3 - .github/ISSUE_TEMPLATE.md | 77 -------------------- .github/ISSUE_TEMPLATE/bug_report.yml | 82 ---------------------- .github/ISSUE_TEMPLATE/config.yml | 8 --- .github/ISSUE_TEMPLATE/feature-request.yml | 33 --------- .github/PULL_REQUEST_TEMPLATE/mergeback.md | 7 -- .github/PULL_REQUEST_TEMPLATE/release.md | 7 -- .github/workflows/sync-docker-images.yaml | 26 ------- Dockerfile | 1 + README.md | 12 ++-- 10 files changed, 9 insertions(+), 247 deletions(-) delete mode 100644 .github/FUNDING.yml delete mode 100644 .github/ISSUE_TEMPLATE.md delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml delete mode 100644 .github/ISSUE_TEMPLATE/config.yml delete mode 100644 .github/ISSUE_TEMPLATE/feature-request.yml delete mode 100644 .github/PULL_REQUEST_TEMPLATE/mergeback.md delete mode 100644 .github/PULL_REQUEST_TEMPLATE/release.md delete mode 100644 .github/workflows/sync-docker-images.yaml diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml deleted file mode 100644 index b920e1793..000000000 --- a/.github/FUNDING.yml +++ /dev/null @@ -1,3 +0,0 @@ -# These are supported funding model platforms - -github: traefik diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md deleted file mode 100644 index 8d124b341..000000000 --- a/.github/ISSUE_TEMPLATE.md +++ /dev/null @@ -1,77 +0,0 @@ - - -### Do you want to request a *feature* or report a *bug*? - - - -Bug - - - -### What did you do? - - - -### What did you expect to see? - - - -### What did you see instead? - - - -### Output of `traefik version`: (_What version of Traefik are you using?_) - - - -``` -(paste your output here) -``` - -### What is your environment & configuration (arguments, toml, provider, platform, ...)? - -```toml -# (paste your configuration here) -``` - - - - -### If applicable, please paste the log output in DEBUG level (`--log.level=DEBUG` switch) - -``` -(paste your output here) -``` diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml deleted file mode 100644 index ce21d35ee..000000000 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ /dev/null @@ -1,82 +0,0 @@ -name: Bug Report (Traefik) -description: Create a report to help us improve. -body: - - type: checkboxes - id: terms - attributes: - label: Welcome! - description: | - The issue tracker is for reporting bugs and feature requests only. - For end-user related support questions, please use the [Traefik community forum](https://community.traefik.io/). - - All new/updated issues are triaged regularly by the maintainers. - All issues closed by a bot are subsequently double-checked by the maintainers. - - DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. - - options: - - label: Yes, I've searched similar issues on [GitHub](https://github.com/traefik/traefik/issues) and didn't find any. - required: true - - label: Yes, I've searched similar issues on the [Traefik community forum](https://community.traefik.io) and didn't find any. - required: true - - - type: textarea - attributes: - label: What did you do? - description: | - How to write a good bug report? - - - Respect the issue template as much as possible. - - The title should be short and descriptive. - - Explain the conditions which led you to report this issue: the context. - - The context should lead to something, an idea or a problem that you’re facing. - - Remain clear and concise. - - Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown) - placeholder: What did you do? - validations: - required: true - - - type: textarea - attributes: - label: What did you see instead? - placeholder: What did you see instead? - validations: - required: true - - - type: textarea - attributes: - label: What version of Traefik are you using? - description: | - `latest` is not considered as a valid version. - - Output of `traefik version`. - - For the Traefik Docker image (`docker run [IMAGE] version`), example: - ```console - $ docker run traefik version - ``` - placeholder: Paste your output here. - validations: - required: true - - - type: textarea - attributes: - label: What is your environment & configuration? - description: arguments, toml, provider, platform, ... - placeholder: Add information here. - value: | - ```yaml - # (paste your configuration here) - ``` - - Add more configuration information here. - validations: - required: true - - - type: textarea - attributes: - label: If applicable, please paste the log output in DEBUG level - description: "`--log.level=DEBUG` switch." - placeholder: Paste your output here. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 80c8c86b5..000000000 --- a/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1,8 +0,0 @@ -blank_issues_enabled: false -contact_links: - - name: Traefik Community Support - url: https://community.traefik.io/ - about: If you have a question, or are looking for advice, please post on our Discuss forum! The community loves to chime in to help. Happy Coding! - - name: Traefik Helm Chart Issues - url: https://github.com/traefik/traefik-helm-chart - about: Are you submitting an issue or feature enhancement for the Traefik helm chart? Please post in the traefik-helm-chart GitHub Issues. diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml deleted file mode 100644 index 5a092594d..000000000 --- a/.github/ISSUE_TEMPLATE/feature-request.yml +++ /dev/null @@ -1,33 +0,0 @@ -name: Feature Request (Traefik) -description: Suggest an idea for this project. -body: - - type: checkboxes - id: terms - attributes: - label: Welcome! - description: | - The issue tracker is for reporting bugs and feature requests only. For end-user related support questions, please refer to one of the following: - - the Traefik community forum: https://community.traefik.io/ - - DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS. - options: - - label: Yes, I've searched similar issues on [GitHub](https://github.com/traefik/traefik/issues) and didn't find any. - required: true - - label: Yes, I've searched similar issues on the [Traefik community forum](https://community.traefik.io) and didn't find any. - required: true - - - type: textarea - attributes: - label: What did you expect to see? - description: | - How to write a good issue? - - - Respect the issue template as much as possible. - - The title should be short and descriptive. - - Explain the conditions which led you to report this issue: the context. - - The context should lead to something, an idea or a problem that you’re facing. - - Remain clear and concise. - - Format your messages to help the reader focus on what matters and understand the structure of your message, use [Markdown syntax](https://help.github.com/articles/github-flavored-markdown) - placeholder: What did you expect to see? - validations: - required: true diff --git a/.github/PULL_REQUEST_TEMPLATE/mergeback.md b/.github/PULL_REQUEST_TEMPLATE/mergeback.md deleted file mode 100644 index dfc856011..000000000 --- a/.github/PULL_REQUEST_TEMPLATE/mergeback.md +++ /dev/null @@ -1,7 +0,0 @@ -### What does this PR do? - -Merge v{{.Version}} into master - -### Motivation - -Be sync. diff --git a/.github/PULL_REQUEST_TEMPLATE/release.md b/.github/PULL_REQUEST_TEMPLATE/release.md deleted file mode 100644 index 226a85a73..000000000 --- a/.github/PULL_REQUEST_TEMPLATE/release.md +++ /dev/null @@ -1,7 +0,0 @@ -### What does this PR do? - -Prepare release v{{.Version}}. - -### Motivation - -Create a new release. diff --git a/.github/workflows/sync-docker-images.yaml b/.github/workflows/sync-docker-images.yaml deleted file mode 100644 index 6f0b3c103..000000000 --- a/.github/workflows/sync-docker-images.yaml +++ /dev/null @@ -1,26 +0,0 @@ -name: Sync Docker Images - -on: - workflow_dispatch: - schedule: - - cron: "0 0 * * *" # Run every day - -jobs: - sync: - runs-on: ubuntu-latest - permissions: - packages: write - contents: read - if: github.repository == 'traefik/traefik' - - steps: - - uses: actions/checkout@v4 - - - uses: imjasonh/setup-crane@v0.4 - - - name: Sync - run: | - EXCLUDED_TAGS="1.7.9-alpine v1.0.0-beta.392 v1.0.0-beta.404 v1.0.0-beta.704 v1.0.0-rc1 v1.7.9-alpine" - EXCLUDED_REGEX=$(echo $EXCLUDED_TAGS | sed 's/ /|/g') - diff <(crane ls traefik) <(crane ls ghcr.io/traefik/traefik) | grep '^<' | awk '{print $2}' | while read -r tag; do [[ "$tag" =~ ^($EXCLUDED_REGEX)$ ]] || (echo "Processing image: traefik:$tag"; crane cp "traefik:$tag" "ghcr.io/traefik/traefik:$tag"); done - crane cp traefik:latest ghcr.io/traefik/traefik:latest diff --git a/Dockerfile b/Dockerfile index 0e08e72da..10ee5e2b5 100644 --- a/Dockerfile +++ b/Dockerfile @@ -5,6 +5,7 @@ RUN apk add --no-cache --no-progress ca-certificates tzdata ARG TARGETPLATFORM COPY ./dist/$TARGETPLATFORM/traefik / +COPY ./traefik.yml /etc/traefik/traefik.yml EXPOSE 80 VOLUME ["/tmp"] diff --git a/README.md b/README.md index 711e19b8c..472057a3a 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,7 @@ +# My modified version of Traefik +slightly modified version of traefik, will be rebased on the latest tag from time to time +this version includes callbacks to external services on configuration update and custom docker label mappings +feel free to check out last 2 commits, they are like 100sloc together

@@ -42,14 +46,14 @@ Pointing Traefik at your orchestrator should be the _only_ configuration step yo Imagine that you have deployed a bunch of microservices with the help of an orchestrator (like Swarm or Kubernetes) or a service registry (like etcd or consul). Now you want users to access these microservices, and you need a reverse proxy. -Traditional reverse-proxies require that you configure _each_ route that will connect paths and subdomains to _each_ microservice. -In an environment where you add, remove, kill, upgrade, or scale your services _many_ times a day, the task of keeping the routes up to date becomes tedious. +Traditional reverse-proxies require that you configure _each_ route that will connect paths and subdomains to _each_ microservice. +In an environment where you add, remove, kill, upgrade, or scale your services _many_ times a day, the task of keeping the routes up to date becomes tedious. **This is when Traefik can help you!** -Traefik listens to your service registry/orchestrator API and instantly generates the routes so your microservices are connected to the outside world -- without further intervention from your part. +Traefik listens to your service registry/orchestrator API and instantly generates the routes so your microservices are connected to the outside world -- without further intervention from your part. -**Run Traefik and let it do the work for you!** +**Run Traefik and let it do the work for you!** _(But if you'd rather configure some of your routes manually, Traefik supports that too!)_ ![Architecture](docs/content/assets/img/traefik-architecture.png)