-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
error running ve/bin/pip bin/srv.py #296
Comments
@j75 It's a bug in the documentation of course, it should be |
However I have installed the
|
@j75 Use pip from your virtual environment for that:
|
A small step forward:
Shouldn't be all these dependencies in |
Actually, they all are mentioned in the README.md file:
Probably you are right, we should add them to |
Neither do I, but how could I specify that? I am following the docs that states that all I have to do is to run Please note that in the documentation the part referring to the configuration is located after the part discussing server start. |
@j75 Yes, you are right. We should fix this part. I hope that now is everything configured correctly and almost up and running. Please ping me via email (igor@chub.in), I will mail you the last part that is not committed into this repository, and after that you will have a running 1:1 copy of wttr.in at your local site. |
The last error message I have now is
|
@j75 It is if you have no IP2location key. This is fixed, please update |
I did, and here's what I have now:
I have installed (on my Ubuntu system) the geoip-database package and thus I have a file /usr/share/GeoIP/GeoLiteCity.dat that I gave as a value to the WTTR_GEOLITE environment variable; however I noticed that in your README.md you are using a GeoLite2-City.mmdb file, maybe in a different format, how could I get one like that ? |
Yes, sure, you can download it from here: https://geolite.maxmind.com/download/geoip/database/GeoLite2-City.tar.gz |
Well, it spite of defining
OK, I moved the file in the
Then I performed a
|
Yes, that was my fault. Thank you for reporting it.
All those problems are fixed now. Now you can use the environment variables, Ok, now please:
|
|
Now it is fine; it just tries to create Now you have two options:
|
Yes, the server starts, but performing a GET @ http://127.0.0.1:8002/ results in an internal error (500), the log saying
|
@j75 I fixed it, but in your case the IP address can't be geolocated, i.e. you will be sent to Oymyakon
|
Yes, it displays
So, where is this |
Sorry for the delay. It was an extremely busy week, but it is better now. This time the error message is correct. The problem is that the caching server (that caches all the queries) is not reachable. because you did not start it. Can you please start it first?
As soon as your own server is up and running and functional, Usually people does not install wttr.in on their own, they just use it, but for that rare users that really need to have their own running copy of wttr.in, it is extremely helpful to have up-to-date and correct documentation. Thank you very much for your time and your efforts |
Unfortunately, still doesn't work! 😟
My questions are:
|
... however, their configuration file (where the weather provider is chosen) seems to be different from the |
I think that what we will do instead (soon), is that it we will use one own rendering engine,
It does not matter in this case. It should work with double slashes too, even if they look ugly/suspicious
Please use the URL I've sent you in email.
On the server the files looks like:
But the values are being overridden by command line options, so it actually does not really matter what you have here. |
I was following the README :
However, bin/srv.py exists:
How should I proceed further?
The text was updated successfully, but these errors were encountered: