yunohost VS awesome-tunneling

Pull that old laptop from the closet, the one with the broken screen and keyboard which made you so sad to put it to pasture since it did have plenty of memory and CPU to keep up. Install Debian on the thing followed by Proxmox Virtual Environment (PVE) [1]. Since you have 16GB of RAM in that laptop (or 8 but 16 is nicer) you should be able to run a number of containers [2].

Here's an idea, more or less based on a number of servers I configured for friends and family, based on 8GB Raspberry Pi 4 hardware with 2/4TB USB SSD. Your laptop will offer better performance.

- Create 4 or 5 containers and name them 'auth', 'serve´, 'base', 'backup' and 'mail' (if you want to run your own mail that is, otherwise skip that one). Their functions are:

> auth runs LDAP, Kerberos (if you want that), a central letsencrypt instance which takes care of all your certificate needs and anything else related to authentication and authorisation

> base runs databases, that means Postgresql, Mysql/Mariadb, Redis, RabbitMQ and whatnot - all depending on what you need.

> serve runs services, that means nginx or another web server which is used as a reverse proxy for the other web-related things you want to run: 'cloud' services like Nextcloud with everything that comes with it (e.g. Collaboraoffice or Onlyoffice to replace whatever web-based office things you currently use), communications services like XMPP, application-specific proxies like Invidious/Nitter/Libreddit, media services like Peertube/Airsonic/Ampache, a Wiki like Bookstack, search services like SearxNG, etc. - the size of your server is the limit.

> backup runs Proxmox Backup Server and is used to backup everything to some external drive and to some outside repository.

> mail runs mail services, only if you want to run those. I always say 'do it' but many people have an irrational fear of running their own mail services. That fear is not grounded in truth, running mail is not hard and offers many advantages over hosted solutions.

While it is possible to separate all the mentioned services out into their own containers I think this adds needless complexity for little to no gain. Separating out database services makes sense since those can end up quite taxing and as such might well be moved to their own hardware in some (possibly not too distant) future. Separating out authentication services makes sense since that lowers the attack surface compared to running them together with externally available services. The same goes for mail services which is why I put those in their own container.

Once you've got this up and running you can create a few more containers to play around with. If you just want to try out services something like Yunohost [3] or Caprover [4] can come in handy but I do not see these as viable alternatives to installing and running services which you intend to keep around for a long time.

Of course you can do most of this on a VPS as well but I prefer to keep thing in-house - the fewer dependencies, the better.

[1] https://proxmox.com/en/

[2] containers perform better and take less memory than VMs but if VMs are your thing that is possible as well

[3] https://yunohost.org

[4] https://caprover.com/

Yunohost is one of those mature projects, that's fully open source.

YunoHost, although not Docker-based, is still nice and quite mature.

If you want something like that, then CasaOS is pretty great and i can recommend it, especially for a beginner. There is also Cosmos and Tipi. Yunuhost too but a bit different approach. Oh and Umbrel is a thing...

However you quickly reach the limits of what Umbrel can do, its very basic in its abilities. Of course it depends all on what you (or anyone else) wants to do with it. There is also CasaOS which is very similar to Umbrel but last i compared, Casa offered a bit more features like for example adding your own docker projects easily. There is also Tipi which i must admit i havent taken a closer look at yet. And there is Yunohost which i guess aims at a similar audience but achieves these things differently, still worth mentioning tho.

This looks exciting and definitely something to look out for as an option fkr self-hosting.

Similiar and a little bit more mature is also YunoHost, https://yunohost.org/, or for professional environments, UCS https://www.univention.com/.

I use https://yunohost.org on my Pi, mostly for monitoring other stuff but you can get Nextcloud running just fine with it!

https://github.com/anderspitman/awesome-tunneling

awesome-tunneling lists a number of ngrok alternatives: https://github.com/anderspitman/awesome-tunneling

- https://news.ycombinator.com/item?id=39754786

- FWIU headscale works with the tailscale client and supports MagicDNS

There are a whole bunch of alternatives too - https://github.com/anderspitman/awesome-tunneling. I will advocate for zrok.io as I work on its parent project, OpenZiti. zrok is open source and has a free SaaS as well as more built in security.

https://github.com/anderspitman/awesome-tunneling. Seems similar to zrok.io, ngrok, cloudflare tunnels, tailscale funnels and zrok although you're using http/3 explicitly.

Personally I work on two similar projects you might want to check out: zrok and OpenZiti. Similar projects, but zrok is closest to what you did here.

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

I haven't tried vscode forwarding. What features does it have that are missing from most of the options on the list[0]?

If you want a nice GUI for remote managing maybe check out one of my tools, boringproxy

[0]: https://github.com/anderspitman/awesome-tunneling

I maintain this list:

https://github.com/anderspitman/awesome-tunneling

Your use case sounds interesting and there may be a tool out there that will do it, but I can't quite wrap my head around your description of how everything is connected and what runs where with your current setup.

I agree with sibling that my main question is what prevents you from using SSHFS or similar?

I'm starting to try to get into Cloudflare tunnel, Tailscale funnel and other alternatives. What I need is my services to be accessible without any installation client-side, and I'm unsure what services provide this. I also looked at solutions like BoringProxy, TunnelMole from this page : https://github.com/anderspitman/awesome-tunneling My goal is to have my current domain rented at OVH pointing to my server to make it as much like before as possible.

Here's a list of options to get around CGNAT: https://github.com/anderspitman/awesome-tunneling

We have a section for overlay networks on the tunneling list[0] I maintain. This is a very interesting space with some excellent software.

I certainly have my gripes about the closed nature of Slack itself, in particular using a closed protocol when the model is clearly "federated" between multiple servers internally. That said, the contribution of something on the scale and quality of Nebula back to the open source community is hard to argue with.

[0]: https://github.com/anderspitman/awesome-tunneling#overlay-ne...