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

Formats and Backends #53

Open
txomon opened this issue Nov 14, 2016 · 1 comment
Open

Formats and Backends #53

txomon opened this issue Nov 14, 2016 · 1 comment

Comments

@txomon
Copy link

txomon commented Nov 14, 2016

I have been looking at the codebase, and it looks like you are calling the formats of the files as backends. However, you also look like willing to implement different backends, such as Environment backend.

Would it be possible to have the code refactored to accept different backends (currently from my point of view only file backend is supported) such as redis, postgres, etc?

To have retrocompatibility, it should be possible to use new backends such as redis, postgres, etc. to load-safe configurations.

Just in case, I am looking at this as a possible implementation of Archaius in python

@ssato
Copy link
Owner

ssato commented Nov 15, 2016

Thanks for your suggestion!

Technically, it may be possible to add support of them that by extending the current base class
of backends, anyconfig.backend.base.Parser. But I feel that it may be difficult to abstract
contents in DBs/KV stores from the point of view of semantics.

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