Every Small Business should have their own domain name & website - these are the foundation of your brand, and your method to communicate with potential customers. Your domain name and website are one of the primary ways that people find your business, discover what products and services you offer, find your contact details, and even transact business with you (e-commerce transactions).
If you're just starting your business, you're not expecting very much traffic, and you want a simple website hosted - you can do this on Google Cloud. Google Cloud makes the process very quick, easy, and inexpensive. Follow along below.
You can also edit the Project ID, in this case I will set it to the same as the Project name.
As mentioned in the prerequisites - you'll need a domain that you own or manage. If you don't have an existing domain, there are many services through which you can register a new domain, such as Google Domains. This tutorial uses the domain www.cookingincloudhipster.com - which is managed through Google Domains and admin.google.com
Note: If you own the domain you are associating to a bucket, you might have already performed this step in the past. If you purchased your domain through Google Domains, verification is automatic.
On the World Wide Web, there are numerous systems that are used to make sure you can get where you need to go... one of the critical systems is DNS or Domain Name Services, which helps translate human readable names like www.cookingincloudhipster.com into the numeric IP Address number of the server that is hosting that website.
Within the DNS System there is the ability to add RECORDs to the DNS entry to help other services to be configured correctly, some the common ones are MX or Mail eXhange RECORDs - to help email systems work.
In this section were going to create an CNAME record - which stands for Canonical Name or it can be thought of as a an Alias so that when someone enters just cookingincloudhipster.com - without the "www" we can still find the right server...
A CNAME record is a type of DNS record. It directs traffic that requests a URL from your domain to the resources you want to serve, in this case objects in your Cloud Storage buckets. For more information about CNAME redirects, see URI for CNAME aliasing.
For www.cookingincloudhipster.com, the CNAME record will contain the following information:
And when you're done it should look like this...
Next, we'll create the Google Storage Bucket to hold our static site files.
So far in this codelab we have been using the Cloud Console GUI. However, Google Cloud can also be controlled using Google Cloud Shell, a command line environment running in the Cloud.
This Debian-based virtual machine is loaded with all the development tools you'll need. It offers a persistent 5GB home directory, and runs on the Google Cloud, greatly enhancing network performance and authentication. This means that all you will need for this codelab is a browser (yes, it works on a Chromebook).
To activate Google Cloud Shell, from the developer console simply click the button on the top right-hand side (it should only take a few moments to provision and connect to the environment):
Click the "Start Cloud Shell" button:
Once connected to the cloud shell, you should see that you are already authenticated and that the project is already set to your
gcloud auth list
Credentialed accounts: - <myaccount>@<mydomain>.com (active)
gcloud config list project
[core] project = <PROJECT_ID>
Cloud Shell also sets some environment variables by default which may be useful as you run future commands.
If for some reason the project is not set, simply issue the following command :
gcloud config set project <PROJECT_ID>
Looking for your
PROJECT_ID? Check out what ID you used in the setup steps or look it up in the console dashboard:
IMPORTANT: Finally, set the default zone and project configuration:
gcloud config set compute/zone us-central1-f
You can choose a variety of different zones. Learn more in the Regions & Zones documentation.
The command line version of "create bucket" can be seen below.
gsutil mb gs://www.cookingincloudhipster.com
Now, obtain the the static files from your website developer, or marketing team. If you're doing it yourself, there are plenty of great tutorials on HTML & CSS.
Then upload these static files into the bucket that was just created...
gsutil rsync -R local-dir
You can either make all files in your bucket publicly accessible, or you can set individual objects to be accessible through your website. Generally, making all files in your bucket accessible is easier and faster.
If you choose to control the accessibility of individual files, you can set the default object ACL for your bucket so that subsequent files uploaded to your bucket are shared by default.
Recommendation: Apply access permission to the entire bucket as a whole. This is safer, and since it is static website all of the contents are likely necessary to readable for the site to load properly. If you have some design metadata (or hidden files like .DS_Store - which is used on Apple MacOS operating system, .is a file that stores custom attributes of its containing folder, such as the position of icons or the choice of a background image.) These can be hidden or deleted individually.
Now, the last step is to assign an index page suffix, which is controlled by the MainPageSuffix property and a custom error page, which is controlled by the NotFoundPage property. Assigning either is optional, but without an index page, nothing is served when users access your top-level site, for example, http://www.cookingincloudhipster.com/
An index page (also called a webserver directory index) is a file served to visitors when they request a URL that doesn't have an associated file. When you assign a MainPageSuffix, Cloud Storage looks for a file with that name whose prefix matches the URL the visitor requested.
For example, say you set the MainPageSuffix of your static website to index.html. Additionally, say you have no file named directory in your bucket www.cookingincloudhipster.com. In this situation, if a user requests the URL http://www.cookingincloudhipster.com/directory, Cloud Storage attempts to serve the file www.cookingincloudhipster.com/directory/index.html. If that file also doesn't exist, Cloud Storage returns an error page.
The MainPageSuffix also controls the file served when users request the top level site. Continuing the above example, if a user requests http://www.cookingincloudhipster.com, Cloud Storage attempts to serve the file www.cookingincloudhipster.com/index.html.
For more information on the cases in which the index page is served, see Website configuration examples.
The error page is the file returned to visitors of your static site who request a URL that does not correspond to an existing file. If you have assigned a MainPageSuffix, Cloud Storage only returns the error page if there is neither a file with the requested name nor an applicable index page.
When returning an error page, the http response code is 404. The property that controls which file acts as the error page is NotFoundPage. If you don't set NotFoundPage, users receive a generic error page.
In the following sample, the MainPageSuffix is set to index.html and NotFoundPage is set to 404.html:
gsutil web set -m index.html -e 404-Page.html gs://www.example.com
And individual Product Pages...
If you are planning on doing the other labs in this series, don't do the cleanup now, do it after you are done with all the labs in the series.
Your created a static website & hosted it on Google Cloud!
Check out these other resources: