In modern versions (since Mistika v8.10), the Mistika  folder structure is designed to be easily shared between multiple systems). If you plan to do that then please read this article carefully before configuring it, as it is easy to miss some  implications:

Mistika has many configuration files in different folders, which we can be divided in two categories:

Settings and configuration files that are useful to share between all systems

This includes things like the mConfig presets, render presets, render targets, display filters, user settings (hotkeys ...), LUTS,  DCP keys, etc.

All the shareable files are initially stored in the SGO AppData/shared folder (which is a normal folder on Windows and Mac, but a unix link on linux systems). These files are not part of the Mistika software structure and they are neither related to the local hardware, so they can be safely shared between systems. 

Logically, on first installation each system will have its own copy of this folder, so it needs to be moved under a common place in the network in order to share it with more systems.

For the case of Mistika Boutique and Mistika Ultima this must be done with  mConfig->FilePaths->Set shared settings folder:  

The common shared folder  does not need to have any specific name, you can put any name you prefer as long as you select it later in the MistikaConfig tool. The only critical point is that the shared folder needs to be always available to all systems, not in a local folder of any of them (as if that system goes down all others will lose it). So it should be located in a reliable network drive.

When you select a custom shared folder for the first time (an empty folder), all the content of the local shared folder will be copied to it. But no files are overwritten in any case, and when adding more systems they will simply use what is in there and they will only copy missing files (if any).

Note for system administrators: The paths to the shared folder, projects folder, media folder, and other definable paths are stored in this xml file:

Mistika versions before 10.5: SGO Apps/installation.xml 


Mistika versions since 10.5:  

- Windows:  User_Home_Folder/AppData/Local/sgoMistika/mistikaPaths.xml

- Linux/Mac: User_Home_Folder/.sgoMistika/mistikaPaths.xml 

Settings and configuration files that must be local to each system

These files are located under SGO Apps and under SGO AppData/Mistika  (or in the case of linux  where those links are pointing to), and these folders should never be shared between different systems

This is because they are specifically configured for to the local hardware at installation time, with several aspects depending on the OS version,  RAM, CPUs, attached color panels, video board model, and many other things that can be different between the systems.  

In the particular case of Mistika Ultima and Mistika Boutique most of these settings are kept in the SGO AppData/mistikarc.cfg file, but some others are in other sub directories.

Note: A full description of all the Mistika folders is maintained in this document

Sharing media files

Please note that all this only applies to user setting files. If you also want to share media files in different computers using different mount points please read this other article 

Linux only (Mistika Ultima):

- On Linux it is also possible to have multiple Mistika versions installed in a same system at the same time, and then switch to a particular version at user request. (this is not possible on Mac and Windows)

Each Mistika Ultima version that is installed is located in these folders:

$HOME/SGO Apps/Mistika Ultima/Mistika ultima.VersionName (Mistika software)

$HOME/SGO AppData/Mistika/Mistika.VersionName (Configuration files for the local system and 3rd party files)

-  All the versions installed in a same system are inactive except one, which is defined by these unix links (same paths without version name extension)

$HOME/SGO Apps/Mistika Ultima/Mistika ultima 

$HOME/SGO AppData/Mistika/Mistika.VersionName 

Mistika knows what version is active by following that links. To change the active version easily just use the mConfig->VersionManager, which will offer all installed versions and it will change said links for you.

NOTE: In general  old projects can be loaded in more modern versions and work fine on them, but logically old versions will not properly understand files that are saved with more modern versions.