As covered in the Provisioning page (part of the Start Here section which is encouraged reading for those new to BrightSign), player provisioning consists of 1) applying a Setup to the player, and 2) installing a Player App onto the player.
The Player App is the collective set of files and folders that provides the player with specific instructions for what to do upon startup. At a minimum, it must contain an autorun, or more specifically, an autorun.brs file (the .brs extension denotes a BrightScript file). The autorun may, for example, instruct the player to display a specific .html file which can be either local on the player or reside on an external website. Alternatively, the autorun may instruct the player to check a particular URL for updated presentations and/or content and, if new files are available, download them and play them.
There are three autorun-related files which unfortunately have similar-sounding names:
autorun.brs (may also be referred to as “the autorun” or “autorun file”)
autorun.zip
autozip.brs
While the naming convention is admittedly confusing, each term has a different function so it’s important to not conflate the terms.
Upon bootup, the player searches for certain autorun files. The player’s search follows a prescribed sequence as shown below.
...
As mentioned in the Player Storage section, the player will search for storage devices in a predefined order.
...