Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

This series of articles will cover how you can set up a secure (SSL, HTTPS) web site for free by using Google's always free Cloud Tier in combination with free SSL hosting from Cloudflare. The only requirement is that you have a Google account and your own domain name.

This article will only cover how to host a static site i.e. HTML files with images, CSS and JavaScript. If you have a requirement for dynamic content e.g. PHP or other server side scripts, that is not going to be covered but most of the steps here will still be applicable to you.

The article is split into three parts:
  • Creating a Google Cloud project and deploying your site (what you're reading now)
  • Setting up a custom domain for your site (part 2)
  • Enabling SSL via Cloudflare (part 3)

So lets get started. If you don't have a Google account already, go ahead and sign up, it's free.

Next head on over to the Cloud Platform Console and click the drop down next to 'Select a project'.

Click the + button to create a new project.

Enter your project details. It doesn't really matter what you put in here, just keep track of the Project ID that is assigned. You can also click Edit to assign your own ID like I did.

Click Create and you'll be taken to the project's dashboard page. If that doesn't happen, click the drop down next to 'Select a project' again and select your project from the 'All' tab.

The next step is to download and install the Google Cloud SDK. There are platform specific instructions and a download link on the documentation site. Since there are many platforms to cover and Google's documentation already does a good job of that I will not cover that here. Just follow the instruction on the documentation page linked above.

After installation, when you run 'gcloud init' select your project created above as the default project. This is where you'll need to know the Project ID you noted earlier.

The next step is to make your web site deployable to the Google Cloud. There is an article that Google has posted about hosting a static site which is useful but I like my approach below better.

First create a new directory for your project and take your existing web site code and put it into a sub-directory of the project directory called 'web'. This should include all of the CSS, JavaScript, images, HTML pages, etc.

Then create a text file called app.yaml in the project directory (contents for this file are listed below).

The layout should look something like this:

Here's an app.yaml file that should work for most static sites. There is a reference available in case you need to customise it.
runtime: python27
api_version: 1
threadsafe: true
- url: /
static_files: web/index.html
upload: web/index.html
- url: /(.*)
static_files: web/\1
upload: web/(.*)

The only thing to do now is deploy your project/site. This is done by running the 'gcloud app deploy' command. This is done in the same manner as when you ran the 'gcloud init' command but you have to do it from the project directory (where you app.yaml file is).

Deployment will ask you where you want to deploy, pick the most appropriate data centre to continue. Your site will be packaged and uploaded to the Google Cloud. The final output should look something like this:
╠═ Uploading xx files to Google Cloud Storage ═╣
File upload done.
Updating service [default]...done.
Deployed service [default] to [https://myfreewebsite-123.appspot.com]

At this point your site will be available via the appspot.com domain but not your own domain. The next part of this article is how to set up your own domain for your project.

Continue reading to set up you domain for you web site in part 2 of this article.


Please leave your comments or feedback below!
comments powered by Disqus
Other posts you may like...
Hi! You can search my blog here ⤵
Or browse the recent top tags...

Recent Blog Posts

Using DeoxIT to repair old game catridges

WebLogic Maven Plugin - How to fix the MojoExecutionException: The artifact location was not specified

jPhotoFrame version 0.4 released with a whole new layout engine

Upcycling a couple of old broken lamps to create something amazing

A custom exception mapper and writer for a RESTful JAX-RS Jersey service

How to fix Plex error - Sorry there was a problem playing this item

Jersey JAX-RS filters and interceptors execution order for a POST request

Fix your Mac - users not showing on the macOS login screen when FileVault is enabled

BMB-012 Nanoblock T-Rex Skeleton Model assembly

Writing a custom MessageBodyReader to process POST body data with Jersey

Recent Galleries

BMB-012 Nanoblock T-Rex Skeleton Model assembly

Tiny Arcade revision 6 kit assembly and decal application

Atari Lynx repair - Part 5 - McWill LED screen mod installation

Atari Lynx repair - Part 4 - screen cover replacement

Atari Lynx repair - Part 2 - re-capping the motherboard

Atari Lynx repair - Part 3 - broken speaker replacement

Atari Lynx repair - Part 1 - introduction and case disassembly

Building a custom Atari Lynx game box storage shelf unit in a day

Protecting old Atari Lynx game boxes with snug fit plastic sleeves

Monument Valley 2 is released and does not disappoint

Blogs and Friends

Matt Moores Blog
Georgi's FlatPress Guide
Perplexing Permutations
The Security Sleuth
Ilia Rogatchevski
Travelling Fairy

Blog Activity

Blog Activity