I’ve recently taken to doing this in Go and absolutely love how easy it makes writing and deploying software that depends on static files.
I’ve recently taken to doing this in Go and absolutely love how easy it makes writing and deploying software that depends on static files.
Having the static frontend assets baked in along with a default config is a huge boon though.
It supports embedding the encrypted secrets in the binary or loading them from a file. The secrets would actually be stored (encrypted) alongside the code, even versioned in git.
Eg this is the rust version on GitHub: https://github.com/neosmart/securestore-rs/tree/master
See https://github.com/bbkane/grabbit for an example
Makes it trivial to run `brew/scoop update myapp` from another computer
I have used cargo-dist and the process is quite smooth, it could be worth giving it a try.
But there is one question. The article says:
> I get my HTTPS certs from Let's Encrypt via certbot — this handles automatic renewal so I don't have to do anything to keep it working.
But I'm using cross-region setup with two servers and a geo-DNS. With this setup, the certbot only works for the server, located in the US, and I have to manually copy the certificates to the server in Europe. Any idea how to overcome this?
PS. Read about ClickHouse Playground here: https://ghe.clickhouse.tech/