Download apache web server raspberry pi how to#
Download apache web server raspberry pi code#

You can see my client-side source code if you download the client, including the Raspberry Pi client. The client uses a sails.js client library to connect. It uses websockets with a node.js / electron client, and a sails.js server. I was looking for the same thing and I found the sails.js MVC framework. What would I use in the C++ server to establish the ssl connection? If anyone could point me at some information, I would greatly appreciate it.

Download apache web server raspberry pi how to#

I found an example that talks about using node.js on the client side, but it doesn't talk about how to configure the server. While I've been able to get websockets in general to work, I'm getting rather confused with how to make those websockets secure. The javascript communicates with a C++ program (with libwebsockets) on the Pi. My pi is running an Apache web server, and hosting a web page with some javascript in it. John123 wrote:I'm wondering if anyone has any background on creating a secure websocket on the Pi.

You will find a ton or articles and tutorials on doing this kind of stuff in node.js around the net. The express.js server module makes that easy. But I find it easier to drop all that Apache and PHP stuff and just create a small HTTPS server in node.js. You can run a node.js web socket server alongside you existing Apache setup if you like, on a different port number. You might like to look at the socket.io node.js module that makes it even easier. In general, if you want to use websockets then doing it with node.js is the easiest way to go. Including user sign up, login, logout etc. I was experimenting with all the things you need to do to make a web app secure. Sorry, my propanel experiment has a bunch of other code in there that is distracting.

The websocket JS code for the browser app is in propanel/app/components/terminal.jsx which is a text terminal that users can type into in their browser and talk with whatever the terminal websocket is connected to at the server end. The websocket server is propanel/server/websocket.jsx The secure web server in node.js is propanel/server/index.jsx I have an experimental web app including server and browser client communicating over websockets securely here: You only need look at the files https-server.js and https-client.js Together with instructions for creating the certificates. I have a very simple example of a secure web server and client using HTTPS in node.js here: Which means you will need keys and certificates. Of course for security that web server will be using HTTPS instead of HTTP. Basically ensuring the connection stays open and bytes can be exchanged in either direction at any time. That request contains a header that tells the server to 'upgrade' the connection to a web socket. What happens is that as web socket client makes an HTTP request to the server. So a web socket server is basically a WEB server.