Add a few default locations for the Palladium config file

[dnouri]

If PALLADIUM_CONFIG is not set, Palladium will try to find a
configuration file at these locations:

• palladium-config.py
• etc/palladium-config.py
• /etc/palladium-config.py

I used print() rather than logging when a default config location is used because logging isn't set up at that point yet.

[coveralls]

Coverage increased (+0.0002%) to 99.927% when pulling 74da978 on feature/default-configfile-name into 60db450 on develop.

[BenjaminBossan]

This will not be helpful on Windows ;)

[dnouri]

This will not be helpful on Windows ;)

Do you have an idea on what locations would be useful to look for on Windows? Maybe C:\Benjamin\Palladium.CFG? :-)

[BenjaminBossan]

I know that there was a Python package that provides all the default directories for the common OSes but I cannot find it unfortunately.

[topiaruss]

? https://pypi.org/project/appdirs/ <https://pypi.org/project/appdirs/>

On 26 Apr 2019, at 17:55, Benjamin Bossan ***@***.***> wrote: I know that there was a Python package that provides all the default directories for the common OSes but I cannot find it unfortunately. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABOKWLYM5J6NVXPFSM2YF3PSMXW5ANCNFSM4HIOMLNQ>.

Russ Ferriday -- Software Product Architect, Developer, Mentor Founder & CTO Topia Systems Ltd topiaruss@gmail.com -- +44 7429 518822

[BenjaminBossan]

Yes, that's the one.

[dnouri]

Thanks for the pointer. It's true that I've included one global path (/etc/palladium-config.py) in the list of default locations, with the two other locations being relative to the current working directory. The intention here was to include the global path as a convenience for Docker containers. I don't think global directories make sense apart from that use case. Palladium projects will typically include the configuration relative to the project root within the source tree. After all, you'll want to be able to develop multiple Palladium projects at the same time. And I'm now thinking that the one global path may not be useful after all. (What do you think?) At the same time, I don't believe we want to put configuration in app directories, such as the ones made available by the appdirs package, because that's not how you use Palladium on your development machine.

Another question I have is: Do we want the tutorial to make use of the default palladium-config.py in the current working directory?

[BenjaminBossan]

For the docker use case, is it too much to ask from the user to specify PALLADIUM_CONFIG?

Regarding the tutorial, it should teach the "proper" way of doing things.

Also, at least in my use cases, I now always have multiple config files, so having that default would not be helpful.

[dnouri]

Thanks for the feedback. I've removed the /etc/palladium-config.py entry.