-
Notifications
You must be signed in to change notification settings - Fork 40
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
Default uchiwa.json config is broken #2
Comments
@aaduffy Starting with Uchiwa 0.2.0, we now initialize undefined attributes so you won't face this issue. |
@palourde, I see. Thanks. Actually that means the default attributes are still broken. Either the default uchiwa version needs to be bumped up to 0.2.0 or the API config needs to be altered. As-is one cannot get a server to stand up using the defaults and must dig through the code to figure out why the uchiwa log is complaining about a refused connection. Please consider my PR, or alternately please consider bumping the default version in the same attributes file. |
@aaduffy The packages for 0.2.1 are not out yet, will do as soon it's released since I consider it's a bug with uchiwa and not the Chef recipe. |
The default configuration laid down by uchiwa-chef lacks port and path arguments. When uchiwa processes the config file the port and path become undefined. When uchiwa creates REST URLs these variables are interpolated as the string 'undefined' creating bogus URLs like "http://localhost:undefined" or "http://localhost/undefined/stashes".
The default configuration is defined in attributes/default.rb
The text was updated successfully, but these errors were encountered: