Skip to content

Kubernetes support, and support for base-URLS #31

@SpiderUnderUrBed

Description

@SpiderUnderUrBed

Hello, could you please consider adding kubernetes support, also whilst not a direct replacement, I would like it if it could do something to fit my use case and others, to better contextualize, here is the issue I am experincing, and what this plugin can do to help it:

kind: Middleware
metadata:
  name: strip-first-prefix
  namespace: default
spec:
#  replacePathRegex:
#    regex: "^/[^/]+(.*)"
#    replacement: "$1"
  stripPrefix:
    prefixes:
      #- "/dashboard"
      #- "/api"
      - "/gitea"
      - "/wordpress"
      - "/vaultwarden"
      - "/pdns"
      - "/glance"
      - "/immich"

So I have a issue. whenever I accessed all of my services via 192.168.1.22/wordpress for example. it forwarded that /wordpress to the actual wordpress domain, leading to page not found, however when i strip the initial proefix, i can access the base page, however, when lets say wordpress wants any css or assets, it will look at 192.168.1.22/assets (I am aware of wpsite to set a base domain, but i want something that works for all of my services)

If there was a way for this plugin to check what the service is coming from, search for the actual content appending a /wordpress or /immich before it, and return it with the first prefix stripped, I think that would fix my issue and provide extra utillity to this plugin as I doubt i am the only one with this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions