Posted by: Frank | August 28, 2015

River4 On Google Cloud Platform

My spelunking among the public clouds has lead me to the Google Cloud Platform, where I spied with my little eye the Node.js instance and it’s $4.49 estimated monthly cost. The cost is not free, but I think it might be lowest monthly cost for hosting River4 on a cloud server. Probably the only lower costs are either the “free” node on Heroku, with all its constraints, or the one time purchase of a server at CloudAtCost.

I launched the Node.js instance on GCP and found that is Debian with node.js pre-installed. To install River4, one can skip the Install node.js portion of the Installing River4 on Ubuntu instructions and start with Install forever, then Install git and finall Install river4, before moving on to the River4 howto, starting at step 4.

You will need to open port 1337 in order to access the River4 site, it appears that something (perhaps node.js itself) is using port 80. I haven’t done much research into disabling whatever is using port 80. In the Google Developers Console, click Networking, Firewall rules. Click New firewall rule, and enter the fields as follows:

Name: allow-1337

Description: Allow port 1337 traffic to access the River4 home page (this is optional, you could leave it blank)

Network: default

Source filter: Allow from any source (0.0.0.0/0)

Allowed protocols and ports: tcp:1337

Then click Create.

To find the public IP address for your site, on the Google Developers Console click Compute, Compute Engine, VM instances. You will see your instance name listed below a graph showing CPU utilization, and to the right is the External IP address. To access the River4 Home page enter http://%5BExternal IP address]:1337 in the address bar of your web browser.

The Google Developers Console provides a button for SSH access to your instance, which opens an SSH session in a browser window.

The GCP Node.js instance is based on the Google Compute Engine f-1 micro instance that can cost as little as $0.0056 per hour per month if you run the instance for a full month. Again, for comparison, the AWS t2.micro instance costs $0.013 per hour, so you can see the compute part of the cost is much lower. I expect there will be additional I/O charges add to the $4.49 estimated monthly price.

from Notes http://ift.tt/1MTgJxE
via IFTTT

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Categories

%d bloggers like this: