...
| Warning |
|---|
This will require at least ecFlowversion 5.7.0. Some Some advanced features are only available in version 5.9.0, but it is not yet released and only available from git as the develop branch. |
| Tip |
|---|
You can install ecFlowUI on MacOS platforms using Brew, or the full ecFlow from conda-forge. |
Dynamic port forwarding
Authenticate via teleport
...
ecFlowUI accesses certain local files (e.g. output and server logs in the Output, Timeline and Server Load panels) directly (standard file I/O) without using the ecFlow client-server communication. This poses a limitation if we run it via proxychains because these files are only local on the remote hosts so ecFlowUI cannot access them. To overcome this difficulty you need to use ecFlowUI version >= 5.9.0 and file fetching will automatically work for you. The only settings that you might need to change is the SOCKS port number, which by default is assumed to be 9050. Should you set up dynamic port forwarding and use proxychains with a different port number you need to set it in Tools→ Configure→Network Tools > Preferences > Network:
System server lists via proxychains (only in version >= 5.9.0)
...
Alternatively, you can use the ECFLOW_SYSTEM_SERVERS_LIST environment variable to specify the very same paths.TODO: explain to to figure out the current paths used e.g. on ATOS
| Note |
|---|
The path to the system server list files for ATOS can be found here. |
Comments
- the dynamic port forwarding sometimes stops/hangs and as a result ecFlowUI loses connection to the servers (it is indicated by the orange strip on the left and the dotted background):
If it happens just go to the terminal where the dynamic port forwarding was started up, terminate it if it still running and run the command again. You do not need to exit ecflowUI, just refresh the servers and the connection will be re-established.
...