Yes that's good enough! Sorry I missed your statement about shutting down first. To clarify I leave mine running since a dump can recover if it gets corrupt.
Basically my backup contains the database and the SQL dump (or equivalent) - that way I don't need to shutdown the service.
Most of the time that's perfectly fine, but if the database were in the middle of an operation you risk corruption.
Could get a hydrophobic coating to make the rain slip off the side mirrors more easily. There are also mirror rain visors that so what you describe.
I don't know about them but I'm using Voyager and see this on both the original and the cross post: https://files.catbox.moe/bzl885.png
If I hadn't opened the post in Firefox I would have thought I was being gaslit and the shitty blur was intentional lol.
Individually. If the app requires a DB, I put it in the compose file. This simplifies both backups and migrations. My tooling for backups has a pre and post script I can customize on a per app basis so I just have the pre do whatever *dump for that DB and the post clean it up (backup takes a tar of the folder).
What are the extra steps? I would think it would be less, no? Paywall would require you to sign up (or login), verify email, select a subscription, enter payment info, subscribe, then go back to read the article. This seems to just be sign up, verify email.
Agreed. I don't have an account, I used to look them up on archive.today but since that has its own... Baggage I just settle for no reading the rest lol.
Not a paywall. This particular article requires a free account to view it.
Or don't give your user docker and use sudo to use the docker CLI to get the same effect. Hell, you could even alias docker as sudo docker to get the same feel.
All things considered that was a better outcome than I expected.
You'll be tagged as the one who thought a shitpost was serious, got corrected, and doubled down.
My Call of Cthulhu session 1 is Saturday so that'll be interesting and hopefully fun.