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

Provide ewf configuration system #121

Open
jocelyn opened this issue Oct 29, 2013 · 0 comments
Open

Provide ewf configuration system #121

jocelyn opened this issue Oct 29, 2013 · 0 comments
Labels

Comments

@jocelyn
Copy link
Member

jocelyn commented Oct 29, 2013

Currently we don't rely on any file to configure the behavior of EWF classes.
But in practice, the code may have hard-coded port number when connector is Nino, or verbose status settings.
And for nino, we can imagine many more settings in the future.

Thanks to WSF_SERVICE_LAUNCHER_OPTIONS_FROM_INI , we have a simple way to use an ini file for those settings.

But what about having a default configuration location and format.
And by default, the EWF code would load in order

  • if environment variable EWF_INI is set to an existing file
  • if there is a ewf.ini in the current path
  • if there is a ewf.ini in /etc/ewf/conf/ewf.ini , or on Windows %APP_DATA%/... (to be defined)

An alternative would be to have a ewf folder instead of a file, this way we can reuse it for other purpose.
For instance, we could have various tool in it that could be reused, even resources such as icons, and so on.
And we could have EWF module that could reuse this folder, such as CMS, or gewf tool, ...
So we could just use

  • environment variable EWF_DIR
  • or ".ewf" in current folder
  • or "/etc/ewf" on linux, ...

About Nino and port number, probably, this should not be set from EWF code, but we could have an alternative with a "nino" specific configuration file.

All this are for now just idea, but with "gewf", and also "cms" component, sometime I would love to have such common place.

Maybe this is not that easy for now to have a system wide folder, since this would be a trouble with application compiled with various EWF framework, but soon or later we should start thinking about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant