You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flyby should search for config files (flyby.qth, flyby.tle and flyby.db) in a defined order and provide sensible defaults if no config file is found. Maybe following the XDG Base Directory Specification (http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html) is a good idea.
It should be possible for the system administrator to provide a default for users that don't have their own config files, e.g. in /etc/flyby.qth. System satellite TLE and frequency databases would also be easier to keep up-to-date than files spread out in users' home directories.
The current approach, copying files from a known location if no config files are found, is not a good solution for providing defaults. Flyby should be able to start without any config files or templates in known locations.
I guess flyby.qth is a config file, but are flyby.tle and flyby.db data files or config files according to the XDG?
Should the TLE list be the union of all TLE files in the search paths, or should flyby use the first file found? What about the frequency database? If a union of all files is used and there's a file in /etc/flyby/, the user can't remove orbit parameters/frequencies listed in that file by having a different database in $HOME/.flyby/. Maybe $XDG_CONFIG_DIRS is a good enough solution to that problem.
Should there be an /etc/flyby.tle.d/ directory with several files? That would make it easier to organize satellites into groups (e.g., amateur.tle, weather.tle, etc.), or to add satellites during a launch.
The text was updated successfully, but these errors were encountered:
Flyby should search for config files (flyby.qth, flyby.tle and flyby.db) in a defined order and provide sensible defaults if no config file is found. Maybe following the XDG Base Directory Specification (http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html) is a good idea.
It should be possible for the system administrator to provide a default for users that don't have their own config files, e.g. in /etc/flyby.qth. System satellite TLE and frequency databases would also be easier to keep up-to-date than files spread out in users' home directories.
The current approach, copying files from a known location if no config files are found, is not a good solution for providing defaults. Flyby should be able to start without any config files or templates in known locations.
I guess flyby.qth is a config file, but are flyby.tle and flyby.db data files or config files according to the XDG?
Should the TLE list be the union of all TLE files in the search paths, or should flyby use the first file found? What about the frequency database? If a union of all files is used and there's a file in /etc/flyby/, the user can't remove orbit parameters/frequencies listed in that file by having a different database in $HOME/.flyby/. Maybe $XDG_CONFIG_DIRS is a good enough solution to that problem.
Should there be an /etc/flyby.tle.d/ directory with several files? That would make it easier to organize satellites into groups (e.g., amateur.tle, weather.tle, etc.), or to add satellites during a launch.
The text was updated successfully, but these errors were encountered: