The entire Master Server currently runs as a single application. This causes problems if, for example, a last-minute scoreboard change is needed and we can’t restart just the scoreboard application because it might disturb the apps managing the database, stations, or phones.
Specifically, we were hesitant to restart the apache2 service during the middle of the competition since it would momentarily take down the Master Server completely.
It would help to pull out the Scoreboard app and run it separately so it alone can be restarted if necessary. Not sure if it’s worth separating dbkeeper and piservice.
The entire Master Server currently runs as a single application. This causes problems if, for example, a last-minute scoreboard change is needed and we can’t restart just the scoreboard application because it might disturb the apps managing the database, stations, or phones.
Specifically, we were hesitant to restart the apache2 service during the middle of the competition since it would momentarily take down the Master Server completely.
It would help to pull out the Scoreboard app and run it separately so it alone can be restarted if necessary. Not sure if it’s worth separating dbkeeper and piservice.