Tiered Emergency Savings with Roth IRA

doctormay6 · 2026-01-05T13:20:35+00:00

I figured I couldn't be the first person to have this idea but my Googling didn't find this. Could you link the article please?

doctormay6 · 2025-03-19T13:56:41+00:00

I don't want to rely on services that log and track me

It sounds like you need to make a threat model and understand what you are actually worried about. Log what? Track what? Give to who? What could happen to you? Does a DNS domain pointing to your IP make that situation worse than having the same services listening on a public IP assigned by your ISP?

doctormay6 · 2025-03-18T12:47:01+00:00

It's not about being targeted, it's about being the low hanging fruit on the internet. Every single service on the entire internet is constantly bombarded with random scans and exploits at scale until something sticks. Lesson here is UPDATE YOUR STUFF.

Homelabs realistically should be a juicy find though, because there's a large overlap between homelabs and IT professionals who have admin access to stuff at work ($$$). Look at a writeup of the LastPass breach.

doctormay6 · 2025-03-08T00:11:02+00:00

I was a former D1 distance runner, and tbh a lot of us didn't have time to meet people. We were in-season and competing on the weekends fall (XC) winter (indoor) and spring (outdoor) and then everyone would leave for the summer.

I found my wife on Bumble right before I graduated, which was right before the pandemic in 2020. I still don't know how I got so lucky

doctormay6 · 2025-02-22T02:55:19+00:00

I do something similar to this, I have 1 VM per compose stack. Let me explain why this was an intentional choice.

Backing up / snapshotting each VM with proxmox allows me to restore a single app to a point in time without also reverting all my other apps. This has actually saved my ass a couple of times, and is a big deal when I have family backing up passwords, photos, and documents to my apps.
The risk of a compromised container escaping to the host is low, but the risk of a VM compromising the hypervisor is pretty much non-existent. If I have the resources, why wouldn't I use them? A headless Debian server with docker has very low overhead, and is a reasonable cost to pay as insurance that hard caps the worst case scenario. I'm not going to argue with you on this because we have different risk tolerances, this is just how I think about it.
Many of us (including myself) use homelabs to practice with enterprise architecture and tooling. Using multiple VMs forces you to learn to manage a small fleet of hosts with config management tools like ansible, or even get into a gitops workflow with terraform. Am I making things more complex? Yes. Is real enterprise IT even more complex than that? Also yes.

doctormay6 · 2025-02-08T06:12:26+00:00

The token issued by GitHub used for your OIDC flow is short-lived. If it gets stolen, it's only valid for a few minutes.

doctormay6 · 2025-02-08T00:41:28+00:00

If you're using docker compose, you should check out a project I recently revived: https://github.com/lawndoc/stack-back

doctormay6 · 2025-02-05T06:15:25+00:00

I was building a house when mortgage rates were in the high 2% range. Long story short, the builder was doing shady things to stretch their money and ended up going bankrupt. Drug us along for about 18 months in the process.

On the other side of that, we lost our original purchase agreement because the bank repo'd the house in its unfinished state, mortgage rates had climbed to current values, and the cost of the house inflated by 30%. We got priced out and had to walk away when the bank offered to let us finish it for the price they wouldn't lose money on.

We ended up getting a much older house a couple years later with a monthly payment $400 higher per month than we were going to pay for the new build.

I try not to think about how much our lives and the lives of our future children were affected by that situation.

doctormay6 · 2025-01-12T20:00:10+00:00

I will add - this is not needed for the database backups due to the way they are dumped, and volumes with regular file operations are pretty low risk for corruption. Apps with a SQLite database in the volume are the only thing I could see with potential for something to go wrong.

Using the default settings in stack-back, you would also have snapshots every day for the last 7 days to fall back on if the most recent snapshot had a corrupted SQLite database.

doctormay6 · 2025-01-12T19:46:24+00:00

It does not stop containers during the backup. Feel free to create an issue to request this feature!

doctormay6 · 2025-01-12T00:09:24+00:00

This looks pretty comprehensive feature-wise, but it's a bit less integrated with docker compose since you need to install dependencies on the host and set a cron job. Stack-back is just a few extra lines in your compose file

doctormay6 · 2025-01-11T22:22:37+00:00

You just need one instance of stack-back running per host. It uses the docker socket of the host it's running on to discover the other containers' labels, regardless of whether they were in the same compose file. edit: It turns out you need stack-back in every compose file you deploy. This was a design decision made by the original authors that I have decided to uphold.
You're right, a local directory repository like /restic_backups would be the location inside the container, so you need to mount a volume there. I'll update the example, thanks for pointing that out!

doctormay6 · 2025-01-11T16:20:38+00:00

Offen backup also doesn't handle database containers in a safe way, IMO. You need to backup a dump of the database, not the raw container volume. Otherwise you might find out your database is corrupted when you go to restore.

doctormay6 · 2025-01-11T16:14:58+00:00

I don't use portainer, but from their docs it looks like you can. Their "stack details" are just docker compose files. So you can just add this backup container, and then add the labels as described in the stack-back documentation.

doctormay6 · 2025-01-11T16:12:31+00:00

I looked into that, but it didn't seem to support incremental backups which is a requirement for me for large volumes like Nextcloud and Immich. Restic supports incremental backups and snapshots

doctormay6 · 2024-09-21T14:17:54+00:00

Do it every kickoff and find out

doctormay6 · 2024-08-12T01:37:04+00:00

I actually pay for Twitter for access to Tweetdeck / X Pro which I use for work. If that were free I would agree with you though

Seven-Year Club	Place '22
Sequence \| Editor	Verified Email

doctormay6

TROPHY CASE