MONS(5)

πŸ“¦ version 2.0.0, in nixos 26.05, nixpkgs unstable

πŸŽ€ 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 to dotnet build or msbuild. and listen: if the dotnet cli is not reliably available, both of those tools can accept msbuild options β€” so you're covered either way. πŸ‘‘ see msbuild(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 the everest-launch.txt file, 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 of https://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 of https://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. πŸ’€ see mons-overlayfs(7) for the full lore on overlayfs installs.
    • data_directory: str | None β€” used for the upperdir overlay 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 the workdir overlay 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 as data_directory.
real talk for a sec: those two directory requirements aren't suggestions, bestie. data_directory needs to be writable, and work_directory needs to be writable and living on the same filesystem as data_directory. also remember work_directory's per-install subdirs get wiped before every use β€” that's by design, that's the whole bit. 🫢

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