I can't say that I am but I have a pretty good guess as to what it is. My thinking is I should have this password backed up somewhere in case I get hit by a bus. That in the even of my untimely demise some one can keep this place going.
Right! When you get hit by a bus, where does that put the project?
Then again, with whom can you safely leave access?
Fucked if I'm even offering any advice on this one. Nope. You're on your own. I just want you to think about it. It's known as the bus problem.
The site is dead without you. You can Git the prod and beta. You can encrypt DB backups well - and put them off-site. Yeah, you're going to want a recovery plan - you can do that well enough. You know the 3-2-1 backup rule, right?
I'm sorry but I am unqualified to help you with these problems. They are your problems, at some point. (I've got some experience here.) I'm way out of date and I'm not really willing to accept the social credit liability for being the person to suggest a particular path on this one.
It does mean, eventually, finding a system (or person) you can trust. I will say that 'dead man switches' are a good start for looking, assuming you want to keep it to yourself until you stop performing an action for a set length of time. "If I haven't logged in and it has been 10 days, decrypt this and send it to this address. Tell them I'm dead."
Again, that's not advice - it's just an observation. I'm not your consultant or your lawyer! ;-)
(post is archived)