XMPP gang rise up! There are dozens of us!
I’m all about adding to the proverbial arsenal. 🤘
You’re absolutely right! I’d point you back to my notion of cost-benefit analysis. Anything more than the 20min that I’ve spent on analysis so far isn’t worth my time. If the VM falls over permanently, that was a risk and my time savings has already been worth that risk. If I were looking at something like a production file server or domain controller, sure – I’d spend more time on it. Likely though, I’d just have engineered it better in the first place. Not every problem warrants a high precision solution. 🙂
Hey everybody. I found this interesting. It’s likely not a game changer for anyone, but “hardware” watchdogs in Proxmox was a new one for me, and was a cheap and easy, hacky fix to deal with a low value VM that was periodically hanging. This is a nice tool to add to the belt, hope you all enjoy!
I’d be interested in seeing that, or at least knowing which ejabberd container you chose and why.
Hey thanks so much for the engagement. I was trying to run it on a VPS that cost $35/year. 2GiB of RAM wasn’t quite enough to make it work for me, granted that was with the webserver and ancillary supporting services.
I’ll find an opportunity to test it out though, as rybbit looks great. I appreciate the mention on the other FOSS products, that’s a good look for you. I have plenty of experience with umami already. Cheers!
Glad to see you post this here. I’ve been experimenting with selfhosted analytics for a while now and have attempted your project here a couple times. The thing that kills me is the Clickhouse requirement. It makes it impossible to host on a lightweight VPS. Like why should my analytics platform require so much more compute than my simple static site? Am I missing something?
Okay this is excellent content, thank you!
I went through and fiddled with some more stuff to try and get this working to no avail. However, it inspired me to take apart netboot.xyz a bit more, and I was able to grab an efi and get next boot to load the efi file. It took me too long to realize you need the console tty arguments as part of the boot cmdline to get it working interactively, but after I got there I got it netbooted. Sadly though, it almost immediately runs into an OOM condition and thus isn’t practical on a free tier x86 asset. It would probably work on an aarch64 node, but I already have my allotted arm node spun up and working so I don’t have a free one to practice with.
Solid write-up though, thank you for putting that together!
The “gotcha” with Oracle free tier is that you can’t install from arbitrary media, so the typical netboot.xyz or any iPXE workflow is out. No console access, no pre-bootloader access, nothing.
I’ve been fiddling with kexec, but it doesn’t seem like a supported method of loading the lkrn file from netboot…
This is super interesting to me, so by all means, if you have the kung-fu to show how this works I would happily read through that!
Interesting. I’ve had two instances running for over 2 years and haven’t noticed that. It might be that I just don’t notice it though. I’m not scrutinizing it much.
I am not well versed with kexec but I always understood it to be a kernel reboot without power cycling the “metal.” Please enlighten us with an example! I don’t see how you’d replace the entire userspace (and possibly filesystem) with simply kexec.
Certainly! As others have said, don’t hang anything worth value on it without an out of band backup strategy, they’re famous for unscrupulously deleting things with no warning. Oracle is a miserable company.
Free is free though!
Decided to write up a quick post on a hacky workaround I came up with for custom distros Oracle free tier and thought I’d share. Don’t rely on Oracle, but definitely do leverage as much of their free compute as you can for non-critical workloads!
I would recommend giscus over discus, but yes, certainly a valid approach!
I have been pleased with giscus on my blog (http://roguesecurity.dev/ ) Its powered via github discussions.
Agreed, prosody is great! I’ve been doing some experimenting with ejabberd and it seems more enterprise-ready, but I haven’t found anything that is discernable as far as feature advantages.
Sounds like a great opportunity to breath some life into it! If you really have the itch for IRC, there’s a slidge bridge to connect IRC to XMPP!
Agreed! Runtime environment management is so much nicer with modern containerization. You or ally can’t overstate how much better it is to have app stack state be entirely divorced from OS state. I’m very pleased they’re back on the bandwagon as well.
Stand up a server and come join our MUC!
UPDATE: For anyone who comes back to this, or any new readers – I have added a MUC (chat room) on my XMPP server for discussion of any tech-related things, akin to the subject-matter of this blog. Hope to see you there!
I’ll add to the pile: https://roguesecurity.dev/blog/xmpp
Prosody gets my vote as well for extensibility over snikket and still being relatively easy.
My guide caters more towards OCI runtimes if you’re into that. I like podman and quadlets, but you could do docker as well.
XMPP for the win!