@concretedog as a developer who's got a few years of experience on large web platforms, find it very difficult to understand what #tindie has been doing specifically. How did they manage to get to this point? Did they not test it? Are they using tech they don't understand? Is their tech stack too confusing and they just stare blankly at log files full of errors?
Will never know - fascinated what led to this disaster. Lack of competence and leadership. The damage done may never be repaired!
RE: https://rustedneuron.com/@jackwilliambell/116422127293374602
Tindie's website has been 'down for maintenance' at least four days straight that I know of; possibly longer. But I can find nothing indicating *why*. A search for recent news about Tindie returns zero articles.
Something is certainly up with #Tindie, but no one is talking about it that I can find.
So no notification of upcoming maintenance up front, no communication at all in several days of downtime. And now you want us to believe that this is a planned migration?
I do hope Tindie comes back alive though, cause that gives me reasonable time to organize an alternative.
@tindie This really does not sound plausible.
You make the new platform - get it working, and tested.
You keep the old platform running while you do that.
You tell people in advance about the planned migration and expected timescales.
You have a fallback plan if something goes wrong.
Then you may need some small downtime to migrate a live database with no new transactions. But if that takes more than an hour you are doing it wrong!
I hope the API on the new platform is compatible.