Skip to content

Deployment

Disk space

OneCamp keeps its own server's disk tidy, and tells your admins well before it
fills.

What runs on its own

Every install and every make update sets up a daily job at 04:40 server time
that:

  • trims Docker's build cache to 5 GB and removes images nothing uses any more;
  • rotates backups, keeping the number you chose;
  • writes what it did, and how full the disk is, to data/housekeeping.log.

Every container's log is capped at three files of 10 MB, so a busy service can
no longer fill the disk with logs.

You can run the same clean-up whenever you like, from the OneCamp folder:

make housekeeping

It prints how full the disk is and warns at 85%. To keep a different amount of
build cache, set it for that run, for example make housekeeping BUILD_CACHE_KEEP=10GB.

If you installed before v2.54.0 (v1.39.0 without AI), the next make update
sets this up for you. To set it up without updating, run make enable-housekeeping.

Warnings in the app

When the server's disk is 85% full, admins see a banner at the top of OneCamp
saying how much room is left and what to do. It can be put away for a day. At
95% it stays until there is room again, since a full disk stops OneCamp saving
messages and files. The same check is listed on the system check in Admin → System as Disk.

Making room

In order of how much they usually free:

  1. make housekeeping, for build cache and old images.
  2. In Admin → Archive, remove for good the channels, projects and files you
    archived and no longer need.
  3. Keep fewer backups on the server, or send them off it.
  4. Move to a bigger disk: OneCamp's data lives in the data folder, which you
    can move with the server stopped.

On OneCamp Cloud, all of this is done for you, and you're emailed before your
server gets full.