Hello Uitsmijter Team,
currently the main headline says this is
A versatile OAuth2 authorization server and Traefik middleware for Kubernetes and Docker.
I wanted to try this out on Docker first as I don’t want to install it in a Kubernetes cluster yet but could not find any instructions in the documentation - is this currently supported and if yes, is there documentation regarding how to do it with Docker/Docker Compose?
Cheers,
Tikl
Hello @tikl,
welcome to the forum. Nice that you have found us here.
Docker support is very important for Uitsmijter and plays an important role alongside Kubernetes integration. We are sure that a solid login solution can bring a decisive advantage, especially for smaller projects. Uitsmijter presents itself as a plug & play solution both as an OAuth server and in interceptor mode. All functions are also fully supported in Docker-based installations.
With the configurability of the Docker solution, we want to make it super easy for smaller projects to create a secure and easy-to-implement solution. We want to significantly simplify the development process for websites, portals and apps and enable later scalability. We have had this in mind from the very beginning and weigh up every feature accordingly.
On our roadmap for version 1.0, both the Kubernetes mode with CustomResourceDefinitions and the Docker mode were crucial and were planned from the outset.
To create custom login forms and develop your applications locally, Docker mode is an ideal playground. This is how our developers validate special requirements that some of our enterprise customers need before we deploy custom settings to the clusters since the first days.
We at Uitsmijter believe that all applications, whether they are simply websites behind a Basic-Auth, or portals, can be implemented excellently with Uitsmijter and that it will be a relief for every developer to use Uitsmijter as a login solution. We want to make sure that installation and commissioning is as easy and convenient as possible.
As you have already noticed, there is currently little information about the Docker environment in the public documentation and there is currently a lack of examples. The current version 0.9.5 supports this mode, but still has some more complicated settings that we have currently fixed and are testing in the release candidate for 0.9.6. In fact, the individual feature branches are currently being integrated and a documentation page is being created.
Before we release the version, we want to have it production-ready. A release including documentation is planned for mid-September.
Development and stabilization takes place online. The following resources can help you validate in advance whether Uitsmijter meets your needs.
Docker-Compose example: GitHub - uitsmijter/docker-compose: Docker Compose Files for Uitsmijter
Installation instructions: Documentation/content/installation/docker.md at feature/docker · uitsmijter/Documentation · GitHub
Current status (branch): GitHub - uitsmijter/Uitsmijter at feature/docker-only
We would love to discuss your experiences here and hear more about your intended use and wishes for the product.
We communicate closely with the community to continuously improve the product and make it easier to integrate into your projects.
I would like to ask you, if you have some time, to look over the branches and criticize aspects that we may have overlooked or not yet fully specified. We would love to make Uitsmijter the optimal solution for your needs and - if you can - please tell us about your experience with Uitsmijter. We are here to help and constantly improve the product based on the experiences of the wider audience.
Thanks a lot,
kris.
If you want to have a quick setup, you may want to checkout this PR: Feature/docker only by KrisSimon · Pull Request #18 · uitsmijter/Uitsmijter · GitHub
You can checkout the Branch and start a fully usable Uitsmijter with the tooling command ./tooling.sh --run-docker
Thanks for the extensive reply, I will have a look at it! In the quote above you were talking about September, was that a typo or do you even mean September 2025?
Uh, my fault, sorry, that was a typo indeed! The release is indeed very close to completion, and I am excited to share that it should be out in the next few days. I appreciate your patience and enthusiasm for this update!
Awesome, thanks for clarifying! I will keep an eye out and try it out in a few days then…