Tech Support Posted May 20, 2020 Share Posted May 20, 2020 Using KVS as a primary content manager for multiple frontends via embed codes If you have or plan a network of multiple sites that use other frontend engine, for example Wordpress, you can still benefit from KVS super powerful video management features by using KVS as you primary content manager and delivering content via KVS embed codes. You can also use this scenario with other KVS licenses (typically Basic), but the key point here is that you don't necessary need to install KVS on every site of your network, you can just use it as your primary solution. Pros: Best way to use KVS with other scripts! Content can be shared or divided between sites, no duplicate files. Single place to manage all your content storage and streaming in one, unified way. Can use ALL KVS video content management features, including multiserver, timeline screenshots, grabbers, multiformats (KVS Advanced+). Can use ALL KVS player features, player advertising and stats. Can show related videos generated by KVS inside player. Can use KVS exporting feeds (KVS Ultimate) to automate content delivery to your other sites, if they support import from feeds. Can configure individual player settings + advertising for each site using KVS embed player profiles. Can have unique titles, screenshots, comments, rating and popularity across the network. Cons: Should use iframes to deliver video player, but domains are overridden. Requires some advanced server configuration to configure aliases (see below). Requires purchasing KVS open source code option for using aliases. Price: $$$ of KVS license of your choice + open source code option ($299) + alias license for every new domain in the network ($1-$50 depending on the amount). Typically no more than $1000 for all your network if you are using Wordpress or other free software for your network sites. From the other hand you get most of killing KVS features and scale them to your network. The idea behind this scenario is that you will need to hide the domain where KVS is installed and instead use embed codes from subdomains of you other project domains. Here is an example of typical KVS embed code, where kvs-demo.com is the primary domain of your KVS installation: <iframe width="854" height="480" src="https://kvs-demo.com/embed/123" frameborder="0" allowfullscreen></iframe> If you want to embed its videos on domain2.com, you will need to create subdomain video.domain2.com that is configured as alias for kvs-demo.com. Then you can use embed codes using this subdomain: <iframe width="854" height="480" src="https://video.domain2.com/embed/123" frameborder="0" allowfullscreen></iframe> In KVS admin panel Settings -> Embed player settings you will need to create a new embed player profile for domain2.com domain. This profile will let you configuring individual player settings for all videos that are played on domain2.com. Using KVS as a primary content manager for multiple frontends via hotlinks This option is similar to the previous one, but instead of using embed iframes you can hotlink video files stored in KVS from other projects. This can also work with both KVS and other scripts, but this approach has less advantages, especially for non-KVS network. Pros: No iframe usage. Content can be shared or divided between sites, no duplicate files. Can use SOME of KVS video content management features, including multiserver, grabbers. Can use KVS exporting feeds (KVS Ultimate) to automate content delivery to your other sites. Can have unique titles, screenshots, comments, rating and popularity across the network. Cons: No multiformats is possible. No timeline screenshots. With non-KVS frontends you can't use KVS player or advertising features. Limited content migration: hotlinked content will stop working if migrated to another storage group. Video files are hotlinked from primary domain and there is no way to hide or replace it. Price: $$$ of KVS license of your choice + $$$ of other network sites either KVS or other script. Typically network KVS sites are KVS Basic licenses in this case. Using KVS satellites to build network sites KVS satellites are special license types that try to combine benefits from both having separate projects and sharing the same set or subset of content from one big database. Satellites are different from other KVS projects that they are connecting to the same database as your primary KVS does, and they are using database data directly. If you want to use KVS for all your network sites, then satellites are probably the best scheme for you. Pros: Best way to use KVS with KVS! Content can be shared or divided between sites, no duplicate files. Single place to manage all your content storage and streaming in one, unified way. Can use ALL KVS video content management, player and advertising features without any limitations. Can have unique titles and descriptions across the network (KVS Ultimate). No need to configure feeds to sync content. All content is managed from the same admin panel for all network. Cons: Requires some advanced KVS configuration to divide content between satellites if you don't want to automatically show all content from the primary database. This is typically configured by our tech support. Requires some advanced server configuration if satellites should be hosted on remote servers. Many satellites can result in database overload for big databases. Can't have unique screenshots, comments, rating and popularity across the network. Shares the same members database for all sites. Price: $$$ of KVS Ultimate license + KVS Satellite license for each network site ($99 - $249 depending on the amount). 1 1 1 1 1 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.