How to increase disk space

AI-generated summary

Jakira is running Discourse on a local server with limited free disk space (4.7 GB on a 52 GB drive) and wants to expand storage by mounting an additional 50 GB disk. After sharing disk usage details Jakira, pfaffman suggests running ./launcher cleanup to free space by removing unused Docker images and containers. Jakira asks if they can directly add disk space, to which pfaffman replies that Discourse itself can’t resize disks but recommends editing app.yml to mount a new volume — for example, pointing /shared to a new path like /var/discourse/shared/standalone2 on the newly mapped drive. Jakira confirms this worked for their new site, though they had to restore from a backup afterward Jakira. The solution involves reconfiguring Docker volume mounts via app.yml rather than expanding the existing partition. Jakira also asks what ./launcher cleanup deletes — it removes unused Docker artifacts to reclaim space. The key takeaway is that storage expansion in Discourse requires manual volume remapping, not automatic disk resizing.

I have installed discourse & when I log into admin panel I can see free space is 4.7 GB which seems quite small to me. Server is host in my local machine & I have 50 GB total my current disk drive.
I have another disk which is 50GB which can be mounted to any folder.

How can I increase it?

[ Backups]

257.1 MB (4.7 GB free)
3 backups on Local Storage
Latest: 13 hours ago

Uploads

9.4 MB (4.7 GB free)

Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           798M   18M  781M   3% /run
/dev/sda1        52G   44G  4.7G  91% /
tmpfs           3.9G  1.2M  3.9G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sdb1        20G  8.5G   11G  46% /var/lib/docker
/dev/sda3        50G  138M   47G   1% /var/discourse/shared/standalone2
tmpfs           798M   32K  798M   1% /run/user/108
tmpfs           798M     0  798M   0% /run/user/1000
none             20G  8.5G   11G  46% /var/lib/docker/aufs/mnt/a7bca0843583fb5792ba29b4eab614e6b5cfab58b3b1f0ce69d2da7dde8f8f53
shm             512M  8.0K  512M   1% /var/lib/docker/containers/1e96d5d7adc41e50848903da415b8e664538cfb6cf7ff84e0f933d0944921578/shm
cd /var/discourse
./launcher cleanup

@pfaffman
Can’t I add more disk space?

Probably, but Discourse can’t do that.

Is there a reason not to delete unused docker images and containers?

Oh, sorry. You could edit app.yml

volumes:
  - volume:
      host: /some/other/path/standalone
      guest: /shared
  - volume:
      host: /var/discourse/shared/standalone/log/var-log
      guest: /var/log

what will do ./launcher cleanup action. from where it delete files?

can I use /var/discourse/shared/standalone2 since I have newly mapped drive?

what actions should I take after this change in app.yml

This worked.
But it is a new site. I had to restore from old.

Thanks @pfaffman