HDMI out with coder

[shanepisko]

Howdo i get my Coder Pi to show video on HDMI out?

[mrutgerj]

If you mean displaying the desktop on HDMI out to a monitor, it should work out-of-the-box. Check your monitor settings, cables, etc.

[shanepisko]

i've got it displaying, but i'm at the really basic screen which just shows a "coder login:" and i dont seem to know the login name, i know the password.

What i'm trying to do is have a projector hooked up to the raspberry pi and use coder from a remote desktop to control what is shown to that projector. So i'm trying to understand how i can control the video out from coder.

[mrutgerj]

The username is "pi", but you have to set the password by going to "http://coder.local" first. Once that is done, try logging in.

Once logged in, you can run "sudo raspi-config". Enter the password for pi, it is configured as a superuser. A very basic configuration screen should appear. You can expand the filesystem, but you can also configure rasbian (the OS that coder is running on) to boot automatically to desktop.

[shanepisko]

Awesome, that's what I'm looking for thanks, I got to the config screen when I first set it up, but forgot to select it to boot to desktop.

Is there a documented way to get coder apps to output video to hdmi? Or display the coder app via the hdmi?

[darryllee]

I've been wondering about this myself - why not just plug the Pi into a monitor, hook up a keyboard and mouse and start coding on the same machine? To get the graphic environment to startup, just type startx once you're logged in. To have this happen by default, you could do:

% sudo raspi-config

then go to boot_behaviour and click enter.

One problem is I don't think the built-in browser is strong enough to handle all of the code that coder uses.

However, even after installing Chromium I'm having problems connecting to the server from itself, essentially. http://coder.local, as well as the usual suspects, localhost or 127.0.0.1 fail, and also, strangely the IP address that the box got assigned.

I can get to http://localhost:8080/ so clearly it's some odd node.js redirect/export thing.

So I'm digging into that.

To install Chromium, it's as simple as: %sudo apt-get update %sudo apt-get install chromium

Be patient though -- the Pi isn't the fastest box on the planet and the update/install can take a while. Get some coffee!

[darryllee]

Whoops this is already being talked about in https://github.com/googlecreativelab/coder/issues/3 "Bundle Chrome for local development"

[oschettler]

shanepisko, darryllee, I am working on an app to operate a RaspberryPi with a connected TFT touch screen. I have written a blog entry about my progress so far.

Now looking to switch to Coder, I have enabled the touch screen on top of the Coder image and started a bare bones browser in it.

Because Coder uses ip_tables to redirect ports 80 and 443 to ports 8080 and 8081, I have found that I need to open URL https://coder.local:8081/app/my_app locally. Also, I included my_app in the apps to launch without authentication in /home/coder/coder-dist/coder-base/server.js:

publicAllowed = ["auth", "my_app"];

[jmstriegel]

Excited to see how some of this will run on the new Raspberry Pi B 2! I'm finding the X environment to be a lot faster, so I'll see if there's a reasonable way to make some sort of HDMI output part of the next release.

[SpeakingOfBrad]

@oschettler Thank you! I have been trying to connect locally for a few hours now... I tried specifying both 80 and 443, but I didn't think to specify 8081. But it makes a lot of sense now.