Manage Redirects Like a Pro

A powerful, yet simple to use, self-hosted redirect service.

re:Director enables you to redirect any domain simply by specifying where it should direct to. Make URLs shorter and easier to memorize.

• Manage Redirects: Create redirects for the domains you want to redirect to some target
• Filter Redirects: Filter you redirects by source, target or status
• Pause Redirects: Option to temporarily pause redirects and resume them at a later time
• Different HTTP Status Codes: Chose between different redirects like: Moved Permanently (301), Found (302), Temporary Redirect (307) and Permanent Redirect (308)
• and more upcoming!

Clone this repo, make sure to have Java 25 installed and run the following command:

./mvnw spring-boot:run

An image of the application can be pulled from Docker Hub.

You can run it using the following command:

docker run \
  --name re-director \
  -p 80:80 \
  -v re-director-data:/data \
  jensknipper/re-director:0.0.4

You can also run this application using Docker Compose Simply save the following code into a docker-compose.yml file and run docker-compose up.

services:
  re-director:
    image: jensknipper/re-director:0.0.4
    ports:
      - "80:80"
    volumes:
      - re-director-data:/data

volumes:
  re-director-data:

You might have quite a few applications running behind a Traefik reverse proxy. The configuration should then look like this.

services:
  traefik:
    image: traefik:v3.4
    command:
      - "--providers.docker"
      - "--entrypoints.web.address=:80"
    ports:
      - "80:80"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

  re-director:
    image: jensknipper/re-director:0.0.4
    expose:
      - 80
    volumes:
      - re-director-data:/data
    labels:
      - "traefik.http.routers.re-director.rule=Host(`re-director.localhost`) || HostRegexp(`.+`)"
      - "traefik.http.routers.re-director.entrypoints=web"
      - "traefik.http.routers.re-director.priority=1"

volumes:
  re-director-data:

Whenever there is a new release, new Docker images will be built and published to Docker Hub. Regular commits etc. will not trigger the images to be built.
By default amd64 and arm64 images will be built.

Before creating a release, make sure that:

• all tests pass
• you update the version in the pom.xml to the next version
• update all the mentioned versions in the documentation
• you are able to run the docker containers - build them locally to do that
  • run ./mvnw jib:dockerBuild to create the container locally
  • use the example files in the docker directory
  • go to http://localhost and check if the application is running
• create the new release here