Using raw vms are great for quickly self-hosting many products. Self hosting sentry is 50 services managed in docker-compose. The docs's arent very clear, but there is a way to use s3 to host the filestorage. Updating the config was too hard for me to figure out and now its all being logged to storage on the vm itself. Our selfhosted Sentry has died many times because it ran out of storage. I didn't realize that before. When you run out of storage, you are no longer able to even ssh into the machine to diagnose the problem. Anyways... this is how we do it on gcp.
From the gcloud cli run.
gcloud compute disks resize sentry-disk-name --size 1000 --zone us-west1-a
And on the machine itself run.
sudo apt install -y cloud-utils # Debian jessie
sudo apt install -y cloud-guest-utils # Debian stretch, Ubuntu
sudo growpart /dev/sda 1
sudo resize2fs /dev/sda1
for RedHat/Fedora/CentOS/etc.
sudo dnf install -y cloud-utils-growpart
sudo growpart /dev/sda 1
sudo xfs_growfs -d / # CentOS 6 needs `resize2fs`
Would also be useful to have some sort of alerts when the storage gets to a threashold... we'll get to that later. Lets just double the current storage and have the next one worry about it.
Big thanks to this stackoverflow post. https://stackoverflow.com/questions/22381686/how-can-size-of-the-root-disk-in-google-compute-engine-be-increased
More relevant links below: