I have not tested yet but I can see that the main problema is that I don't have enough reading about the Resin.io Dockers.
Can you suggest me some blog or, maybe a YouTube so I can understand better how Resin.io Dockers?
I'm a "reading man" so don't spend time with YouTube,unless you know some very special video.
The best place to start is here:
https://resin.io/how-it-works/
And there are many resources on YouTube regarding git and git remotes. GitHub and Bitbucket have a lot of resources. I work for Atlassian, so I'd be recommending Bitbucket. You can have free private git repositories
To boil it down, your git client is really your first step to cloning my code. Making it your own would simply require either Bitbucket or Github repo you can clone.
This can be done easily following the instructions under heading "Importing an existing Git project into Bitbucket Server":
https://confluence.atlassian.com/bi...-code-from-an-existing-project-776640909.html
Clone from mine:
https://[email protected]/inodes/resin-docker-rtlsdr.git
Sending to yours:
https://[email protected]/yourname/yourrepo.git
This isn't compulsory, but this would allow you to change the code, and that would be where you would git push (origin).
I'll keep you informed about my progress. Your problem is my problem as I own three "wild" stations and need to care about them everyday via remote access with various issues and degrees of difficulty. Some of these problems would remain unsolved till my next visit,
That's why I'm very interested on this topic.
Cheers!
Having many RPI's and many locations was the reason I moved my project to Resin.io. You can have 5 devices for free.
This proved itself handy when I visited my wife's family in Japan. I removed one of my Sydney based RPI's, plugged it in when I got to Japan. I changed the GPS co-ordinates and various id's (I had to pre-arrange a couple, but that's not hard to do).
It took about 3 minutes for the changes to kick in.
I could have started from a blank SD, and it would have taken no more than 5 minutes.
Remote access into these is very straightforward with Resin.io as well. I can monitor and reboot without an issue. If however the power was interrupted, I'd just have someone at the other end turn on and off the power, and it would come alive again in Resin.io.
My previous solution used Docker and Docker compose. Resin doesn't allow Docker compose, so my docker file is really a group of applications in the one container (normallly a no-no, but it works). And thankfully Resin uses the benefit of Docker's repeatable and predictable image to build everything from scratch.
To install new versions of any of the clients, make a simple change to any of the scripts (i.e. put a space - which has no consequence - in the start.sh from my repo), push it to the remote (Resin), and Resin will completely re-build the image from scratch.
If there is a new version of the client software, it gets included immediately.
The error you're getting above though is odd. It might be as simple as not having the right remote.
I'd still double check your addresses. Delete and re-create the application if required.
Additional tip regarding Piaware:
Although it doesn't pertain to the Planefinder client, Flightaware moved away from using a MAC Address (the hardware address of the ethernet adapter), to an ID. I instead included PIAWARE_ID to map to this.
Booting your device would warn you of this.
Tip regarding your errors:
This might be a build error as well. Go to your Resin dashboard and click on your application, then "Releases". It should list the various times you've pushed a change using "git push resin master". These builds represent the equivalent of a whole new Docker image and will have a unique commit code. Each time you add a new RPI to this application, it receives the latest build.
This is also the reason I have two applications - one for my working production, and one for testing.
I can make changes to the code, push this to the test, the move devices to this. This could for example test a new version of the clients, or a change to the Dockerfile or start.sh. If I didn't like the result, I would move my device back and it would boot up with the old versions. If I did like the result, I would simply run a new "git push resin master", a new build would be created and the remaining devices would all update. Easy!
