Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Table

The table contains the PTR – you only have to fill in the columns you really need: if the network contains, for example, only Windows machines “Linux” and “Mac” remain empty.

Add Row

You can add as many PTRs as required. RealFlow always tries to find a matching rule from the existing PTRs and ignores invalid rules.

Example A

This is the configuration:

  • The project is located on a Windows computer on the D:/ drive

  • The D:/ drive's network name is “Data

 
  • , named Data

  • On Linux the Data drive is mounted as /mnt/Data/

  • On macOS the Data drive is mounted as /Volumes/Data

Here are all possible PTRs for different operating systems, but and you only have to use the ones valid for your operating system(s):

 

 

PrefixD:/
Linux/mnt/Data/
WindowsD:/
macOS

/Volumes/Data/

 

Example B

To access a project on an macOS computer we recommend mounting the Mac volumes as network drives. In Windows you can assign a letter to a network drive and this makes PTRs really easy.

  • The project is located on a macOS computer under /Volumes/Data/

  • Let's assume the “Data” drive's network letter is X:/ on Windows.On Windows, the Data drive is mounted as X:/

  • On Linux the Data drive is mounted as /mnt/Data/

Here are all possible PTRs for different operating systems, but and you only have to use the ones valid for your operating system(s):

 

Prefix/Volumes/Data/
Linux/mnt/Data/
WindowsX:/
OS XmacOS/Volumes/Data/

Example C

Finally, the Linux route:

  • The project is located on a Linux computer under /mnt/Data/

  • On Windows, the Datadrive is mounted as Y:X:/

  • On macOS the Data drive is mounted as /Volumes/Data/

Here are all possible PTRs for different operating systems, but and you only have to use the ones valid for your operating system(s):

 

Prefix/mnt/Data/
Linux/mnt/Data/
WindowsYX:/
OS X/Volumes/Data/