Viewing profile — lstoll

We use an AWS KMS asymmetric key for the CA keys, they're cheap and avoids exposing the private key material in an any way. For signing SSH certificates, we run a small service (pr…

I migrated from the EU to the US, but then realised that once everything was factored in (medical, car, housing, cost of living) the taxes were actually worth it, so I moved back t…

you don't have to predict that exact scenario to know that domestic semiconductor manufacturing is a good idea.

This is fine while you're employed, but what if you lose your position or decide to take a couple years off? Then it becomes a different equation. Spread out over time, in the plac…

Git also supports S/MIME, and GitHub provides a tool to sign commits with this directly https://github.blog/changelog/2018-09-10-smime-signature-ver...

It used to use RubyEncoder, now it uses something custom. The overhead is very minimal, and it's only when the source is read off disk.

We just keep all our go code in one repo.

Heroku already does this pretty well, not sure what the benefit would be?

There's already a `goenv` https://github.com/wfarr/goenv , that I've been using for a bit. Also can do go version management.

I recently had an immediate need to use Fusion in a Vagrant-style environment, so I hacked 'Tenderloin' together from an old version of Vagrant: https://github.com/lstoll/tenderloi…

There is, it's just not officially supported: https://github.com/heroku/heroku-buildpack-php . Github lists it as having 82 forks, so people are definitely playing around with this…

I'd rather see a benchmark of a more real-world case. These hello world microbenchmarks don't show anything.

I think if a new 'leader' in version control systems starts to make ground, github could easily adapt and support it. The github magic isn't just git, it's the network and collabor…

It is however possibly the only obviously 'Java' experience that most non-techinal people have had. If you're trying to prove to them that Java is everywhere, this is what's going …

How is it flawed? According to the original report IE's handling is correct, it's the spec that's flawed.

Seems to work fine: http://smooth-stream-686.herokuapp.com/ (code at https://github.com/lstoll/heroku-playframework-scala , basically a simple hello world app)