starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #2154] [MERGED] [docs] Add Ouroboros to community web ui list #2529

New Issue
Closed
opened 2025-12-29 03:21:40 +01:00 by adam · 0 comments
adam commented 2025-12-29 03:21:40 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/2154
Author: @yellowsink
Created: 9/26/2024
Status: ✅ Merged
Merged: 9/27/2024
Merged by: @kradalby

Base: main ← Head: patch-1

📝 Commits (1)

  • 6b23a46 Add ouroboros to web ui list

📊 Changes

1 file changed (+7 additions, -6 deletions)

View changed files

📝 docs/web-ui.md (+7 -6)

📄 Description

  • have read the CONTRIBUTING.md file
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • added unit tests
  • added integration tests
  • updated documentation if needed
  • updated CHANGELOG.md

Hi! I have developed a UI for Headscale which I have running in production on my server currently.
It is designed for multi-user tailnets, to allow users to manage their nodes entirely on their own, without providing any sysadmin features.
It offers management (rename, delete, logout, exit node, routes) of nodes, and intercepts the /register endpoint (if using a correctly configured reverse proxy), to allow users to add their own nodes.

Users must authenticate through Github OAuth2 and the list of allowed users are predefined up-front by the admin.

image

image

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/2154 **Author:** [@yellowsink](https://github.com/yellowsink) **Created:** 9/26/2024 **Status:** ✅ Merged **Merged:** 9/27/2024 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`6b23a46`](https://github.com/juanfont/headscale/commit/6b23a4662110d3e69f4b0a9eb89b818ed803f7c8) Add ouroboros to web ui list ### 📊 Changes **1 file changed** (+7 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `docs/web-ui.md` (+7 -6) </details> ### 📄 Description <!-- Headscale is "Open Source, acknowledged contribution", this means that any contribution will have to be discussed with the Maintainers before being submitted. This model has been chosen to reduce the risk of burnout by limiting the maintenance overhead of reviewing and validating third-party code. Headscale is open to code contributions for bug fixes without discussion. If you find mistakes in the documentation, please submit a fix to the documentation. --> <!-- Please tick if the following things apply. You… --> - [x] have read the [CONTRIBUTING.md](./CONTRIBUTING.md) file - [ ] raised a GitHub issue or discussed it on the projects chat beforehand - [ ] added unit tests - [ ] added integration tests - [x] updated documentation if needed - [ ] updated CHANGELOG.md <!-- If applicable, please reference the issue using `Fixes #XXX` and add tests to cover your new code. --> Hi! I have developed a UI for Headscale which I have running in production on my server currently. It is designed for multi-user tailnets, to allow users to manage their nodes entirely on their own, without providing any sysadmin features. It offers management (rename, delete, logout, exit node, routes) of nodes, and intercepts the /register endpoint (if using a correctly configured reverse proxy), to allow users to add their own nodes. Users must authenticate through Github OAuth2 and the list of allowed users are predefined up-front by the admin. ![image](https://github.com/user-attachments/assets/b0455891-fedb-47e9-b096-f7d801331936) ![image](https://github.com/user-attachments/assets/c19efd93-e05b-4a81-af37-2afb6a1f29eb) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 03:21:40 +01:00
adam closed this issue 2025-12-29 03:21:40 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#2529
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?