b0b_z wrote:Local Host
PI runs localhost at 127.0.1.1 and Screenly at 127.0.0.1
Is there a reason for this...?
Can they be the same IF I wanted to host files locally?
127.0.0.1 is localhost. That's has pretty much been that way forever. That's the IP that the loopback-interface (lo0) binds by default. You could change this, but it would probably break some system services.
I checked on my of my nodes and it appears as Debian/Raspbian adds an entry in /etc/hosts for 127.0.1.1 that maps to the hostname (default 'raspberrypi'), so maybe you got them mixed up.
Generally speaking though, I'd strongly
advise against serving content from
the Raspberry Pi. If you were to fire up a web-server on the Raspberry Pi, it will most likely have severe negative impact on Screenly's performance. The resources are already stretched as it is. If you don't have a server on your network, just use Dropbox's public folder and serve it from there (or better yet get a cheap hosting service).
theoretically serve content from the Raspberry Pi. Screenly's admin interface binds on 127.0.0.1:8080, and HTTP is usually served on port 80, which is not being used by Screenly. Just install Nginx or Lighttpd and have it serve content from port 80 and you should be good, but again, I'd strongly advise against this.
Creator of Screenly (Screenly.io), the leading digital signage solution for the Raspberry Pi. Now hacking on WoTT (github.com/WoTTsecurity/agent),
Twitter: @vpetersson | vpetersson.com