Ah, I wonder if it’s something with the Wasabi S3 hosting. I’ll check into it.

It’s literally all I wanted to do when I saw the .bond TLD came up for registration.

You can take stronk.bond from my cold dead hands.

I would consider using your Synology for what it’s good at - storage.

My homelab has a Synology DS1618 and servers are Lenovo M90q systems. They have enough compute to get the job done, and use the Synology NFS mount for storage.

Yeah, for the integrated CI/CD, give GitLab a shot - it saves on spinning up a Jenkins or ConcourseCI server.

CI/CD can be useful for triggering automation after merge requests are approved, building infrastructure from code, etc.

I’ll come out with an anti-recommendation: Don’t do GitLab.

They used to be quite good, but lately (as in the past two years or so) they’ve been putting things behind a licensing paywall.

Now if your company wants to pay for GitLab, then maybe consider it? But I’d probably look at some of the other options people have mentioned in this thread.

Oh snap, are you the developer of Viewtube? If so, first off - great job. I do the infrastructure side of IT for my day job but aside from some basic go, I couldn’t code something like this to save my life.

I wish I had the chops to contribute to the project.

Heck, you could do a pre-stage play where you delegate to localhost an ansible.builtin.get_url to download the compose file before doing the rest.

It’s anonymous bulk text posting - great for sharing logs, but don’t discount the more grey side of the internet. If you browse recent public posts there’s often some fun things like scam links, credentials, etc.

It’s definitely fallen out of favor for password dumps though.

I didn’t intend to use it on the chest freezer - it was mostly for the modem, but since I had spare battery capacity and outlets I thought what the heck.

The power load is practically nothing until it cycles, and even then it’s fairly efficient - my current runtime is estimated to be about 18 hours, more than enough to come up with an alternative if we lose power in a storm.

While I appreciate the sentiment, most traditional VMs do not like to have their power killed (especially non-journaling file systems).

Even crash consistent applications can be impacted if the underlying host fs is affected by power loss.

I do think that backup are a valid suggestion here, provided that the backup is an interrupted by a power surge or loss.

I agree that 99.999% uptime is a pipedream for most home labs, but I personally think a UPS is worth it, if only to give yourself the option to gracefully shut down systems in the event of a power outage.

Eventually, I’ll get a working script that checks the battery backup for mains power loss and handle the graceful shutdown for me, but right now that extra 10-15 minutes of battery backup is enough for a manual effort.

This is why I have about five of these bad boys: CyberPower CP1500PFCLCD.

One is in my utility room for my cable modem and our chest freezer, three back up my homelab and wifi AP, and one is for my office.

They’ve been bulletproof through storms, and when we’ve lost power, but not Internet I can’t keep on working.

The big thing to look for is number of battery+surge outlets vs just surge outlets. Typically they top out at 1500VA - the more overhead for what you’re powering, the longer you can go without mains power.

A screen/display is helpful for at-a-glance information like expected runtime, current output, etc.

This is the right answer. I have dockerized Calibre and Calibre-Web for initial intake, then use Calibre-Web’s OPDS feed with my Moon+ Android app for reading on my tablet/phone.

Calibre handles type conversions, metadata sync, and file organization.

Calibre-Web works well for browser reading on my PC.

It really depends on what you want to run. I have a clusterHat (four Pi Zeros on a Pi4) that runs a Hashicorp Vault cluster with minimal usage.

The big thing about self hosting is what happens if you (or other people) start to depend on your service - what do you do about hardware failures? Maintenance windows for patching?

To start off, a Pi is fine, but you’ll probably start maxing out your compute and memory (again, depending on workload).

Dropbox keeps hounding me to upgrade to a paid level - back when they were incentivizing sign-ups with free storage for the inviter and invitee, I spin up several throwaway accounts and VMs to give myself bonus storage (I’m just over 21GB).

It’s plenty for some critical secondary backups of wedding photos, docs, and an encrypted volume or two - but I absolutely cannot see myself paying for even their cheapest tier.

Psh… That’s amateur, I just keep incrementing the number at the end ‘password1’, ‘password2’, etc. Gotta fool the password reuse counter!

After about a year of using Keycloak for some #dayjob side projects, I literally just stood it up in my homelab.

It does have a learning curve, but it supports OIDC and SAML - those two should get most internal services covered.

Back end can federate with AD or LDAP - for the real stinkers who refuse to support SSO. (Looking at you Netbox)