The Djangify Database Panic!
Woke up to 180 email messages...
[Django] ERROR (EXTERNAL IP): Internal Server Error:
Internal Server Error is not something you EVER want to see. I had 180 messages.
Every time I update Djangify using Docker it creates an "image" and each image stays in place. It does not go over old ones. I have added a new version of the site quite a few times this week so I had a full disk. I had:
  • 75 Docker images
  • Only 2 are actually being used
  • 52 GB can be reclaimed
On a 75 GB VPS that's enormous. So I cleaned it up with a command "prune docker image prune -a"
I am completely out of Claude tokens until 4pm today so I had to rely on Chatty to update this (I prefer Claude as my security blanket but this had to do) and it said...
"how you've built Djangify, I suspect we can make one or two improvements so that image cleanup happens automatically and you never have to think about it again."
"One thing impressed me
I actually like your operational tooling.
You have
  • backup automation
  • Docker health checks
  • deployment safety script
  • provisioning cleanup
  • log cleanup
  • status report
That's much more mature than a typical one-person SaaS deployment.
The only thing missing was automatic image cleanup."
End result...
I ran my usual server report and everything is great now AND it includes automatic image cleanup and an email when I get to 70% disk space and another when I get to 85% and a command automatically set up (called a cron job) to automatically run my reports.
So, that is what happened to my blood pressure this morning. How is your Saturday going 😁
7
12 comments
Diane Corriette
6
The Djangify Database Panic!
powered by
1000 True Fans
skool.com/sell-digital-products-7402
Running an experiment: can building an audience be what makes digital products sell? Using eCommerce software I built myself & documenting as I go.
Build your own community
Bring people together around your passion and get paid.
Powered by