Re:XXH: Bring your favorite shell wherever you go through th...
by suifbwish on Tuesday December 14, 2021 @05:00PM
(#29558561)
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.
[ Parent
| on HN ]
Re:XXH: Bring your favorite shell wherever you go through th...
by spicybright on Wednesday December 15, 2021 @09:48AM
(#29566649)
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!)
Re:XXH: Bring your favorite shell wherever you go through th...
by suifbwish on Tuesday December 21, 2021 @03:25AM
(#29635214)
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.