galileorc(5)

📦 version 0.5.1, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

galileorc 💖 (section 5, File Formats Manual)

okay bestie, so this is the manual for galileorc — the config files for the galileo Fitbit synchronization utility. yep, the whole thing. it's giving "settings but make it a vibe" ✨

NAME

galileorc — configuration files for the galileo Fitbit synchronization utility 🎀

DESCRIPTION

so the galileorc file is literally just there to hand galileo(1) some default settings, so you don't have to keep typing the same stuff over and over like a broken record 😭 any setting you'd normally pass as a command-line argument to galileo can live in this config file instead. no cap, it saves your wrists.

but here's the tea: settings you put in the config files can be overridden by run-time command-line switches. see galileo(1). 👑

FILES

these files get read if they exist. later ones override previous settings, and settings given on the command line override anything defined in configuration files. hierarchy? slay. 💅

  • /etc/galileo/config
  • $XDG_CONFIG_HOME/galileo/config (the XDG_CONFIG_HOME environment variable defaults to ~/.config if it's not defined, just fyi)
  • ~/.galileorc
  • any file specified with the -c command-line switch

SYNTAX

the settings file is defined in YAML format, bestie. blank lines and comments (from the first hash character # all the way to the end of the line) are ignored — so go off, annotate your heart out 🦋

the config file is parsed as a dictionary of settings, which means every setting is defined using a keyword followed by a colon character. for single-value settings (the majority of them), the value just follows the colon, like:

do-upload: true

and for settings of type list (such as the tracker ID inclusion and exclusion lists), the values show up with an indentation on subsequent lines and prefixed with a dash, like:

include:
  - '123456789ABC'
  - '9876543210AB'
notice the quotes on those IDs? that's not decoration, that's survival. more on that in BUGS 👀

SETTINGS ✨

the following settings can be added to the configuration files — not all options have to be specified; any that are not mentioned will leave the defaults in effect. see galileo(1) for details about the default values. 💖

  • logging — controls the amount of progress output. can be verbose to display progress during synchronization, debug for more detailed information useful for diagnosing problems, or quiet to display only warning and error messages. pick your fighter 🌈
  • syslog — setting this to true will send all logging output to the syslog facility. due to the rate-limiting of some syslog servers, this option might not work in combination with the debug log level. (lowkey a trap, be warned) 💀
  • include — the list of tracker IDs to synchronize. if this is specified then only trackers from this list will be synchronised. main character trackers only 👑
  • exclude — the list of tracker IDs not to synchronize. not you, not you, definitely not you 🙈
  • force-sync — setting this to true causes trackers to be synchronized even if they report that they already have been synchronized recently. no excuses, we're syncing anyway 🔥
  • daemon-period — this defines, in milliseconds, the period at which a synchronisation attempt will be performed when galileo is run in daemon mode. tick tock ⏰
  • keep-dumps — setting this to true causes galileo to save the data retrieved from trackers to the directory specified in dump-dir. hoarding? valid 💾
  • dump-dir — the directory used for saving tracker data if the keep-dumps option is set. 🍓
  • do-upload — setting this to false will prevent galileo from sending tracker data to the Fitbit web service. staying offline, iconic behaviour 🧚
  • fitbit-server — this setting allow to specify the name of the server to connect to when performing the synchronization. yes bestie, you can point it elsewhere 💜
  • https-only — setting this to false will allow galileo to fallback to unencrypted HTTP if HTTPS fails for sending tracker data to the Fitbit web service. unencrypted?? in this economy?? 😭
  • hardcoded-ui — this is a structured section that includes the answers needed during the pairing/firmware update process. 🎀

EXAMPLE 🌸

the following is an example configuration file:

daemon-period: 60000
keep-dumps: false
do-upload: true
dump-dir: ~/.galileo-tracker-data
logging: verbose
force-sync: false
https-only: false
include:
  - '123456789ABC'
  - '9876543210AB'
exclude:
  - 'AABBCCDDEEFF'
  - '881144BB1234'

copy it, paste it, make it yours, bestie 💅

SEE ALSO

AUTHOR

written and maintained by Benoît Allard, with contributions from other authors. shoutout to the whole squad 🫶

BUGS 😭

tracker IDs which consist of only numbers must be surrounded with single quotes (as in the EXAMPLE section above). it's probably a good idea to always quote tracker IDs to avoid possible confusion. fr fr, just quote them, don't fight the parser ⭐

please report additional bugs to <https://bitbucket.org/benallard/galileo/issues>. they'll be loved and appreciated there 💖

and that's the whole page, bestie 🎀 this was galileorc(5) from galileo version 0.5.1, dated June 2014 — yes, an elder, but a legendary one 👑 go forth and configure responsibly, and remember: command-line switches always get the final word 💅✨

📦 where this page comes from