But you don't need Ruby installed?
Show HN: A simple Go utility to ease deployments via SSH and SCP
21–26 of 26 posts
Re: Show HN: A simple Go utility to ease deployments via SSH and SCP
#22Re: Show HN: A simple Go utility to ease deployments via SSH and SCP
#23Heh, I made a similar thing (mostly unreleased/undocumented at [0], original idea at [1]) that would take your Go code, build a binary wrapper for it using the target OS arch, SSH to the target, SCP the file over, run the binary, connect stdout/stderr/stdin with the remote, allow the remotely running binary to request files from the home binary, and delete itself once complete. One thing I found is SCP/SFTP is a real…
> I believe that we are getting to a point where config management might as well be in a programming language instead of a bunch of ad-hoc scripts in templates that defer to dynamic language scripts and become a mess. That's the idea behind my brainchild, judo[1]. [1]: https://github.com/rollcat/judo
Re: Show HN: A simple Go utility to ease deployments via SSH and SCP
#24Small question: In the readme (first section) you use, as an example, the command: "Run adduser bob 2>/dev/null" why do you add the "2>/dev/null" part? I see a lot of tutorial/guide/example/etc... do that! I understand what it does (send the stderr to devnull) but i don't understand why would i want to do that?
Re: Show HN: A simple Go utility to ease deployments via SSH and SCP
#25Earlier quoted context omitted.
That's a good point. Ansible is robust, well-known, well-supported, and has support for doing anything and everything from creating users, to setting cron-jobs, MySQL users, and more. This application only allows two things: * Uploading a file, or series of files. * Running a command, or series of commands. In short I'm very simple. But because of that it avoids some of the horrors of trying to be overly-complex in t…
So perhaps this is most comparable to Python's fabric library.
Re: Show HN: A simple Go utility to ease deployments via SSH and SCP
#26Earlier quoted context omitted.
> I believe that we are getting to a point where config management might as well be in a programming language instead of a bunch of ad-hoc scripts in templates that defer to dynamic language scripts and become a mess. That's the idea behind my brainchild, judo[1]. [1]: https://github.com/rollcat/judo
Judo seems like a great automation option for some simpler tasks where Ansible could be considered overkill. For me, that covers almost 100% of my remote automation needs. :) Nice!