2 ms·
Author here: I would be flattered if people found this invaluable enough to install on fleets of servers. But pragmatically that's not the problem I'm trying t
by hnlmorg 6y ago
Author here:
I would be flattered if people found this invaluable enough to install on fleets of servers. But pragmatically that's not the problem I'm trying to solve. I think managing remote systems is largely a solved problem with tools like Ansible (or which there are many competitors) and the few occasions you want to drop into a shell on a remote machine are occasions when you want the least resistance. So Bash is a sensible choice. But the problems Sysadmins/DevOps/Developers face these days is that a lot of tooling starts out being ran on local machines before being pushed out to CI/CD, Kubernetes, ELK stacks, Github/Gitlab, to all these other wonderful enterprise tooling I've neglected to mention. And having a shell that glues all these local machine executables together can still give big productively gains even if it does diverge from Bash.
So that's the inspiration behind this shell. It's not there to replace Bash on the server but it is designed to make engineers lives easier when working locally with CLI tooling like Docker, git, Terraform, JSON log files, and so on and so forth.
Of course, you're free to use / not use this in any way you want :)
- bayindirh 6y ago> I think managing remote systems is largely a solved problem with tools like Ansible... Leaving a server in the dark and remotely prodding it via Salt/Ansible/Chef/Puppet makes sense in a very narrow and very limited scenario set. Even if you manage all your systems like that (I generally install a fleet via XCAT and manage some of them via Salt), you probably need to login to that server and poke around to see what went wrong with a user's job or why that server is acting wonky. OTOH, I applaud you for all the work you did and hope this shell makes lots of people's lives much easier. Keep up the good work, good luck. :)
- jonwest 6y agoThat’s where tools like Greylog, fluentd, and tools like Prometheus or “full service” tools like New Relic et al come into play—if you’re managing one or two servers, sure, it makes sense to jump in and poke around, but beyond a handful of servers that becomes a nightmare and centralized visualization is going to do wonders for your sanity without having to dive into individual machines on a semi regular basis.
- gigatexal 6y agoHey Author ;-) If I can find the wherewithal to switch my native shell to one of these shell improvements such as yours I will. I think the productivity gains could be really nice. Of late, I've been forcing myself to learn idomatic bash for my shell scripting duties, though. Perhaps a feature to think about would be to be able to transpile to idomatic bash so that people could script in your shell but ship portable bash. Then once more and more devs adopt your shell it could replace bash.
- hnlmorg 6y agoThanks for the feedback and that's an interesting suggestion. The biggest hindrance to that is that murex has builtin support for structured data types which would mean any transpiled code might then depend on non-standard tools like `jq`. But it's an interesting enough problem that I might have a play if just out of academic curiosity. I've created a Github issue so the suggestion doesn't get forgotten: https://github.com/lmorg/murex/issues/281 https://github.com/lmorg/murex/issues/281
- gigatexal 6y agoWow I’m honored. I’ll follow the issue.
- blondin 6y agothoroughly impressed by what i saw in the terminal session video! my inner voice kept saying: that's how it is supposed to be. totally understand where OP is coming from though. most of the automation tools you cited would often have you drop in the shell because, well, they can't do it all. this is a great project and i will be following it. even if it doesn't become widespread, i hope some of the ideas will catch and live on. i don't want to look for binaries or configuration paths. i want inline docs as i type. and i want un-paged docs on my terminal. tired of googling documentation. hashicorp i am looking at you guys. "go doc" is the best thing ever. and yet you guys make us google for documentation all the time! i want the online multi-line completion and variable expansion i saw in the video, etc. everything i saw looks good. great job!