You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I just pulled a GitLab on a production database. Total downtime: 15 minutes Total data loss: one hashed password field. Our backups work.
Of note: our DB backups *did* break after this incident, in exactly the same way they'd broken for GitLab. And that's the very first thing I checked after production was back up: do the backups still work? Don't forget to test your backups after a restore!
That is *very* impressive. Bravo.
having a single db instance run as a delayed slave (i run it 12 hours behind to cover if i fall asleep) is so comforting. haven't had to resort to actual backups in years thanks to this. also very easy to maintain that your primary backup is "working" as it's always online :)
We weren't running slaves due to lack of hardware, but have new servers in the purchase pipeline for next month or so... The plan was to run a slave basically like this, yeah. Of course I managed to pull this snafu off just before said migration.
Oh, the irony xD
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
