Back
Similar todos
🪦 retired the old 
#djangopackages droplet because the new one is running stable
Move blog from old droplet to new fancy droplet that isn't being attacked every other day
Set up a fresh droplet (server) with the same configuration as the previous one to overcome certbot renewal bug that crashed nginx 
#deepmeditate
remerge old droplet and new droplet for the better security
Temporarily break 
#wip when trying to migrate to Digital Ocean, but requests started timing out so I reverted the change
🚀 refactored my server setup, shut off a DO droplet, redeployed two dozen websites, and configs are getting smaller and much easier to support
debating moving #djangopackages to a new droplet or provider since having some DO issues
Create fresh DigitalOcean droplet to be replacing older one from 2016
🖥 migrate 
#grpcbin to new hosting
started migration from old host 
#misc
Restart DO droplet, investigate dodgy Cron job issue
deployed existing RO-version to the development droplet 
#ratingluk
migrate personal site to LAMP droplet
Recover data from old droplet 
#discountkit
destroy and recreate DO droplet 🤦🏼♂️
Removed DO droplet I wasn't using; created a new $4/mo droplet with the latest version of Ubuntu (24.04); cloned my flask-vuetify-template repo to my MacBook.