Create a ticket
Follow

Q100438: Creating a VPN Build for Flix 5

SUMMARY

Artists can use Flix from home or a remote location by running a special VPN/remote Flix build. This article describes how you can create such a build.
 

MORE INFORMATION

If you want to create a Flix 5 setup for your VPN users, we recommend that you contact us at support@foundry.com to schedule an appointment with us, so we can walk you through it.

If you want to create the Flix VPN build yourself, you can do so by following the steps below:

1. Create a directory called flix (anywhere you want) and copy your flixApp directory there. You will need to change some files to make this new location behave like a Flix VPN build.

2. In this new location find the file:

flix/flixApp/flixConfig/remote/localProcConfig.py

Inside the file, change all the procs to point to 127.0.0.1 except for the file services (those need to point to your Flix file servers). Also, make sure you have a resync service setup on port 35909.

3. You will need to update the config file which tells Flix where the Flix files are installed. We recommend C:\flix for windows and /Applications/flix for OSX (Darwin) The config file which needs to be updated is:

flix/flixApp/flixConfig/context/localContext.py

Add the line below to the localContext.py file above

self.fileService = 'flix.fileServices.fileMerge.FileMerge'

4.  Update the paths where Flix is installed on OSX in:

flix/flixApp/apps/osx/Flix_Variables.yml

and on Windows in:

flix/flixApp/apps/windows/Flix_Variables.yml

Also, make sure the below Nuke license server variables are set correctly within the 2 .yml files above.

FOUNDRY_LICENSE_FILE:
foundry_LICENSE: 
RLM_LICENSE:

5. Update the Flix.yml file (it will be in the same location where you start Flix from) to have the correct path to the Flix_Variables.yml file you just updated. Also, from here you'll configure all the Flix services to start. The ports need to match the services you're running locally from the flix/flixApp/flixConfig/remote/localProcConfig.py file. Flix.yml's command should look like:

commands:

        - '--port 35900 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug'

        - '--port 35905 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug'

        - '--port 35909 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug --resync'

        - '--port 35910 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug'

        - '--port 35911 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug'

        - '--port 35912 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug'

        - '--port 35921 --context "%(FLIX_RELEASE_CONTEXT)s" --noBrowser --debug'

        - '--port 35980 --context "%(FLIX_RELEASE_CONTEXT)s" --debug'
>

6. Create empty flixProjects and flixers directories at the same level as flixApp (inside the directory flix you created in step 1).

7. Delete the flix/flixApp/apps/linux directory, unless you'll have artists using Linux remotely connecting to your Flix server. This will save you about 1GB.

8. Zip up the flix directory and give it to your remote artists. They will need to download the zip file and unzip it to the location you configured in step 3. To start Flix the artists need to open their VPN connection and start Flix from the directory they just unzipped.

You are done.

You can test this setup at the studio as well. You need to unzip the zip file created in step 8 to the directory you specified in step 3, make sure Flix is not already running and start Flix from the newly created directory. Once Flix is running open:

The Flix Status page

and make sure all services (except for File) are running locally on 127.0.0.1.

Was this article helpful?
/

We're sorry to hear that!

Please tell us why.
0 out of 0 found this helpful

Comments