MONS(5)
π MONS(5) β the mons config file, explained by your favorite unix bestie π
okay so this is the manual page for mons, section 5 of the manual (that's the file-formats girlies π
), and honestly? it's a config file glow-up. let's get into it.
β¨ NAME β¨
mons β the configuration file, bestie. that's it, that's the whole name section. iconic minimalism.
πΈ SYNOPSIS πΈ
$XDG_CONFIG_HOME/mons/config.yaml
that's the path. that's where she lives. $XDG_CONFIG_HOME/mons/config.yaml β write it down, tape it to your monitor, get it tattooed, idc. π«Ά
π DESCRIPTION π
the mons configuration file uses the YAML format. yes, YAML. mind your indentation, queen, because YAML will absolutely humble you if you get sloppy with the spaces. π
β¨ OPTIONS β¨
okay here's the whole menu, no skips, no skimming, we're reading the entire thing together like the devoted besties we are. π
source_directory: str | Noneβ the default path to use when building Everest from source. once you've set it, you can still override it by handing over a path from the commandline. so it's a default, not a prison. πbuild_args: List[str]β build options that get passed todotnet buildormsbuild. and listen: if thedotnetcli is not reliably available, both of those tools can acceptmsbuildoptions β so you're covered either way. π seemsbuild(1)for the available options, iykyk.launch_args: List[str]β the default command-line arguments used when launching Celeste. heads up though: Everest will also read arguments from theeverest-launch.txtfile, so check the Everest documentation for the deets. π¦downloadingβ the whole section for options related to downloading files. she's a container, she has children:everest_builds: str | Noneβ the URL used to fetch the list of Everest builds. by default, the URL is read from the contents ofhttps://everestapi.github.io/everestupdater.txt. π§mod_db: str | Noneβ the URL used to fetch the database of Everest-compatible mods. by default, the URL is read from the contents ofhttps://everestapi.github.io/modupdater.txt. πthread_count: intβ the maximum number of parallel downloads to use. go fast, but like, responsibly. π₯
overlayfsβ options pertaining to installs using an Overlay Filesystem, and yes it's Linux only, sorry to the mac girlies. π seemons-overlayfs(7)for the full lore on overlayfs installs.data_directory: str | Noneβ used for theupperdiroverlay mount option. each install gets its own subdirectory within this folder, and that subdirectory will contain all the files added or modified by that install. β this directory should be writable.work_directory: str | Noneβ used for theworkdiroverlay mount option. each install gets its own subdirectory within this folder, and that one gets wiped before each use (not me gasping π). this directory should be writable and on the same filesystem asdata_directory.
real talk for a sec: those two directory requirements aren't suggestions, bestie.data_directoryneeds to be writable, andwork_directoryneeds to be writable and living on the same filesystem asdata_directory. also rememberwork_directory's per-install subdirs get wiped before every use β that's by design, that's the whole bit. π«Ά
π COPYRIGHT π
2022-2023, coloursofnoise
and that's the page!! mwah π this was mons, manual section 5, dated Aug 23, 2023, brought to you by coloursofnoise β go config responsibly, and remember: YAML indentation is a love language. πβ¨π¦
π¦ where this page comes from
- nixos 26.05: everest-mons 2.0.0
- nixpkgs unstable: everest-mons 2.0.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms