Skip to content

Latest commit

 

History

History
85 lines (60 loc) · 3.9 KB

README.md

File metadata and controls

85 lines (60 loc) · 3.9 KB
Raw
Host Service URL
static.grinnell.edu
landing

This document should be used to launch the static-landing-page, service name landing on host static.grinnell.edu as part of a docker-traefik2-acme-host stack.

Note that this process should be started only AFTER the acme service!

Command Sequence

cd ~/host/landing
docker-compose up -d; docker-compose logs

static-landing-page

This project defines the landing page for Grinnell's static.Grinnell.edu server.

Deploying this Site

As of 10-Jun-2020, this site is intended to be deployed using my docker-traefik2-acme-host approach. A docker container run command is no longer used to launch the site on Grinnell College's static.Grinnell.edu server.

Now Using Docker-Compose

With the introduction of Traefik v2.x this site now relies solely on files, most importantly docker-compose.yml, and a single docker-compose up -d command, to execute a one-time application launch. On Grinnell's static.grinnell.edu server, after the host has been initialized (see README.md), the whole command sequence, executed as administrator, looked like this:

cd ~/host
git clone --recursive https://github.com/McFateM/static-landing-page landing
cd landing
docker-compose up -d

Since the above commands have already been run once, there should be no need to do it again. However, the pertinent portions of the process can now be specified like so:

cd ~/host/landing
git pull  # assumes the git remote is origin -> https://github.com/McFateM/static-landing-page
docker-compose up -d

Local Development

It is recommended that you clone (or fork and clone) this repository to an OS X workstation where Hugo is installed and running an up-to-date version.

My typical workflow for local development is:

cd ~/GitHub/
git clone https://github.com/McFateM/static-landing-page
cd static-landing-page
git checkout -b <new-branch-name>
atom .
hugo server

The atom . command opens the project in my Atom editor, and hugo server launches a local instance of the site and provides a link to that site if there are no errors. This local site will respond immediately to any changes made in Atom.

Updating the Production Server

You can use a ./push-update.sh command to push your changes into production. Study the ./push-update.sh script and corresponding push-update-Dockerfile configuration to see all that it does.

An Even Easier Update

Not long ago I added the Atom Shell Commands package to my Atom config, added a command named Push a Static Update, and pointed that command at the push_update.sh script that is now part of this project.