Because it’s like a search box you can explain a problem to and get a bunch of words related to it without having to wade through blogspam, 10 year old Reddit posts, and snippy stackoverflow replies. You don’t have to post on discord and wait a day or two hoping someone will maybe come and help. Sure it is frequently wrong, but it’s often a good first step.

And no I’m not an AI bro at all, I frequently have coworkers dump AI slop in my inbox and ask me to take it seriously and I fucking hate it.

Charybdis, hippo, appa, Momo, pabu

If you want to self-host, I recommend a used business thin client, docker + docker-compose, and Tailscale for access away from home if needed. Don’t forget to dump & back up nightly.

Edit: thin client because it beats a pi in every respect and doesn’t run on an SD card. Tailscale because you don’t have to open ports in your firewall and point a public domain at your house.

Or you could use hosted services, neon.tech and turso both offer really generous free tiers for SQL databases.

Or you could use a notebook and pen. Sometimes simplicity is king.

The trickier part here his connecting your domain to your raspberry pi and allowing the big internet to access it. You have a few options:

• Set up dynamic DNS to direct your domain name to your (presumably dynamic) home IP address. Assign the rpi a static IP address on your home network. Forward ports 80 and 443 to that address. The world knows your home IP address, and you’re dependent on your router for security. No spam or DDOS protection.
• Use a service such as cloudflare tunnel. You’re dependent on cloudflare or whoever, but it’s an easier config, you don’t need to open ports in your firewall, and your home IP address is not public. (I recommend this option.)

Either way, don’t forget to set up HTTPS. If you aren’t dead-set on using nginx, caddyserver does this entirely automatically.

I’ve been using caddyserver for awhile and love it. Config is nicely readable and the defaults are very good.

I have 113k images going back two decades. The screenshot above doesn’t include RAW files, with those included I’m around 2 terabytes of total storage.

• Immich is in fact a photo album, and a damn good one at that.
• Immich keeps google’s grubby paws off my photos. I don’t need or want anyone datamining every precious memory I have in order to modify my behavior to their benefit.
• Immich shares photos between my wife and my phones.
• Immich ensures that if I lose my phone, my photos aren’t lost.
• Immich lets me easily re edit and re-export RAW files without creating duplicates or losing metadata
• Immich lets me conveniently share photos with friends and family without requiring them to have an account anywhere.

Mostly I self-host things when I want data synchronized between multiple devices, or I don’t want to lose it in the event I lose the device it was created on.

Also, like, phone screens are tiny and typing on them is terrible? Why would you want to do everything on your phone?

If encryption is enabled, don’t worry about it. Otherwise ‘dd if=/dev/zero of=definitely-the-bad-drive-do-not-fuck-this-up bs=4M’

Agreed, that should be many tens of pages not one. Also the mobile layout isn’t very good. I think it’s important to remember that normies use their phones for almost everything.

Got a 3 year old kid with another on the way. I just need it to be reliable so the kid can watch Sesame Street and the lights keep working.

I definitely see your point, but the difference is that it’s one thing to learn. Once you know docker, you can deploy and manage anything.

Cons of containers are slightly worse disk and memory consumption.

Pros:

• ease of installation
• declarative, consistent configuration
• security some degree of sandboxing
• dependency management is solved

Stick with the containers

but there is a reason i just explained it to you

Ok but is there room for the idea that your intuitions are incorrect? Plenty of things in the world are counter-intuitive. ‘docker-compose up -d’ works the same whether it’s one container or fifty.

Computer resources are measured in bits and clock cycles, not the number of containers and volumes. It’s entirely possible (even likely) that an all-in-one container will be more resource-heavy than the same services split across multiple containers. Logging from an all-in-one will be a jumbled mess, troubleshooting issues or making changes will be annoying, it’s worse in every way except the length of output from ‘docker ps’

I can see why editing config files is annoying, but why exactly are two services and volumes in a docker-compose file any more difficult to manage than one?

I disagree with pretty much all of this, you are trading maintainability and security for easy setup. Providing a docker-compose file accomplishes the same thing without the sacrifice

• separate volumes for configuration, data, and cache because I might want to put them in different places and use different backup strategies. Config and db on SSD, large data on spinning rust, for example.
• separate container for the database because the official database images are guaranteed to be better maintained than whatever every random project includes in their image
• separate networks because putting your reverse proxy on a different network from your database is just prudent

Seems fine, but you’re sorta hitting two fields at once. Application development (coding) is a different skill set from devops/deployment (docker). I’d stay pretty surface level on docker and the CLI for now and focus on building your app. You’ll know when you need to go off and learn those things.

Yeah, I tried it but that experience isn’t as good as a native app. No swipe gestures, and an extremely basic UI

Miniflux has served me very well for years, combined with a few different apps. Reeder on iOS, I can’t remember what I used on android but there were plenty of options

So there’s a storage protocol called “S3” (I wanna say it stands for simple scalable storage?), first created by Amazon for AWS. Many types of software, including backup programs, have been designed to use it as a storage backend. There are now many S3 compatible providers, last I looked the best value was backblaze B2.

You need a backup program with end-to-end encryption, S3 compatibility, and whatever other features you like. I use restic but it’s CLI only, there’s also borg backup and many others.

If you encrypt locally with a good key, you don’t have to trust the remote storage provider. They just see a bunch of meaningless noise. Just don’t lose the key or your backup is useless.