OK sorry, didnt know you were using auth.sh (actually it could be called anything)
The upgrade will only keep config.ini and server.pem (if you are using ssl)
If you are going to do some real custom development like using auth.sh or some other events i think you might need to run your own raspbian image instead. Just install raspbian and install virtualhere then you can control everything yourself. I dont want to be guessing what customers are changing and have them complain its not kept on upgrade.
You can define it in the config.ini file. Just directly write bash script instead of where you call /root/auth.sh
However its just it gets complicated as it all has to be on one line in config.ini and its easier if its in a separate file thats why the example shows that.
.
OK sorry, didnt know you were using auth.sh (actually it could be called anything)
The upgrade will only keep config.ini and server.pem (if you are using ssl)
If you are going to do some real custom development like using auth.sh or some other events i think you might need to run your own raspbian image instead. Just install raspbian and install virtualhere then you can control everything yourself. I dont want to be guessing what customers are changing and have them complain its not kept on upgrade.
Maybe you could add auth.sh
Maybe you could add auth.sh to your internal list, seeing as how you have it directly mentioned in various examples?
even better would be a way to define that inside config.ini and then it wouldnt matter
.
You can define it in the config.ini file. Just directly write bash script instead of where you call /root/auth.sh
However its just it gets complicated as it all has to be on one line in config.ini and its easier if its in a separate file thats why the example shows that.