-
Notifications
You must be signed in to change notification settings - Fork 27
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
install guide #94
Comments
I found out what was my problem : #95 But there should definitely be more explanation in the readme |
+1 |
A full guide for a map server setup is one of the things I have on my to-do list since a long time but I am no longer interested in doing. But I think the setup of a reverse proxy, compiling the client and so on does not belong in this repository but should rather be a seperate repo (map server setup guide) and possibly have a fancy readthedocs page. The guide in README.md is supposed to explain a standalone installation of hopglass-server. Your point about changing the default config values should be solved by adding more documentation to the example config (now possible with hjson). For whole map server installations I am always happy to help people out with a mumble session or questions via issue or forum (tag or PM me). The https://github.com/eulenfunk/mapconfig repository contains some template files that might be helpful. |
Is there a thogough install guide for a Freifunk-newbie?
I got hopglass-server running on our gateway 18 with the install guide from the README. Now I try to get data into my hopglass-server, but there is no data collected:
http://18.gw.freifunknord.de/hopglass/nodes.json
We use gluon 2016.2.5: https://github.com/freifunk-nord/nord-site
Up to now, we still use alfred, but we want to get rid of alfred.
I started an apache proxy and opened port 1001 UDP and Port 80 in our firewall.
What am I missing? How should the data get to the hopglass-server?
Can you add more info in the readme, so a new comer can successfully run hopglass with hopglass-server?
The text was updated successfully, but these errors were encountered: