jareware's comments

Echoing the sentiment here, this is a great way to host smaller projects on the cheap, without adding the complexity/price of k8s, Nomad et al!

I do the same, and have spent some time automating the backup of such a set of standalone containers [0], in case others also find it useful.

[0] https://github.com/jareware/docker-volume-backup

FWIW, io-ts offers this via its “userland” implementation of branded types.

If there's an API for working with data that you know well already, it's somewhat pointless to learn the (quite esoteric) jq one.

Just pipe curl to node (https://github.com/jareware/howto/blob/master/Replacing%20jq...) or Python or Ruby or whatever you already know!

Thanks for being upfront about “don’t have any plans for that”, instead of a vague “we’re looking into it” which sounds better but effectively means the same thing.

Ditto, with https://github.com/jareware/howto/, which I’ve been meaning to automatically sync from a specific notebook from my Joplin. Yours looks very polished though, maybe I should just use that!

I feel like Joplin (https://joplinapp.org/) should also get mentioned: storing notes in plain Markdown files, optionally synced via e.g. Dropbox. Bonus points for also having mobile apps that sync with the same backend.

Either your colleagues were very misinformed, or this was a slight misunderstanding on your part: Terraform IS cloud agnostic, but not in the way you understood.

Instead, it allows you to use the same tool and management model for resources on any of the 3 big cloud providers, about a 100 assorted SaaS providers, and most importantly, wire them together (e.g. create a Mailgun configuration, and set up its verification DNS records on AWS), all in code, and in the same workflow.

Same feature set - plus a few extras like Basic Auth support, custom headers, preventing direct access to the underlying S3 bucket - implemented as a reusable Terraform module: https://github.com/futurice/terraform-utils/tree/master/aws_...

We had a similar need a while back, and open sourced our solution: [alley-oop](https://github.com/futurice/alley-oop) is a Dynamic DNS server with an integrated Let's Encrypt proxy, enabling easy HTTPS and WSS for web servers on a local network (LAN).

It effectively automates the process that's described in the article. Once you have it set up (you need a few DNS entries and a tiny Go server running somewhere), using it is as simple as issuing an HTTP API call to your alley-oop server with the LAN IP you have, and the DynDNS domain you want associated with it, and getting a valid cert in return. You're then ready to spin up your HTTPS server with it, and start serving LAN traffic with a valid cert.