|
|
|
|
|
by scubakid
340 days ago
|
|
That's an impressive number of years to stick with a product you questioned. Probably 2x longer than Google would have maintained it lol (who says products by indie devs always have higher long-term support risk?!) I'm really happy to hear it turned around for you. The 4 months of down time sound terrifying. Can you share more about how you navigated that, how it impacted customers, and what you were able to restore vs what you couldn't, and what processes you changed in the aftermath? |
|
The biggest impact for the business was not making any sale during this period and my SEO rankings going down. Actually the site disappeared from search. I guess the biggest impact for me - personally - was psychological. All production data was gone and I was seeing it as a sign I should just let it go. I had all the source code, so in theory I could do it, but not sure I would have the motivation to.
Then in the end my thingy was hosted in a section that was salvaged from the fire. I saw it as a sign that actually I SHOULD keep going, lol. I don't remember exactly how long it was off but yeah, 4-6 months. Everything was restored though.
The only thing I did was to implement automatic backups and to a different datacenter. I remember from the incident, one issue for many was their servers were hosted in Strasbourg with backups also hosted there.
I've touched on this in my last comment, but my wife is by far my biggest motivator. It's tough life for us working solo, with our minds playing tricks on us all the time. It always sounds so much easier to go and work for someone else again or to just start a new side project from scratch. Not sure if there's any Alex Hormozi fan here, but one thing he's always repeating is to not give up, not start anything new over and over and just keep pushing that one project.