Share workspace between two PCs

I am new to KNIME and could not find anything on how to share a workspace. If the question has been answered please point me to the answer.

I have two PCs and would like to use KNIME on both. What’s the proper way to share the workspace between two PCs?

*

Should I put it on a NAS? Probably bad since temp files are also stored in the workspace and my local NVME is much faster than a NAS drive.

*

Can I use a tool like Syncthing to sync the NAS between the PCs? Syncthing allows to exclude different files and folders so I could exclude the temporary data.

Another related question: can I use git for versioning of the workspace?

I found the following topics, but not really solved the issue:

Hey Julian, Thanks for the replies, I apologize for my delayed response. Figured I’d update here in case this is helpful for anyone else. I have been using git and GitHub successfully for version control of my KNIME workflows! The way I have been doing it is to go to my command line and add the workflow folder, because each individual node is stored as a folder within that workflow folder, and git add on the workflow folder adds, deletes, or updates all the nodes that have changes. I have mult…

Hi, it’s possibile to use a share workflow with version control (i.e. github) for work in a team on the same project?

Hi, is it posible to dicretly sync ones workspace with a git repository within KNIME or to add an own server repository like the one with the workflow examples? Best regards Jürgen

this one point to another question which is no longer available.

For those interested: I'm currently using a .gitignore file (see below), and commandline git. I tried to re-open workflows that were restored using just the files in the git repository, and KNIME never complained, so this seems to indicate that all the necessary information is backed up to git. here's the contents of my .gitignore ## KNIME files .knimeLock .project .savedWithData workflowset.meta ## KNIME directories containing node data internal/ port_*/ .metadata/ internalTables/ # Pac…

this one seems to have kind of a solution, but the answer is 7 years old.