I know what you're thinking--why would you want to use Oracle for your node backend when you have perfectly good options like mongo and the like? You know the old saying: "When in Rome, etc.". The business enterprise is quite likely Rome, and Rome likes its Oracle, baby.
My coding buddy Aaron Frost tamed this beast (to mix metaphors), so credit where it's due. I mostly watched and told him to use "sudo" in a couple of places. In this article we'll walk you through how he did it using one of two available drivers (as of this writing) to connect up your Node-acle beast under Linux. It's up to you to tame it. You up to it? Let's go!
Continue Freytag's pyramid
When you run a shell script or some other process from NodeJs and want to get the output in a stream to a client, you can redirect or pipe the output from the process that originally outputs to stdout into your socketio stream.
When you connect to a remote server, you're connecting over ssh or scp or a similar protocol. In each case, you may have to provide some authentication credentials to prove you are who you say you are. This can come in the form of a user/password combo, but if you're connecting a lot or if you're trying to setup a non-interactive connection, this can become either really monotonous or really problematic. Public/private keys will come to our rescue, and we'll never need to enter our password again.
Rack up more surf time on tasty articles...