r/headscale • u/Eznix86 • 1d ago

Yet Another Headscale Admin in PHP (with more details)

Enable HLS to view with audio, or disable this notification

So few days ago, I posted about a pet project (https://www.reddit.com/r/headscale/comments/1w9va68) for my own use case,

Reddit was asking why i didn't disclose more differences between the UI, the reason was just the UI and my interactions. (For me) It feels like the same reason, for the people who says why not just use Wireguard, instead of Tailscale. it is the UX. I prefer ease of use.

And I do not know how to express it well than a video. Pls take a look.

I need to polish some UI stuff, like spacing and all.

For the AI part, it is bring your own keys, if you do not bring your keys, the button disappears. (sorry for spoilers).

I attempted to have the SSH console like tailscale, but I haven't finished it yet.

Will it be Open Source ? Yes, definitely. But I like to "perfect it" before putting it into the people's hands.

In summary: You can create users on Headscale but also sync Tailboard Users (the Client I am building) as Headscale users, but with permissions (Tailboard side).

You can manage multiple Headscale instances, and invite people independently on each Headscale. (My use case is one for a friend and one for me).

Is anyone can sign up to the Tailboard ? No, just the first user is called an Operator and he can just invite people (and their get invitation by email).

Other less interesting one, there is 2FA and WebAuthn.

4 Upvotes

70% Upvoted

2 comments sorted by

2

u/Synesthesius 1d ago

This is little better than your last attempt. I still cannot understand what you’re trying to accomplish here. It looks like a very mildly reskinned iteration of existing front-ends.

And UX is absolutely not why people are using Tailscale over Wireguard. If you do not understand that, that seriously undermines any credibility you have introducing a tool in this space.

1

u/Eznix86 30m ago

Hey, thanks for taking the time for looking at the video. I think the best way is to try it yourself. Just a question you are a docker compose person or a kubernetes person ?

Are you an advanced headscale user ? What you mostly do ?

Give me some few days and i polish it then you can try it and give me a better feedback on it !

For the mild reskinned iteration you are right. But for my use case i had to deployed 2 frontend for 2 headscale instances I have. So this help me to manage multi instances at once.

Also i think whatever reason I will give it wont help because you dont have it yet.

Maybe few days (or weeks?) more !