- Run the install script again. The
pipcommand will check for a newer version and install it.-
bash ~/ipf-setup.sh
-
Note: Check the pip output to verify the new version is installed. If a newer version is available but it wasn't installed, see the section below: "Pip won't install the latest version of ipf?".
-
Stop any running workflows
-
bash ~/ipf/bin/wfm stop
-
-
Backup config files
-
bash ~/ipf/bin/save_configs.sh
-
-
Remove the install directory and script
-
rm -rf ~/ipf ~/ipf-setup.sh
-
-
Follow the Installation Guide again starting from the top
-
The backed up config files will have been restored. Generate the workflow files
-
bash ~/ipf/bin/configure_extmodules
-
-
Start the workflows
-
~/ipf/bin/wfm start
-
-
Check the published data
- See steps in Configure Software Modules Publishing
Yes! The configure_extmodules script will look for config files matching the
naming convention configure_extmodules*.conf. You can create multiple config
files and a workflow definition will be created for each one. Just make sure
that RESOURCE_NAME is unique in each config file.
- Backup workflow configs
-
bash ~/ipf/bin/save_configs.sh
-
This will do 2 things:
- make backup copies in
~/.config/ipf/ - create symlinks to the backup copies in the ipf install dir.
On a re-install, the IPF installer will look for any backed up config files and re-make the symlinks.
Two possible workarounds:
rm -rf ~/ipf/
OR
rm -rf /tmp/pip-build*
Then re-run the installer.
See also: https://stackoverflow.com/questions/14617136/why-is-pip-installing-an-old-version-of-my-package
~/ipf/.venv/bin/pip freeze