You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently getting the code to run from another account/home folder is a nightmare and takes alot of digging about to make it do so.
I'm also looking into making changes to the code within my own fork to make everything run under a user account and not just making it all run as root - this is a big security risk, while its only a laptiming system, to be taken seriously this needs to start happening.
Let me know your thoughts - I'm coming from a Systems Admin Point of view over a coder - these are the sort of things I am trained to pick up on.
The text was updated successfully, but these errors were encountered:
Personally I prefer to run things outside of the Pi home folder and in a specific account for ERLT.
This is more a security and monitoring reason.
Creating a global variable across ERLT for this reason called ERLTHOME
Changing the code to /home/pi/EasyRaceLapTimer to $ERLTHOME should be an easy change in the code to make this run from any home folder.
Then just setting up your /etc/rc.local to point to the account(erlt in this example):
(sleep 1; /home/erlt/EasyRaceLapTimer/ir_daemon/ir_daemon > /var/log/ir_daemon.log 2>&1 &) || /bin/true
(sleep 1; /home/erlt/EasyRaceLapTimer/web/start_sidekiq.sh > /var/log/sidekiq.log 2>&1 &) || /bin/true
Currently getting the code to run from another account/home folder is a nightmare and takes alot of digging about to make it do so.
I'm also looking into making changes to the code within my own fork to make everything run under a user account and not just making it all run as root - this is a big security risk, while its only a laptiming system, to be taken seriously this needs to start happening.
Let me know your thoughts - I'm coming from a Systems Admin Point of view over a coder - these are the sort of things I am trained to pick up on.
The text was updated successfully, but these errors were encountered: