You can keep your work apps separate from this. At least that’s what I would do
You can keep your work apps separate from this. At least that’s what I would do
Yes! I mentioned it in the article and they have a self-hosting guide which to be honest, is not about hosting Beeper at all, but it’s just a vars.yml template to host some matrix bridges. The template I provide in the article is based off of that.
You can’t know what they do with your data, so I decided to self-host this alternative.
Was born too late to enjoy that experience 😔
You can totally skip federation and you won’t be able to use matrix users or join public rooms, but I guess it’s something that some people don’t need.
I wish I could escape it because of privacy concerns, but I’m finding it too convenient to let it go. Would appreciate it if someone could convince me out of it
You could implement plenty of ways to access it, Cloudflare is just one of them. I made this guide to achieve the goal of self-hosting matrix bridges for people who are already familiar with Cloudflare and have a domain behind it, but it’s not something that is mandatory to have for a similar setup.
Cloudflare Tunnels are useful to connect to the server without exposing your ssh port to the internet, and Cloudflare Workers to add .well-known files for federation and Sliding Sync proxy if you don’t have a way to serve those files easily.
Lmao. Truly broken right now.
Beeper is great but you have no idea what they’re doing with your data.
Thought the same, that’s why I decided to learn how to host it locally and wanted to share the knowledge.
an assembled docker rather than ansible playbook, that is going to be the one that takes off.
Definitely. Right now it causes quite a few headaches and Docker is also what’s probably most known by selfhosters.
Only locally, so that your local computer can access your server locally. Then the Cloudflare proxy will allow you to connect to it from the internet securely through a two-factor authentication or any other access type you choose, without opening any port to the internet. It’s all explained in this section.
You can also implement passwordless authentication but that would probably be too extra.
The default layout is what feels comfortable to me and I chose starfish because I used to use starship with zsh, so I went with something I was familiar with and didn’t think too much about it.
I didn’t even know about tide until now but after a quick look I can’t find any groundbreaking differences in the layouts compared to starfish.
It really is just Arch with a different init system. There are no noticeable major differences. The faster bootup times are probably negligible.
Of course I like the idea of minimalism and the unix philosophy, but the reason I chose Artix isn’t so philosophic. I was already using Arch on my laptop and wanted to install it on my desktop, but I enjoy trying to do harder things and learning in the process, so I ended up learning how to use a different init system… and I also did it because I liked the Artix logo better lol.
I’m very happy with both Artix and Arch and while I wish systemd wasn’t almost a monopoly, at the end of the day everyone is free to use what they want as long as it doesn’t hurt the linux ecosystem for others.
I guess not. I’m not that experienced with ddns but I think there’s no way to have subdomains?