One of the major differences between ecFlowUI version 4 and 5 is that they can only interact with servers of the same major version. As a side effect if you start up ecFlowUI version 5 you will not be able to interact with any of your version 4 servers and vice versa.
As a temporary solution, for the migration period between version 4 and 5, we recommend to use the -confd command line option. With this option you can define a custom configuration directory for ecFlowUI and can keep the version 4 and 5 servers separated.
This is one possible way of how it could be used:
- start version 4 with
| Code Block |
|---|
ecflow_ui |
this will use the default configuration directory in ${HOME}/.ecflow_ui
- start version 5 with
| Code Block |
|---|
ecflow_ui -confd path_to_your_version5_config_dir |
...
To help the clear separation of ecFlow4 and ecflow5 related settings, from version 5.2.3 ecFlowUI will use a new configuration directory. As a consequence, you can create a separate server list for ecFlowUI 4 and 5.
You do not need to do anything, when you first start up ecFlowUI with a version >= 5.2.3 the new configuration directory will be automatically created for you by copying the contents of the old configuration directory.