Web Folder Mechanics

web folder was previously called simple file networking (sfn) in brightauthor\ connected and is still referred to as simple file networking in {{brightauthor classic}} this page describes how web folder publishing works in brightauthor\ connected and {{brightauthor classic}} the set of files/folders that the player will need in order to play the published presentation schedule is generated when the presentation is authored it includes a sync spec ( current sync xml or current sync json ), which is a manifest of the files and their download urls on the web folder server these urls are based on the url for web folder (that is, base url) set in the web folder parameters the user is expected to make the generated file/folder set available on the web server so the player can download them if you are transferring the files using your own ftp client or the brightauthor\ connected ftp client, binary transfer is required this is because the assets in the pool folder have no file extension, so some ftp clients will assume that they are 7 bit text and corrupt the files on upload 3 the player periodically downloads the sync spec from the web folder server at the url for web folder (that is, base url) with /current sync xml or /current sync json appended the downloaded spec does not immediately replace the sync spec currently in use the sync spec download interval and url for web folder (aka base url) are initially set on the player when it is configured for web folder usage, then is (re)set by the retrieved sync spec upon application of a new schedule if the sync spec retrieved from the web folder server does not match the sync spec currently in use, the current presentation continues to play while the player goes through the sync spec, downloading files that do not already exist on the player's storage once all files from the new sync spec are downloaded successfully (file size and file hashes must match what is specified in the sync spec), the player will activate the new presentation schedule it will only reboot if there is a new autorun or plugin script if the delay schedule change until current media completes playback option is enabled for the currently running presentation in main docid\ us hzc7pouideldtfckfj or presentation settings docid\ a6ali6u szxhuansk6t3 the schedule change and reboot will not occur until current video finishes the web folder server will be impacted as follows one sync spec download request per player at the configured update interval one sync spec download request when a player (re)boots storage is needed for published presentation content note that brightsign tools do not manage the server's storage, so old/unused content is not removed automatically the web folder should should be periodically cleared just before a new published file/folder set is copied in screenshot 2024 12 11 at 7 56 43 am png brightsign supports ftpes, the modern variant of secure ftp, but not sftp you can read more about these protocols here https //obambu com/guide/ftpes ftps and sftp key differences and characteristics/ server requirements your web folder server must support configured mime types (in addition to default html/javascript types) (no file extension) application/octet stream bsfw application/octet stream rok application/octet stream brs text/plain json application/json xml text/xml note that directory browsing on the server is not required because the player will directly download all files via the download urls in the sync spec