It seems that ./install.sh always enforces the blank project to be started, but it doesn't ensure that this project is actually still present. After deleting the blank project and running ./install.sh again will result in the webserver not starting up anymore.
Restoring openplc.db with git checkout HEAD -- webserver/openplc.db will make the system run again, though this will reset the user's settings, which is a pain when you have to enter slave device information again.
Steps to reproduce
Have a working OpenPLC install running a sample project:
Delete the unused Blank project:
Re-run ./install.sh (for example after git pull to update your runtime)
Description
It seems that
./install.shalways enforces the blank project to be started, but it doesn't ensure that this project is actually still present. After deleting the blank project and running./install.shagain will result in the webserver not starting up anymore.Restoring
openplc.dbwithgit checkout HEAD -- webserver/openplc.dbwill make the system run again, though this will reset the user's settings, which is a pain when you have to enter slave device information again.Steps to reproduce
Have a working OpenPLC install running a sample project:
Delete the unused Blank project:
Re-run
./install.sh(for example aftergit pullto update your runtime)Attempt to start runtime (after rebooting):