Kaczorek wrote: This is absolutely correct. GPS Panel is designed to show real and the actual GPS position and if it is not available it shows default position (hard coded because it needs to show something). Should you consider any other approach do not hesitate to suggest it. It was just my assumption but I would be more than happy to do it the way you want.
To change this behavior you need to change gpspanel.py file, which I do not recommend because all the changes will be overwritten by future updates. So it is better I change it for all the users.
Changing astropanel.conf does nothing to gpspanel. It just works with Astro Panel, which calculates bodies positions for a specific location (which can come from GPS or static config).
BTW. I agree it is kind of a mess but I haven't came up with a good solution. As for now there are separate locations for:
1. Astro Panel (GPS or astropanel.conf file or Weather Plugin location)
2. GPS Panel (only real GPS receiver)
3. KStars (GPS or static configuration of KStars location)
Any ideas how to combine these? Bear in mind that before first start of Kstars it's configuration defaults to London, before connecting GPS receiver GPS Panel defaults to Warsaw, before setting up astropanel.conf Astro Panel defaults to GPS or Weather Plugin
Kaczorek wrote: Thanks for the ideas guys! Each and every worth considering.
Some users do not use GPS at all, so GPS Panel is useless for them but they will would like to use Astro Panel with Solar System objects data. We have to have good source of location data for users that do not use GPS, so config file is a must because... they will not necessarily use Weather Plugin at all.
So things are getting complicated indeed. Especially if we add location data for KStars to this puzzle. To complicate things even more some users prefer to use Skychart than KStars...
The idea to use environment variables seems interesting and easy to implement. Let me rethink the approach. There is some space for improvement for sure.
I'm very curious about 'bad gateway' errors you report. Technically speaking the root cause is gpspanel.service or respectively astropanel.service is down, so nginx server which handles web interface cannot display content in sliding menu panels. Have no idea why would they go down though. To nail it down I need your help.
If it happens just run (depending which panel is not available):
systemctl status gpspanel.service
systemctl status astropanel.service
Send the output to github.com/rkaczorek/astroberry-server/issues or here.
AstroNerd wrote: ...all that is needed is a simplified way of entering own data to the astropanel.conf file, rather than having to edit the actual file itself...?. Also would it not be a good idea to use those same data inputs to feed the GPS panel, when a GPS is not present, so at least it will show correct location data, albeit static...rather than the Warsaw data..