Open
Conversation
crypt0rr
requested changes
Apr 10, 2026
Collaborator
There was a problem hiding this comment.
Please make sure to use the standard .env file in the templates as default. Leave the comments in the file as well, thanks! 🙏🏼
You may request a review again after changes have been made, so we can merge!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Title: Update Kaneo compose.yaml to v2.6.0
Description
Kaneo's configuration files were outdated and did not work with the latest official images.
This PR updates the compose.yaml and env file to match Kaneo's latest release.
Related Issues
Type of Change
How Has This Been Tested?
docker compose up -dChecklist
README.md)Additional Notes
In order for the frontend to be able to communicate with the backend, I added a second proxy handler that matches
/apitolocalhost:<backend-port>/api/. By doing so, the API can be accessed using the same MagicDNS url as the WebUI (by adding e.g./api/auth/get-sessionat the end). This removes the need to create a separate Tailscale container just for the backend.