In modern versions, the Mistika Ultima folder structure is designed to be easily shared between multiple versions and multipe systems. Please read this article carefully before configuring it, as some aspects have more implications that it seems:


- Each Mistika Ultima version that is installed is located in the $HOME/MISTIKA-ENV.VersionName , and it is installed independently on each system. 


-  All the versions installed in a same system are inactive except one, which is defined by this unix link $HOME/MISTIKA-ENV


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


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


Settings and files that are useful to share between all systems and all Mistika versions


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


All the shared files are initially stored in the $HOME/MISTIKA-SHARED folder, so they are not part of the MISTIKA-ENV.VersionName structure, so they can be shared between all versions. You may also notice that there is also a link MISTIKA-ENV/shared pointing to the shared folder, but the folder itself is always kept out of the MISTIKA-ENV structure in order to make it version independent and shareable between systems.


However, on first installation the $HOME/MISTIKA-SHARED folder is still local to each system, so it needs to be placed in a common place in the network or a network drive in order to share it with more systems. 


This must be done with  mConfig->FilePaths->Set shared settings folder.  Apart from that, the common shared folder name does not need to be MISTIKA-SHARED at all, you can put any name you prefer,  but the only critical thing is that it 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).  This tool will save an internal variable telling mistika where to find the shared folders. And it will also change the MISTIKA-ENV/VersionName/shared link pointing to the new place. This link is not what Mistika uses (it uses an internal variable) but the link is also necessary for backward compatibility of external scrips.


Settings and configuration files that must be local to each system


These are located under MISTIKA-ENV  (or better said in the MISTIKA-ENV .VersionName folder where it points 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. Manyof these settings are kept in the MISTIKA-ENV/mistikarc.cfg file, but many others are in other subdirectories of MISTIKA-ENV.


Important Note:  If you plan to write management scripts for those folders please be warned that these structures are only valid up to Mistika Ultima 8.7, they are planned to change in 8.8 version in order to accommodate newer Mistika products like Mistika VR and Mistika Review in a common structure.  


Important Note:  Old versions from several years ago didn't had the shared files separated, so it was a common practice to manually create multiple links to common places here and there. This is now a bad habit and not recommended, as those links may fail to survive during upgrades. If you had a link heritage like this we recommend to backup your shared settings, remove the MISTIKA-ENV link and make  a clean installation with the latest version. If the MISTIKA-ENV link does not exist then the installer will use the default structures, which is a clean way to start the configuration.  Once installed, you can simply use the mConfig->Set Shared settings folder to establish a shared folder in the SAN or Network, and finally recover your backup and place its contents on that folder