frc-frecon / frecon

An API for building scouting apps for FRC competitions
MIT License
3 stars 0 forks source link

Configuration #50

Closed Sammidysam closed 9 years ago

Sammidysam commented 9 years ago

We need a configuration manager so that we can have some configuration variables such as

As was mentioned sometime in the past though I do not at all recall when, we should also store Mongoid's configuration inside of our FReCon configuration and then send that to Mongoid. That will include the environment and most other things.

rye commented 9 years ago

JSON would be good for that. We can also use the idea that you have regarding embedding the Mongoid configuration in things.

As far as system configurations go (which might be something we want to look at), for user familiarity, we might want to look at adhering to the XDG Base Directory Specification. Effectively, we want to support ~/.config paths (based on the environment variable, not just our own configurations :wink:).

rye commented 9 years ago

YAML would be good for this also. I did some work related to this in my rdeployd project.

andbass commented 9 years ago

TOML is another format that is super simple but still very flexible. Check it out here: https://github.com/toml-lang/toml. There's a few Ruby libraries available.

rye commented 9 years ago

I like how TOML looks, but I'm unsure whether or not our potential users will know what to do with it.

Sammidysam commented 9 years ago

Yeah, I'd say that YAML or JSON is preferred since pretty much everyone seems to know them at this point.

rye commented 9 years ago

We can use YAML. I'm going to fold this into #67.