3 ms·

when would you use this? Sounds like an awful way to distribute and run software...

deleted 5y ago
[deleted]
spicybright 5y ago
Lots of reasons this can be useful. At my company we sometimes have to SSH into our dev nodes to restart things, figure out what's going wrong, etc. But we wipe them out nightly to update the code. This tool would let you keep all your special aliases for working on the nodes without manually copying your config(s) over. Can't say I'd use it, but I can see use cases like the above.
- laumars 5y ago
  For every use case I can think of, there are several better ways of achieving the same goal.
- suifbwish 5y ago
  Why not just have the instance run a script to fetch a new .rc file from a local repo? Or better yet just include the aliases in the profile/rc file on the image itself.
  - spicybright 5y ago
    The instance would need to have extra credentials for that I suppose, and you'd need the repo up somewhere, then track everything with git. Lots of engineers are also using the nodes, so you'd need to share that repo with them then have some command you type in each time to load it after you ssh into the node. And you'd only have updated versions of your rc every night, unless you want to commit a change, push, go to the server to pull it down, reload the shell. I guess what I'm saying is this tool fills a niche and avoids all the above complexity just for some shell aliases. (btw I don't really have a use for it, I just have 2 or 3 commands to copy paste into the shell for 99% of what I need to do. Just maintaining the argument to hear alternatives from people!)
    - suifbwish 5y ago
      As long as the commands are not secret, you could have your terminal just fetch them from a web server after logging in via the console and source it if the hash checksum of the page equals an expected value. If the checksum does not meet the expectation you either updated the commands in the file without updating the expected hash or the file server has been compromised.
johnisgood 5y ago
What does it have to do with distributing or running software? What did I miss from the README?
- nimih 5y ago
  It's a program whose only purpose is to download/build some executable files, transfer them to a remote host, and then execute them. That would seem to encompass both "distributing" and "running" software.
  - johnisgood 5y ago
    I only got the "transfer them to a remote host, and then execute them" bits, my bad. Probably because I see no reason for the first two steps.

deleted 5y ago

[deleted]

Lots of reasons this can be useful. At my company we sometimes have to SSH into our dev nodes to restart things, figure out what's going wrong, etc. But we wipe them out nightly to update the code. This tool would let you keep all your special aliases for working on the nodes without manually copying your config(s) over. Can't say I'd use it, but I can see use cases like the above.

laumars 5y ago
For every use case I can think of, there are several better ways of achieving the same goal.
suifbwish 5y ago
Why not just have the instance run a script to fetch a new .rc file from a local repo? Or better yet just include the aliases in the profile/rc file on the image itself.
- spicybright 5y ago
  The instance would need to have extra credentials for that I suppose, and you'd need the repo up somewhere, then track everything with git. Lots of engineers are also using the nodes, so you'd need to share that repo with them then have some command you type in each time to load it after you ssh into the node. And you'd only have updated versions of your rc every night, unless you want to commit a change, push, go to the server to pull it down, reload the shell. I guess what I'm saying is this tool fills a niche and avoids all the above complexity just for some shell aliases. (btw I don't really have a use for it, I just have 2 or 3 commands to copy paste into the shell for 99% of what I need to do. Just maintaining the argument to hear alternatives from people!)
  - suifbwish 5y ago
    As long as the commands are not secret, you could have your terminal just fetch them from a web server after logging in via the console and source it if the hash checksum of the page equals an expected value. If the checksum does not meet the expectation you either updated the commands in the file without updating the expected hash or the file server has been compromised.

johnisgood 5y ago

What does it have to do with distributing or running software? What did I miss from the README?

nimih 5y ago
It's a program whose only purpose is to download/build some executable files, transfer them to a remote host, and then execute them. That would seem to encompass both "distributing" and "running" software.
- johnisgood 5y ago
  I only got the "transfer them to a remote host, and then execute them" bits, my bad. Probably because I see no reason for the first two steps.