Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Config file placement and config defaults #1

Closed
ryeng opened this issue May 1, 2013 · 1 comment
Closed

Config file placement and config defaults #1

ryeng opened this issue May 1, 2013 · 1 comment
Assignees

Comments

@ryeng
Copy link
Contributor

ryeng commented May 1, 2013

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.

@bjorgan
Copy link
Member

bjorgan commented Feb 13, 2016

Fixed in 59e1a78

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants