Hi there,
I'd like to simplify the processes of setup/provisioning and publishing content. I wonder how other people handle these workflows, especially when having a larger setup of players involved.
Background: We use a web folder setup, publish content to the folder from our network, and the players pull the content remotely. Most of the cases cover a 1:1 relation. So one folder per player.
Challenges:
Duplicate Name definition
The player name has to be specified in the setup, but can be overwritten by the provisioning / actual assignment of Player <> Setup. Organising content per player requires a setup for each player, only because of its name, that is anyway overwritten by the provisioning. The amount of setups can get messy.
Duplicate Web Folder URL definition
The URL is part of the setup, but has to be filled again in order to publish content. This can also lead into a misconfiguration. Publishing the wrong URL to a player requires a full reprovisioning that takes a couple of minutes to bring it back to its original value. And thinking of a scenario of live events, this is one of the worst cases we need to avoid.
Ideas and Questions:
1) Does anybody know a way to use the player name value as a variable in the web folder url? I'd like to have a generic setup, that is adopted by the provisioning, e.g. the player name is player123, the web folder url is https://example.com/webfolder/<playername>. By Provisioning the web folder url will be substituted with corresponding value of playername.
2) Why is the player configuation > url for web folder mandatory? It's a value that is present from the player's perspective.
Thanks & Best regards
Robin