What WEB Server is running on the BBB out of the box?

The example code pasted above is close to what you need. Personally I start up a separate instance using node, and have it listen on a different port. That way I don't need to touch the existing code and can start from a clean slate.

If you want to see an example of that, see this code. You'll see in the index.js file what I did to provide web server capability (but on a different port, 8081 in my case).

If you want to modify the existing server, that should be possible, but I've not had a need to attempt it so far.

EDIT: edited to add a more direct link.

Cool.  More her than my simple needs to spit out my own web page.

How did you associate your code with http://xx.xx.xx.xx:8081/index.html

Did the "npm install socket.io" command set up the path to your files at 8081?

I see you changed your link.  I was lucky enough to see the original to:

Building a Frequency Synthesiser

The new link takes me to the code directly but deprives everyone from seeing your really cool project.

Hi Mark,

The index.js file uses an 'app.listen(8081)' command to set that (unlike a web server like Apache, there is no config files and all behavior has to be programmed, in this case it is programmed in the index.js file). You won't need the socket.io stuff, just lines 1-33 of the code should work fine (you can delete line 4). Also, delete line 21 which forces all requests in my case to always respond with a single file index.html.

With those changes, the code should be close to what you need.

Thanks Shabaz,

I'll play with a smaller version of this and see what I can come up with.  Thanks for all the help.

Hi Mark,

No problem, let us know if it works out.

Here is a good intro to some node packages that serve up static content

http://www.sitepoint.com/serving-static-files-with-node-js/

Mike

Well it took way too long, but I finally found the files.

I guess most of the Linux users here are thinking, "Yeah. Duhh.  What took you so long"? Not being too familiar with either Linux or HTML, it was a challenge for me.  Anyway to finish the thread, they're here:

root@beaglebone:/usr/share/bone101/Support#

ls

BoneScript  bone101

The various WEB pages aren't as "flat" as I had expected.  Files are spread out in the various sub folders depending on where you are going on the WEB page.

Thanks Michael, that's exactly what I was looking for.  I wonder why those are left to a third party, not given as obvious examples in the docs.

selsinork wrote:

 

Thanks Michael, that's exactly what I was looking for.  I wonder why those are left to a third party, not given as obvious examples in the docs.

You mean in the node.js docs? I don't know why. It does seem like it would be helpful to point out a more sophisticated implementation. Of course it's possible that at the time the docs were written they hadn't quite figured out a good way to serve static content, and by the time they figured it out, third party implementations were available.

Mike