No judgement here. I think it’s a worthy goal just not one I am particularly interested in at this point. Maybe if the automation was a bit easier and the mobile device management was easier I might join you.
My experience is it’s really a lot of work and with the prevalence of letsencrypt, there is not a lot of automated setups for this use case (at least that I have been able to find). It is kind of a pain in the ass to run your own CA, especially if you plan to not use wildcard and to rotate certs often. If you use tailscale, they offer https certs with a subdomain given to you:
[server-name].[tailnet-name].ts.net
That’s honestly what I’m moving towards.
Another vote for wiki.js. It has tons of authentication options and integrations. The mobile web interface is a tad clunky but usable.
I don’t know what DAE means but yes it’s very annoying. It’s almost like trying to prohibit information limits legitimate use.
I see. GP said the same. Thanks for sharing!
True enough for VNC but we’re specifically talking about RDP, which is supported by Linux Mint.
Yea that looks pretty amazing. Thanks for sharing!
Single node k3s is possible and can do what you’re asking but has some overhead (hence your acknowledgment of overkill). One thing i think it gets right and would help here is the reverse proxy service. It’s essentially a single entity with configuration of all of your endpoints in it. It’s managed programmatically so additions or changes are not needed to he done by hand. It sounds like you need a reverse proxy to terminate the TLS then ingress objects defined to route to individual containers/pods. If you try for multiple reverse proxies you will have a bad time managing all of that overhead. I strongly recommend going for a single reverse proxy setup unless you can automate the multiple proxies setup.
And here I am running a bare metal k3s cluster fully managed by custom ansible playbooks with my templatized custom manifests. I definitely learned a lot going that way. This project looks like it has just about everything covered except high availability or redundancy, but maybe I missed it in the readme. Good work but definitely not for me.
Sounds like a good option then!
Yep that’s why I use KDE. It has nVidia support for Wayland.
I have heard they are either working on a similar thing for Wayland or already solved it.
This looks promising, but I have not used it before.
waypipe is a proxy for Wayland[0] clients. It forwards Wayland messages and serializes changes to shared memory buffers over a single socket. This makes application forwarding similar to ssh -X [1] feasible.
[0] https://wayland.freedesktop.org/ [1] https://wiki.archlinux.org/title/OpenSSH#X11_forwarding
Check out Termux. It lets you install nearly any linux software on your Android device. Probably a good place to start to get your toes wet.
I’ve used X11 over SSH before and it works great for some use cases, however it does not work with Wayland, so if their system supports it now, there’s no guarantee it will work after a major system update.
In my experience, RDP locks the screen for anyone at the physical machine. It sounds like OP is wanting a simultaneous screen sharing.
I think VNC protocol over your tailscale tailnet would work well. It shares the screen without locking out the in-person user.
You could also try Steam remote play, it shares the desktop like what you’re asking, but would require a bit if setup (custom “game” added which would expose the entire desktop for e.g.), and wouldn’t be useful without someone relaunching it after a reboot, so wouldn’t be very useful for remote management without grandma available at the machine.
I would stay away from X11 over SSH because X11is deprecated in favor of Wayland and will stop working as you upgrade the OS (if it even works now).
RustDesk looks promising but it sounds like it may lock the screen for the in-person user, but I’ve never used it so can’t say for sure.
That would be pretty dope. If you end up writing it up don’t forget about me 😁
Do you have a link to a tutorial on this? I’ve been thinking about adding my amd64 server with an nVidia GPU to my Raspberry Pi K3s cluster.
I’m out of the loop. Why did github “block” Organic Maps?