multi.meshviewer.org isn't up to date

genofire / meshviewer-collector

Lets share a meshviewer and make a performance test

https://multi.meshviewer.org/

MIT License

0 stars 10 forks source link

multi.meshviewer.org isn't up to date #33

Open herbetom opened 2 years ago

herbetom commented 2 years ago

Hi,

according to https://data.meshviewer.org/collector/ new commits haven't been pulled in quite some time for multi.meshviewer.org (at least April). It would be great if this could happen.

Thanks a lot!

cc @AiyionPrime

AiyionPrime commented 2 years ago

@rotanid The reboot performed this night was not sufficient.

genofire commented 2 years ago

@rotanid need also to pull this repository for update (and the reload the meshviewer-collector, restart or reboot)

AiyionPrime commented 2 years ago

I think he has done that like three? days ago? At least my submission is in there.

herbetom commented 2 years ago

Yes, he pasted the following script:

#!/bin/sh
export GOPATH=/opt/go;
export PATH="$PATH:/usr/local/go/bin:$GOPATH/bin"

echo "update collector and build";
systemctl stop meshviewer-collector
go get -v -u github.com/genofire/meshviewer-collector;
echo "start meshviewer-collector";
systemctl start meshviewer-collector

This certainly could be automated. However, it would be good if this wouldn't result in regular restarts. So some form of check for available updates and a comparison with the currently running version would be required.

genofire commented 2 years ago

Oh good, one of my old scripts xD

That is for upgrading the daemon, not for updating the config file ...

But yes maybe we could write something, which autodetect changes on git remote

rotanid commented 2 years ago

not sure why it was no problem for around 1.7 years and all of a sudden we need regular updates? what happened?

herbetom commented 2 years ago

Well, my understanding is that it did run for quite some time, but it is currently required to manually "pull" all changes onto the VM. Bit I certainly could be wrong with this.

So the idea was to automate this process so that it can continue running without much intervention.

But that is just me trying to lower the burden for you, @rotanid 😉

It's also fine with me to just close this issue and keep everything as it is. It just would be great if changes, probably mainly within the config, would be deployed at some point in time.

rotanid commented 2 years ago

hm, if you say something went "different" during those 1.7 years since we took over this machine, i wonder why, because we did nothing (until a few days ago) besides regular apt updates and reboots...

genofire commented 2 years ago

i believe was not detected the last 1.7 years, because the URL changes in the config.toml was so low.

Maybe the upgrade script of the binary meshviewer-collector has the new config.toml also polled and fix it sometimes.

maurerle commented 7 months ago

Is this still up to date? It would be cool to update the meshviewer of this project to https://github.com/freifunk/meshviewer - so that one can see how many deprecated devices are there.

The map service is currently broken? And it would be cool to update the communities to a more recent state and be in sync with https://github.com/freifunk-gluon/census-exporter and https://api-viewer.freifunk.net/

Or is this project deprecated?

genofire commented 7 months ago

First, the census-exporter was develop without any take / hint to this project: https://github.com/freifunk-gluon/census-exporter/issues/4 So i do not know, why everybody want to make his own ...

if this project is down, i do not know i am willing to merge and maintain the code. But i do not have any access to multi.meshviewer.org anymore (but @rotanid ) ...