5 ms·
Actually we're planning to keep improving it, I factored out the SSH driver into SSHKit (http://github.com/capistrano/sshkit http://github.com/capistrano/sshkit
by codebeaker 12y ago
Actually we're planning to keep improving it, I factored out the SSH driver into SSHKit (http://github.com/capistrano/sshkit http://github.com/capistrano/sshkit) when I did the v3 rewrite. Right now we are founding a company, and hiring a team to build Harrow, the tool we all wish existed to tidy up some of the workflow loose ends, and bring some order (whilst maintaining flexibility) to what might otherwise being DevOps chaos. Find it (not launched yet) at https://www.harrow.io/ https://www.harrow.io/. One of our goals for Harrow is to open source that as well as running a hosted service, and using the revenue and expertise to follow the (exceptional) Hashicorp example of building a commercial FOSS company to build excellent, useful software, whilst defining new standards, and providing all the tools people didn't know they needed.
Of course we know that Docker, and Rocket, and to an extent more of the AWS tools are automating a lot of these processes, but for every problem they solve, some people can't use them, and we're counting on "script things, run them in a repeatable environment, share the scripts, and results with your team" theme won't go away for a while (ever?), as most of what we do, even with all these modern deployment tools is still programmer duck-tape.
- lifeisstillgood 12y ago(Late to the conversation - I've had this tab open that long!) I just wanted to ask your opinion on the docker comment - I think tools that make repeatable builds will always be necessary (even if only to make the first docker instance of your immutable server). Or is there some other theme at play I so not understand that means this idea is old hat?