I posted a while back about a client-side set-up feature (this would enable deployment as a private channel and would no longer require developer-mode). Well, today I accidentally discovered that client-side set-up is already possible. Here is what I did.
(1) When I installed from Springboard, I intentionally entered my server IP incorrectly. (XXX.XXX.XXX.101 instead of XXX.XXX.XXX.100).
(2) When I started the Channel I received an error message and a was given the option of manually entering the correct server IP.
(3) It still didn't work yet. When I pointed my browser to localhost:8001, I noticed that the server settings still incorporated the XXX.XXX.XXX.101.
(4) Given that not understanding what the hell I am doing never stopped me from messing around, I manually edited the server/config file to reflect the correct server IP.
(5) Rebooted my computer. Ran the server. Restarted the channel. And everything works.
The point is that this channel almost as is can be deployed as a private channel, with the client pointing to a standard default server IP. It doesn't matter whether the server IP is correct, because you can manually edit the settings directly on the Roku. I thought I'd throw this out there and let those smarter than me figure out what to do with it. Thoughts?
