Hd Flix Pro

[Kapil Grunewald]

TheMySQL database doesn't need to be running on the same machine as the Flix Server. However, it must accept external connections over a network to allow for communication with your Flix Server(s). Refer to this Knowledge Base article for more information.

You need to set up a config.yml file before you can run Flix Server. By default, Flix Server reads the config file from the same directory as its binary file (flix_server). In order to make upgrading to future versions of Flix easier, we strongly recommend storing the config file in a different location and pointing to it when running Flix Server using the --config-file CLI argument.

You will then need to point all of your Flix Servers to use the license floating from your Foundry License Server by setting the floating_license_hostname and floating_license_port config options.

You have now completed the minimum steps for setting up Flix Server. The following instructions guide you through more advanced set up options. If you want to return to these custom options later, you can jump to Running Flix Server.

By default, your Flix assets are stored in an 'assets' directory, which is located in your install folder alongside the flix_server binary. We strongly recommend that you change this to a custom location, to make the upgrading process easier for all future releases of Flix. To do this, set the asset_directory option in your config.yml file. For example:

Flix can be configured to store assets on shared storage, accessible by all servers. This way assets aren't siloed across multiple servers. To switch to shared storage, add the shared_storage setting into the config.yml file.

By default, under the assets directory, each server will have its own directory specified by the server identification number (a long string of numbers/characters) where it stores its own assets. If you want all the servers to store assets in a shared directory, set the shared_storage option to true. Every Flix Server stores the assets in the same directory specified by the asset_directory folder.

The OAuth configuration allows users to log in to Flix using their credentials provided by an OAuth service. Using the example below, configure your Flix server config file to use OAuth. Once the configuration is enabled, restart your Flix Server, and users should now be able to log in using the Sign In with Google button.

username - This determines whether artists are authenticated by 'username' or 'email' address and is used to create their Flix username. Setting the username parameter to email forces Flix to create unique usernames.

Making use of integrated cloud platform features such as auto-scaling and load balancing can be challenging, because Flix Clients require direct access to all Flix Servers to run effectively. Flix supports reverse proxy servers to simplify this process, which are commonly used intermediary servers that manage requests for resources across the internet. Using a reverse proxy server allows you to customize the connections between Flix Clients and Flix Servers to fit your needs, including:

Load Balancing - distribute Flix Client requests across the available Flix Servers to maximize efficiency and avoid any one server being overloaded. Without load balancing, all Flix Client asset requests in your studio might be directed to a single Flix Server despite there being more servers available to handle requests.

Flix includes a health check to determine if a server is "healthy" and ready to handle remote procedural calls (RPCs) and then the reverse proxy server can act accordingly. For example, if one Flix Server reports as unhealthy, the remote proxy server can redirect Flix Client RPC requests to another available server.

disable_hostname_check boolean [default: false] - If set to true, Flix Server does not check that the host header requested by the Flix Client matches the hostname of the server. This can be used for reverse proxy setups where the reverse proxy's public URL does not match the Flix Server's hostname.

