In this chapter, we learned how to deploy an isomorphic web application to the cloud. We presented how the igweb server-side application operates in production mode, showing you how external CSS and JavaScript source files were included by the application. We also showed you how to tame the file size of the JavaScript program produced by GopherJS. We showed you how to generate static assets for the application's template bundle along with the JavaScript and CSS that were to be used by the deployed cogs.

We first considered the deployment of an isomorphic web application to a standalone server. This consisted of adding an igweb user to the server, setting up the redis-server instance, setting up nginx as a reverse proxy with GZIP compression enabled, and setting up the igweb root folder. We also showed you how to cross compile Go code from the development system (64-bit macOS) to the operating system running on the production system (64-bit Linux). We guided you through the process of preparing a deployment bundle, and then we deployed the bundle to the production system. Finally, we showed you how to set up igweb as a systemd service so that it could easily be started, stopped, restarted, and automatically started on system startup.

We then focused our attention to the deployment of an isomorphic web application as a multi-container Docker application. We showed you how to install Docker on the production system. We walked you through the process of dockerizing igweb, which consisted of creating a Dockerfile, defining the services that make up IGWEB in a docker-compose.yml file, and running the docker-compose up command to start up IGWEB as a multi-container Docker application. Finally, we showed you how to set up the igweb-docker systemd script to manage igweb as a system service.