2 ms·
Are you aware of some well-built systems for enabling that? What you're describing, while simple in concept, is not so simple to set up. There's tooling to be
by otterley 10y ago
Are you aware of some well-built systems for enabling that? What you're describing, while simple in concept, is not so simple to set up. There's tooling to be written and authentication to synchronize.
- eropple 10y agoI...just do it? I don't find it to be complex at all. Use one or another method of user authentication for SSH (I use SSSD, but no solution can be really universally recommended), launch gitolite (a six line Chef recipe), do the same for Boxcutter or whatever you need. I tend to think that the problem isn't complexity, the problem is the current developer culture being so predicated on it's easy, you don't have to understand things that having to understand things borders on anathema. Yes, doing this does require understanding how your tools work, but that doesn't make it complex. And you should know anyway. Or pay me. My rates are reasonable. =)
- otterley 10y agoI've been doing this for 20 years now, and little has changed. It's not that developers don't think they have to understand things; it's that their incentives are to understand things that are relevant to the problem domains of the products they are working on. Reliable and efficient deployment strategies are not usually in their problem domains.
- eropple 10y agoThey may not have been in their problem domains twenty years ago (though they were for me from the start, albeit merely fourteen or so years ago =). I think that the future is obvious and that the expansion of the "stack" to the underlying runtime infrastructure is a foregone conclusion; this is ignored at a developer's own peril. (As it happens, I was a developer first--but I was managing my own infrastructure, too, and so from a very early age I had to be damned comfortable with doing that. Now the industry is pivoting there as "devops" becomes more and more of a thing.)