-
Notifications
You must be signed in to change notification settings - Fork 170
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
standard config file lookup #290
Comments
|
Nothing is impossible ;), but I'm not sure about this. IMO a config file is tied to a specific gallery, as you may want to use different directories/theme/plugins/etc. for different galleries. And I think that global config are often introducing confusion because it's easy to forget that there is a global config somewhere. |
|
After digging a little I realized I could have a common sigal conf file for all galleries, given that in my context, same thumbnail sizes, source and destination folders, author etc. album titleThe possibility to have album title in ZipHaving zip_gallery be a constant file-name is a no-go because you don't want people to have all the zips they download from your site being named So, I use this and suggest it could be new default or new example in conf file comment: *Still, the need expressed by @anarcat is relevant. |
There could be a logging message, indeed.
That would be a good addition to the config file comment 👍 . |
so in my long, ongoing shopping list, i'd like to add the capacity to load configuration files from standard locations. what i am doing right now is that i have a base config file that I copy all over the place. i think that's silly: that config file should work for gallery A as well as gallery B, without me having to copy that thing over. yes, they will have the same name: I don't care about that. in fact, ideally all relevant config files would be merged on top of each other so i could have a base, global config file with sane defaults and then be able to override that with a one-line config per gallery.
so, for example, I'd like sigal to load
/etc/sigal.confif it's available, then~/.config/sigal.confand./sigal.conf(current default). i am not sure what--configshould do - maybe it could just wipe that list and replace it with a single config.would this be a good idea? i looked at the code briefly and i don't think it would be impossible to do...
The text was updated successfully, but these errors were encountered: