It breaks large uploads into smaller chunks. If you’re hosting behind a reverse proxy and using cloudflare, there’s I think a 100MB upload limit. Can pose a problem for importing some videos.

Chunking and the ability to rotate an image. I guess those features aren’t sexy.

Strangely, I deleted them and reuploaded. Now they display fine. Might need to play with this a bit more.

This is a criminally underrated tip. Liquor boxes are seriously sturdy, and the size keeps you from overpacking them.

Also, I started with a pi, added a synology (a NAS is a game changer), and then moved almost all services off the synology to a Beelink S12 pro. Recently upgraded the S12 to 32GB of memory, and I have a 2tb ssd upgrade I have to do soon. All of this is over the past 2-years.

Two sites that really helped me get the basics of docker compose were Marius hosting and Dr Frankenstein’s docker guides. Both are focused more on synology, but the docker stuff works anywhere.

ETA: linuxserver.io is pretty handy, too.

Archived link

Once I pick one, I’ll probably set up a regular donation. I should also probably drop some $$ towards the other projects since I’ll probably keep an eye on them.

Agreed, iCloud Photos is pretty nice. I almost gave in when they added the AI features and text recognition. Unfortunately, my library started having some stability issues. Was finally, hopefully, able to resolve those yesterday.

Still, one of the nice things about most of the photo hosting apps is they store photo metadata properly - in sidecar files. If they go tits up, and you maintained your metadata you really haven’t lost much. If the Photos DB gets corrupted, you’re going to lose data that would otherwise have been stored in those sidecar files. IMO this is a glaring omission on Apple’s part. I get that having all that info in a database makes larger libraries perform better, but por que no los dos?

Ah, i didn’t see ente’s self hosted version. The instructions look kind of strange. Will need to look into it more.

I’ve looked at ente, but honestly don’t see the point unless I want to stop paying for iCloud storage (which for the time being I don’t).

I’ve seen some examples where Caddy can do some cool stuff (I think the example I saw recently was defining routes that can call an arbitrary program with the HTTP request details).

I guess this is what I was getting at. From what I can tell, at their core, both do pretty much what Swag is already doing for me. Was mainly curious about additional functionality I hadn’t thought of. Most of what I’ve done so far is stuff I hadn’t thought of until I saw it mentioned here, reddit, or in the linuxserver list.

Damn! I missed that one. Working now. Thanks!

Won’t connect on either port using http or https.

This is really helpful. I’ll look into that. Thanks!

I can upload files outside of the docroot, but if they stay there for too long, I get a nasty email from Dreamhost reminding me that this is for web space and not offsite storage (something they also sell). I haven’t tried uploading something inside the docroot and just setting permissions to 400 or something!

I haven’t played w/ memory limits, but when I tried messing w/ buld download of raw TIF files, it ran out of memory pretty quick. I may look into what I can to about the limits, though.

Same. I have a mediawiki install on the shared hosting still, but I haven’t updated it in forever. For the $10.99/month I’m paying for shared hosting, I could save a little and do a more powerful VPS to host similiar stuff… Of just keep doing what I’m doing w/ my S12 pro & Synology. Might look at some kind of failover down the road.

Fair point. Currently, everything that requires off-site backup is sent to my father’s Synology using hyperbackup. So off-site is sorta self-hosted already. Was thinking in terms of a second fallback option.

At the ends of the day, it’s about what you’re comfortable working on. My daily driver is a MacBook Pro. I have a BeeLink S12 Pro that runs most of my self hosted stuff, and a Synology that runs a couple things. I also have an HP Z440 as a test bed box (powered off unless I’m working on something). I’m comfortable working with Linux and power draw was important for me in setting up my always-on server (my power bill is already high).

The only minor concern I would have with a mini is you’re limiting your support base. This isn’t to say there’s no support, there’s just less. Most self hosted are using something like a unraid, a beelink, or an old micro Dell/HP/Lenovo. Because of that, there’s a ton of stuff out there about getting various services running on these setups. The M-based mini environment is going to be a little more unique.