The issue of running out of disk space when uploading a backup in a local developer Discourse is discussed. precessor followed the instructions to set up a local developer Discourse, but encountered an error when trying to upload a 4MB backup file.
precessor found a workaround by manually copying the backup file to the VM using SFTP and then restoring it through the Discourse admin panel. This involved:
Connecting to the VM via SFTP
Copying the backup file to /vagrant/public/backups/default
Starting the rails instance
Restoring the backup through http://localhost:4000/admin/backups
skozz confirmed this workaround also works for them when installing Discourse on OS X.
I’ve followed the instructions (this and this) to get a local developer Discourse running. It seems to have worked, and I am browsing at http://localhost:4000/ as admin. I would now like to upload the backup of my working cloud Discourse (a new install on DigitalOcean, the backup file is only about 4MB). The plan is to hack away on the local version.
My backup upload fails with
“There has been an error while uploading ‘my-discourse-2016-04-04-131830.tar.gz’: There is not enough space on disk to upload this backup.”
Back to the local developer Discourse, here is an image of the output from the ssh to the VirtualBox VM when I try to upload the backup (I am not sure if it will help):