-
I am using TallyArbiter TallyArbiter 3.0.3 / 3.0.4 installed as a CLI on a RaspberryPi as described here https://josephdadams.github.io/TallyArbiter/docs/installation/cli When i am starting TallyArbiter manually, editing a configuration, closing TallyArbiter and again starting TallyArbiter, config.json is read properly. If i then run TallyArbiter as a service via pm2 this config is not loaded again. If i again start TallyArbiter manually and not as a service this "old" config.json is again loaded properly. Where is the config saved when running as a service ? Why is this different when starting TallyArbiter manually and as a service ? Markus |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
a little update: Finally i found the way using autostart / Desktop Entry ... this was working ... sudo nano /home/pi/.config/autostart/tallyarbiter.desktop ... fill with: [Desktop Entry] ... save ... reboot ... and now tallyarbiter is starting on boot using the settings in .local/share/TallyArbiter/config.json. As mentioned above i do not know, why it is working this way ... but it is (at least for me) I would be great is somebody with better knowledge could explain and also edit/update the documentation accordingly Markus |
Beta Was this translation helpful? Give feedback.
a little update:
As i am a linux newbie i did some googling and tried several other ways to autostart tallyarbiter.
Solutions like using rc.local, bashrc and systemd all showed the same behaviour as autostarting with pm2 ... storing the settings of tallyarbiter was somehow not done using .local/share/TallyArbiter/config.json and the exitsting config.json was not used autostarting.
Finally i found the way using autostart / Desktop Entry ... this was working ...
sudo nano /home/pi/.config/autostart/tallyarbiter.desktop
... fill with:
[Desktop Entry]
Name=tallyarbiter
Exec=tallyarbiter
... save ... reboot ... and now tallyarbiter is starting on boot using the settings in .local/share/TallyAr…