skip_transfer_tls boolean [default: false] - If set to true, Flix Server listens for insecure (non-TLS) RPC connections. This can be used for reverse proxy setups where the reverse proxy terminates the TLS connection (grpcs://) from the Flix Client and uses an insecure connection upstream to the Flix Server.

As mentioned above, we strongly recommend storing the server config file outside the Flix Server directory. To point Flix Server to the location of the server config file, use the --config-file CLI flag. For example:

Now that Flix Server is running, it's a good idea to ensure it's accessible by other computers, as end users only access it from another computer at the studio (on the same network), or remotely (over VPN).

Tip: Depending on the size of your Flix user base, a single server may not be enough to provide satisfactory performance and speed. Having multiple servers in your Flix Deployment helps ensure better performance across all users, with HTTP(S) requests being spread across all the available resources. For more information on adding another server to your Flix Deployment, see Adding Servers.

Can't find what you're looking for? Use our feedback widget on the right to request more information.

You must accept cookies from learn.foundry.com and disable any ad-blockers to provide feedback.

Once upon a time, there was a man who hid Mother's Cookies Flaky Flix Cookies on the highest shelf of a hard-to-reach cabinet. He hid them there to keep anyone else from eating them. They were his special treat. His son, being quite clever, maneuvered a way to climb on top of the counter and reach to the top of this hard-to-reach cabinet's highest shelf so he could steal a few cookies for himself. The Flaky Flix, with it's inner crunchy wafer cookie covered in rich chocolate and topped with crisp corn flake crumbs, was also this boy's favorite cookie.

Several years later, in an entirely different household, there was a woman who hid Flaky Flix cookies in her sewing basket which she kept right next to her recliner in the living room. She covered them up with cloth and spools of thread in hopes that no one would find her secret little treat. Her daughter, however, was quick to find all of her mother's "stashes" and this one was no exception. While her mother was in the shower or taking a nap, she would very sneakily snatch a few of the tasty cookies for herself and enjoy every last crunchy, chocolatey bite while hiding in her bedroom.

For both children, years went on and different treats became their favorites, though they both always had a soft spot for the delicious cookies they had to steal from their parents' secret hiding spots.

Then one day, this boy met this girl. They went on one date and then another and another. They got to know each other, though at first it was the basics- how many siblings did they have (the boy had two, the girl had one), who their favorite band was (both agreed on The Beatles), what their favorite animal was (both agreed on dogs), what their favorite drink was (the girl preferred a nice glass of red wine and the boy loved kombucha), and what their favorite movie was (the boy loved "The Graduate" and the girl loved "Ferris Bueller's Day Off"). Then as months went on, they got to know each other even more- which way they preferred the toilet paper to be loaded (both agreed that "over" was the best way), what foods they always kept stored in their refrigerators (the girl always had hummus and baby carrots and the boy always had pickles and peanuts), and what position they each slept in (the boy was on his side and the girl was on her stomach). Their favorite childhood cookie never came up.

Late one evening, while driving home from a long road trip, the boy and the girl began to exchange their favorite childhood stories in an effort to stay awake. The girl mentioned how she used to steal cookies from her mother's sewing basket but she couldn't remember what they were. "Chocolate-covered wafer cookies of some sort." The boy was reminded of how he used to do the same thing and told her the story. "And they were chocolate wafer cookies too! Flaky Flix!"

"Yes! Flaky Flix! That's what they were called!" the girl exclaimed. The boy took the next exit off the freeway, though they were still about an hour away from home, and parked in front of the first grocery store he saw. The girl didn't even have to ask the boy what he was doing- she knew. They both ran into the store and looked frantically for the cookie aisle. Once they found it, they both stood silently, their eyes searching the shelves for the familiar brown package. There were no Flaky Flix to be found. They got back in the car and drove a few more miles to the next exit to try a different store. Again, they had no luck but they repeated the process at several more stores along the way home.

Over the next few weeks, whenever they boy or the girl were in a grocery store (or even just near a grocery store), they would search for Flaky Flix. There were none to be found. Mother's Cookies had gone bankrupt and had been bought by Kellogg's, though neither the boy or the girl realized that this had happened- they had long ago stopped buying cookies from the grocery store and neither paid all that much attention to the news. Even after the boy and girl learned of this, every once in awhile they would still search the cookie shelves at the grocery store for one last package that may have been left behind. After a couple years of unfruitful searching, they gave up.

The boy and girl eventually got married and then shortly after they became vegan. Their fond talks of Flaky Flix turned to fondly remembering how they used to stalk the cookie aisle of every grocery store they went into. They would talk about how it was "their thing" and how that "obsession" was one of the many things that brought them closer together. They would laugh about how alike they were, how they were almost the same person, long before they had even met. Then, for their second wedding anniversary, the girl made vegan Flaky Flix cookies so they could enjoy them together for the first time. The cookies were incredible. The texture was slightly different but all of the flavors were there and the fact that the boy and the girl were finally able to share them together made it absolutely perfect.

3a8082e126