Updating raspiCamSrv

Before updating, make sure that

• video recording is stopped
• there are no active photoseries
• triggered capture (motion tracking) is stopped
• server will not start with stored configuration

It is recommended configuring Versatile Buttons for the commands described in the following, so that update and server restart can be initiated directly from the Web UI.

For update, proceed as follows:
(If running a Docker container see Update Procedure for Docker Container)

1. Within a SSH session go to the raspiCamSrv root directory
   cd ~/prg/raspi-cam-srv
2. If you have made local changes (e.g. logging), you may need to reset the workspace with
   git reset --hard
3. If you have created unversioned files, you may need to clean the workspace with
   git clean -fd
4. Use git pull to update to the latest version
   (normally you need to pull only the main branch)
   git pull origin main
   As a result, you will see a summary of changes with respect to the previously installed version.
5. Restart the service, depending on how the service was installed
   sudo systemctl restart raspiCamSrv.service
   or
   systemctl --user restart raspiCamSrv.service
6. Check that the service started correctly
   sudo journalctl -e
   or
   journalctl --user -e
7. If you used start with stored configuration before updating, you may now try to activate this again.
   In cases where configuration parameters were not modified with the update, this will usually work.
   If not, you will need to prepare and store your preferred configuration again.

In case that the server did not start correctly or if you see an unexpected behavior in the UI, you may have forgotten to deactivate start with stored configuration
In this case, you can do the following:

• cd ~/prg/raspi-cam-srv/raspiCamSrv/static/config
• Check whether a file _loadConfigOnStart.txt exists in this folder.
• If it exists, remove it:
  rm _loadConfigOnStart.txt
• Then repeat step 4, above