-
Notifications
You must be signed in to change notification settings - Fork 478
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
forecast.io backend progress #83
Comments
I'm having trouble using the forecast.io backend with that branch. After cloning that branch, building, changing the .wegorc, and running I get:
Also I've noticed that this branch needs to update the routine that initially creates the .wegorc file. It contains keys such as:
but no corresponding key for forecast.io like this:
|
Hm, works for me. Can you double check you actually built the version with a |
That couldn't be the case, the binaries are in different locations. The wwo one is in my $GOPATH ( How do I specify the location as "LAT, LON"? Do I do something like this in .wegorc?:
|
yes, but without the space in between. Example for New York:
However this will probably not fix your error. |
Update! The forecast.io backend should now be in a usable state (see todo list in first post). @camelinc and other interested people: You have 48 hours to test the new backend in the |
I fixed the issue I was having. My problem was that one has to use the right config key for forecast: |
Indeed, thanks for the feedback. I just pushed an update, so that a nice error message appears when no API key is specified. |
Thanks @Daml, I merged your commit and slightly adapted it. The forecast.io branch has now been rebased onto master and is the new default backend. This issue stays open until at least the two non-optional points are fixed. |
Closing this since the last remaining todo is tracked by #87. |
I pushed the first version of the forecast.io backend to the forecast.io branch. Some points need to be adressed before merging into master:
Fetch
to the requested number of dayslat,lon
string?The text was updated successfully, but these errors were encountered: