Support for Alternative Config File Extensions #379

Closed
derks opened this Issue Jul 7, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@derks
Member

derks commented Jul 7, 2016

Currently application and plugin configurations are expected to end in a .conf or they are ignored. This doesn't make sense for an application using JSON or YAML configuration files.

@derks derks added the stable/2.10.x label Jul 7, 2016

@derks derks added this to the 2.10.0 Stable milestone Jul 7, 2016

@derks derks self-assigned this Jul 7, 2016

@derks derks changed the title from Support Plugins with Alternative Confix Suffix to Support Plugins with Alternative Config Extension Jul 7, 2016

@derks derks changed the title from Support Plugins with Alternative Config Extension to Support Alternative Config File Extensions Jul 7, 2016

@derks derks changed the title from Support Alternative Config File Extensions to Support for Alternative Config File Extensions Jul 7, 2016

derks added a commit that referenced this issue Jul 7, 2016

@derks

This comment has been minimized.

Show comment
Hide comment
@derks

derks Jul 7, 2016

Member

Added in cement/master (2.9)... This is now configurable via the CementApp.Meta.config_extension option (default .conf).

Member

derks commented Jul 7, 2016

Added in cement/master (2.9)... This is now configurable via the CementApp.Meta.config_extension option (default .conf).

@derks derks closed this Jul 7, 2016

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