Skip to content

Kaneo - use a single application service instead of two (replicate Kaneo configuration) - #343

Open
DimitriHautot wants to merge 1 commit into
tailscale-dev:mainfrom
DimitriHautot:update-kaneo-to-single-container
Open

DimitriHautot wants to merge 1 commit into
tailscale-dev:mainfrom
DimitriHautot:update-kaneo-to-single-container

Conversation

@DimitriHautot

Copy link
Copy Markdown

Kaneo: fix services

Description

Recently, the Kaneo application code has been merged into a single service, so no distinct frontend + backend anymore, just one service.
Official documentation here.

Related Issues

  • None.

Verification

Edited the.env file:

  • added value for TS_AUTHKEY
  • set my own tailnet in the KANEO_CLIENT_URL
  • generated a random value for AUTH_SECRET

Then docker compose up
image
image

Checklist

  • I have performed a self-review of my code and followed the templates structure.
  • I have added verification that the stack works as expected.
  • I have updated necessary documentation (e.g. frontpage README.md ).
  • I have selected the correct label(s) for this PR.

Additional Context

  • None.

…ce into the only one, 'kaneo'.

Removed duplicate and now useless keys in .env file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant