Closed gbernal closed 2 years ago
Wonderful! Thank you @davesteele!
Dear @davesteele
One more question, can you please clarify what does comitup-callback mean in this path ?/usr/local/bin/comitup-callback. Is comitup-callback my script or a directory? My RPi only had usr/local/bin/ but nothing after that. Is that a path I have to create?
Also, Am I right to assume that I have to modify comitup.conf from # external_callback: /usr/local/bin/comitup-callback
to external_callback: /usr/local/bin/comitup-callback/myscript.py
?
Thank you again.
comitup-callback is an executable script that is your responsibility. The path is defined by the external_callback parameter, but, if you don't define that parameter, it takes the value shown in the comitup.conf comment. So, no, you don't have to make that change.
Dear @davesteele,
Thank you first of all for sharing your work. I'm using comitup for a research project on a raspberry pi 3B. I have a python script that sends over WebSockets the device IP every time the pi is connected to the new user's local router so I can then ssh into the device without having to connect to a monitor.
I have seen at StackOverflow that people suggest putting the python code here
"/etc/network/if-up.d/upstart" just after "all_interfaces_up"
https://stackoverflow.com/questions/29204423/how-to-automatically-run-python-script-after-raspberry-pi-fully-bootsBut since the network interface is handled by comitup I figured it might be better to ask here how to go about. (The upstart file is no longer in the location suggested in stackoverflow.)
Thank you in advance.