206 karma · joined July 9, 2012
My book: https://selfhostbook.com
In case anyone still trusts & uses keybase:
[ my public key: https://keybase.io/meonkeys; my proof: https://keybase.io/meonkeys/sigs/fEwfH1Pzs5TMp9n4wDRXYjpm7eNLdfKjriDGlPWdgbM ]
> It is 2024, and I say it is time we revisited some of the fundamental joys of setting up our own systems.
Self-hosting really is joyful. It's that combination of learning, challenge, and utility.
+1 to Actual Budget
+1 to Changedetection.io
-1 for not mentioning threat modeling / security. The author uses HTTPS but leaves their websites open to the public internet. First-timers should host LAN-only or lock their stuff way down. I guess that's tricky with shared hosting without some kind of IP restriction or tunneling, though. No idea if uberspace offers something like that.
For folks getting past the initial stages of self-hosting, I'd really recommend something like Docker to run more and more different apps side by side. Bundled dependencies FTW. Shameless plug for my book, which covers the Docker method: https://selfhostbook.com
Also working on my homelab. Recently got DocuSeal, changedetection.io, and Actual Budget running.
You can test this in Bash: userA does cat>/tmp/newfile (assuming a chmod or relaxed umask so /tmp/newfile is created with permissions 0664), userA types in lines of text every few seconds, userB does tail -f /tmp/newfile and watches lines appear, then userA does chmod 600 /tmp/newfile, but userB can continue to tail -f /tmp/newfile and watch lines appear.
containerA: all outbound traffic allowed
containerB: no outbound traffic allowed, except to reply to a client
containerC: may only reach out to updates.example.com
Is this just per-container iptables? I could wedge iptables into existing images but it seems like a lot of work.
Or maybe something with iptables on the host?
would have been more accurate, less clickbait.
Details: https://2024.fossy.us/schedule/presentation/219/
If you bring a book, I'll sign it.
If you're stuck getting started with your homelab, see https://selfhostbook.com/videos/ . Any suggestions on other videos I might create? Should I stick with short and sweet, or do something longer? How much longer?
'Is "source available" that bad?' discussion from 5 months ago: https://news.ycombinator.com/item?id=38790767
Also, why is your username green?
I chose Nextcloud and Jellyfin when I started in 2020. Before then I was running a few random things like Syncthing and Samba mostly just for myself. In 2020 I decided to try and apply a more thoughtful, disciplined process. Good security, reliable backups, useful for my whole family, etc.
Shameless self-promotion: https://selfhostbook.com . My book covers justification for self-hosting, fundamental skills, and homelab (or perhaps "homeprod") setup with Ubuntu, Ansible, Docker, and Traefik.
I wrote it for folks with some light sysadmin/programming skills. It's a good general starting starting point for self-hosting.
I'm writing a small book. I shared my experiences with Pandoc and Asciidoctor in case it helps you or anyone:
https://adammonsen.com/post/2122/
Your use case may differ from mine (I didn't see you mention printing), but my anecdote above might help suss out tooling differences between Pandoc and Asciidoctor.
Here's an example printable book generator using Asciidoctor PDF:
However, often I'll open up a GUI I haven't used in a while and feel like I'm just as lost as I am with a command-line tool I haven't used in a while. I rely on notes I've taken and try to stick with stable software.
Can you think of any command-line tool you might not use for 6 or 12mo but when you crack it open after a long time it is intuitive how to do what you need to?
I hypothesize muscle memory is required for efficiency at the command line.
magnet:?xt=urn:btih:6285b37e9f968526f953c714993ff2f76c6a4d29&dn=dsl-2024.alpha.iso&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A6969
Hopefully that magnet URI works. This is the first time I've tried to create one. Hopefully the tracker works too, I seem to be getting intermittent "Connection failed" errors from it. If anyone already knows how to properly serve torrents, please school me. :-)
Size is 698126336 bytes. Checksum is at https://damnsmalllinux.org/download/dsl-2024.alpha.iso.md5.t... (looks like they only have an MD5 checksum posted).
Signal is open source. It's a fair argument that they make it difficult to use servers other than theirs, and we can't be sure exactly what they run server-side, but their code is possible to fork and all that. Their licensing is clear. Even the choice of AGPL is significant here: they must provide the source for exactly what they run on their server.
Network access is orthogonal to source availability/openness. Closing source as a means to limit access is security through obscurity. Not to say that it wouldn't work, but we certainly wouldn't expect the Signal Foundation to take this approach.
The most significant measure Signal uses to manage access to their network has to do with the phone number requirement. That's an intentional choice on their part (arguably controversial, but I don't have an opinion about it).
I've never received a spam message from another Signal user... is this common for you (or anyone)? I think in all the years I've used Signal I've only received less than 5 spammy "message requests" that are quite obvious/easy to decline because I don't already have their phone number in my contacts. I've always had to first ask someone "hey, can we use Signal?" so I'm already expecting legitimate message requests when they arrive.
Check out SkyMap!
Any company can sell microcloud, but it must remain AGPL.
This license choice is a defense against microcloud being assimilated into proprietary products.
(Now I'll guess at the motivation of your original question. Lemme know if I missed your point...) The AGPL doesn't apply to any containers or VMs running in a microcloud any more than Ubuntu's licensing applies to programs you run on Ubuntu.
I've heard several mentions of it being used in place of services like Dropbox, OneDrive, Drive, Box. For the features above, I agree.
What Syncthing is missing is usability for folks that use the proprietary services because they are easy to set up and maintain and share files from. For that I recommend Nextcloud. It is centralized, so perhaps a different use case. But certainly a more complete replacement if you (or people you support) are used to Dropbox.
Also, just curious, but why is this on hacker news today? Was there a new announcement or release for Syncthing?
I looked through the docs and didn't find anything about integrating/importing/exporting. I found lots of open feature requests for integrations.
I've carefully curated contacts and meetings in my Nextcloud instance, so of course I'd like to leverage all that work. I added my thumbs-up to https://github.com/monicahq/monica/issues/1444