: What are the steps to ensure that if you die, your hosting & domain will live on? Assuming you are micro independent software vendor (MISV) or one man web shop (OMWS), how do you reduce your

@Shakeerah822

Here are a number of simple steps which will make it easy for someone to take over after you are gone:


Give clients plenty of time to figure it out. Don't register domains for only one year at a time, go longer. Domains are fairly cheap and there is little reason to choose shorter-term registration.
For client websites, record all necessary details that another web developer or website administrator would need to know to take over the project. Give that to the client and tell them what it is and explain the limitations (for example, you wouldn't include SSH keys or logins which would grant access to machines with multiple clients' websites).
Choose the domain registrar and host carefully. Some, like Gandi.net, allow you to delegate permissions to renew hosting, configure DNS, and other tasks to a separate account. That means you can have one master account that oversees every client website, and individual accounts per client that they could hand over to the next developer to resume control.
Prepaid credits - this relates to the first point and is optional. It does increase the time people have to make a decision if there is a financial buffer in place.
Choose a CMS than can auto-update, and enable auto-updating (for at least security patches) on the host machine(s). There is some peril here as updates can break things. So can not updating, so weigh your options.
Communicate with the clients. This is the biggest, most important step. I tell people upfront 'If I get hit by a bus what do you do about your website?' I usually get a nervous laugh or a funny look, then I hand them the printed details from steps 2 & 3 and explain that they should find another developer and give them the papers, they'll know what to do from there.

Vote Up Vote Down

@Rivera981

The simplest thing to do is employ a dead man's switch that sends vital information to someone that you trust, and have established an agreement with to carry on or conclude a select few of your affairs or ventures if something should render you unable to continue with them.

In the simplest case, you have something set up to send an email to several people containing (or, telling them where to find):


Financial information (a statement of things as they are, financially)
Account / server credentials
Encryption keys and instructions on what to do with them
Contact information for those working with you, instructions on who needs to get what
Source code, or access to it, if applicable
Where to find credit card / payment methods to continue paying bills - or cash you've stashed for this purpose.


... and this triggers if you don't do something in a specified amount of time. For a while, when I was working mostly freelance, I had something like this set up to trigger if I didn't commit to a repository at least once in a two week period.

And yeah, there's already a service that simplifies this sort of thing, but you'd probably use that in conjunction with your own hidden 'stash', if you're not comfortable storing the keys to your metaphorical kingdom with a third-party directly.

These days, I just have passwords to various accounts that I own ready to send to my wife so she can shut them down properly (or manage them) in the event that something happens to me.

Note - this is no substitute for a proper will and testament and an appointed / trusted executor, however life sometimes puts us in circumstances where the traditional isn't always possible - and incapacitated doesn't always mean dead.

Vote Up Vote Down