I tend to agree with Kevin. in fact after a significant amount of persistence I have a Raspberry PI 3 with Raspbian Jessie running Concerto 2 as both a server and player very nicely indeed.
I had already used the RPI 2 to run as a LAMP stack running Drupal 7 websites, and already used RPI 2 extensively with Kodi. Amazing what you can make them do. I generally start out by moving the root file system over to a USB 3.0 Nano Stick. So the Micro-SD just has the FAT boot partition on it, and boots it into the Linux file system on the USB. Although the PI is only USB 2.0, using a USB 3.0 stick means the PIs own USB hub is the slowest interface and I am pretty sure it gives me better read/write speeds than running from the Micro-SD. Regardless of the speed benefits, this greatly negates the issue of the limited lifetime of SD cards, where USB tends to have a much longer life with constant read/write activity.
It took a number of goes at it to get all the components for Concerto going. Ended up having to install from source with a compiled version of Ruby 2.2.2 . Eventually got the full gem bundle to install without errors and then managed to get it running solid in rails production mode.
I can then drop another folder into the Concerto public folder which I called "uploads" (or you can setup another virtual host on another port in Apache). Then you just drop video files into one of those locations where they can be called locally via http, and you can use the Concerto 2 backend functionality to set your video file URLs. But instead of having the video delivered over the internet it is getting played direct from the local storage (in my case from USB) which the RPI3 handle no problem. So for applications where I mainly just want rotating images and video I can do it all from a single RPI 3.
I am then using a startup script to boot directly into Iceweasel (Firefox esr) with the R-Kiosk addon as the frontend player. So it boots directly to fullscreen player and runs fading images and video beautifully. Using the R-Kiosk addon forces Firefox to only be usable in fullscreen mode, but I can either just ALT-F4 to kill it and then use Chromium or Epiphany to call the backend interface.
More practically I can leave the PI running the Firefox kiosk frontend player while I bring up the Concerto backend URL in a browser on a different machine on my network. Or with XRDP installed I can remote desktop to the PI as a different user session, and manage the backend that way without disturbing the frontend player on its HDML output.
I have then also created a symlink from my "uploads" folder in /concerto/public to a sub-folder of /home/user/ and then samba shared this folder on my network. So I have this shared folder mapped on my network on another machine, where I can just drop new video files straight into position, and then load them up via the Concerto backend.
I have also just been playing with running a Drupal 7 as another virtual host on a different port. Where I can then call pages from the local Drupal in with custom theme layouts, or load content nodes into the Drupal and pull it through to Concerto as a local RSS feed. Running the Drupal as well doesn’t seem to hurt as the only additional load it is putting on the PI is the calls being made from Concerto. So it is very minimal extra load considering I already had Apache2, PHP and Mysql running anyway.
I only have one remaining significant issue as I see it... Due to the rails/passenger architecture, Concerto still requires an internet connection at boot up for it to startup properly. I actually see this as Concerto's one achilles heal, as the primary goal for any signage display is to minimise any downtime, and reality is that internet dropouts can and do happen. Although Concerto's broader spectrum of functionality requires internet anyway, in this instance where I can be delivering all content locally, it would be nice if it could boot up and start without needing the active internet connection. This would make it even more viable when used with a cellular modem/router where the internet might not be so reliable but where you are just using the internet for backend admin functions.
I have thrashed away at finding a solution to offline boot up, but cannot get it to work yet. It's a Passenger Net:HTTP issue that plagues me. Its not the biggest problem needing internet, but it would greatly reduce the chances of display downtime. If anyone knows how to get Concerto 2 to boot up offline I would be eternally grateful for your wisdom.