Re-writing microcosm in Go

The readme is idealistic ;)

And LFGSS makes running it hard because it's running on a custom domain with HSTS enabled and this is in the Chrome and Firefox HSTS preload list.

What I've done:

1. Create a self-signed SSL cert for *.microcosm.app
   
2. Checkout the repo
   
3. make && bin/microcosm-web --help
   
4. Fill in the MICROCOSM_WEB_CERT_FILE and MICROCOSM_WEB_KEY_FILE with the self-signed cert created in step #1
   
5. Note that the static files are expected to be at /srv/microcosm-web and for me that is a symlink to where I have checked out my repo, and then the path to the static files: microcosm-web -> /home/buro9/Dev/src/github.com/buro9/microcosm/web/files/ because my $GOPATH is /home/buro9/Dev
   
6. I'm practising on Brixton Cycles ;) I'll stop doing this now and will create a forum somewhere for dev work... but whilst I'm read-only (doing the read path before the write path) I have an /etc/hosts that is 127.0.0.1 forum.brixtoncycles.cc
   
7. make && bin/microcosm-web should now work
   
   

Then I hit the home path of forum.brixtoncycles.cc which is now served by my local dev copy of Microcosm.

The aim is to have 3 binaries from 1 repo:

• microcosm-web = just the front-end (for those who want to bespoke that but not run the API or database)
  
• microcosm-api = just the back-end and PostgreSQL (so I can scale this independent of other things)
  
• microcosm = all the things (you don't need the others as it includes front-end, back-end and PostgreSQL, scale by just having more instances)
  
  

I'm working exclusively on microcosm-web right now, just the front-end... which is talking to a live API :)

When done with the front-end, I'll be copying the existing backend code into this repo... and at that point, yes it will create the PostgreSQL tables, etc.

Today: Just the front-end, and you need some certs as all dev work is HTTPS.