Investigate options for Private Key / Certificate / Environment Variable Management

At present, provisioning a VM instance requires several _manual_ steps. _Specifically_:
+ [ ] SSL/TLS Certificate Creation
+ [ ] SSL/TLS Certificate location (on the file system)
+ [ ] Updating the NGiNX config file to reflect the location of the Certificate see: [nginx.config#L37](https://github.com/healthlocker/healthlocker/blob/3daa89818d7415bc52a64c2a6b17cee9c7f3253e/nginx.config#L37)

These _manual_ steps ok _initially_ because "_automation_" is _expensive when uncertainty is high (_e.g. in a "startup"_) read: http://paulgraham.com/ds.html

However I _counter_ that _automating_ the steps (_using scripts_) is not _that_ much more work than documenting them (_in words for humans to read_).

Possibly invest time in https://github.com/dwyl/akey ? ⏳ / 💰
Which would be a _general purpose_ solution to the problem ... 🤔