Bashible: An Ansible-inspired deployment/automation tool written in Bash DSL

Re:Bashible: An Ansible-inspired deployment/automation tool ... by _frkl on Monday March 23, 2020 @07:27PM (#22670014)

I'd imagine it's because it's available everywhere (even openwrt routers and those things), and it's easier to get away with not having to use sudo (depending on the task you are doing, of course). With Ansible, you almost always need python installed on the target host. Which, in 95% of cases is not a problem. It's not ideal to install a system package just because you want to do some provisioning (there are ways around that, but it gets hacky pretty quick...).

I haven't looked at this yet, but I really like the idea. Always wanted to have something like this for a few special cases. And if it's well designed, it could be a nice, lightweight and portable solution to do server provisioning, development project setups, use in Docker builds, etc.

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by yjftsjthsd-h on Monday March 23, 2020 @08:27PM (#22670481)

> it's available everywhere (even openwrt routers and those things)

BASH itself? Or a Bourne-family shell? I thought most embedded systems were shipping busybox's ash as /bin/sh

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by travbrack on Monday March 23, 2020 @09:48PM (#22670980)

Most *nix server and cloud nodes use bash for the shell. You're right about embedded systems but they're not usually the target platform for a config management system like this one or Ansible.

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by yjftsjthsd-h on Monday March 23, 2020 @10:39PM (#22671338)

Yeah, I was mostly thrown by the reference to openwrt. I'm sure most/all GNU/Linux systems ship BASH.

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by shakna on Monday March 23, 2020 @11:03PM (#22671469)

Debian ship's dash for /bin/sh doesn't it?

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by detaro on Monday March 23, 2020 @11:26PM (#22671576)

but also ships bash for interactive use, so #!/bin/bash will just work, which you should be doing anyways in scripts that want bash.

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by mdaniel on Tuesday March 24, 2020 @12:21AM (#22671892)

If you use `env` instead, it'll pick up more recent versions of bash available on the path, such as the one installed by homebrew

    #!/usr/bin/env bash

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by abathur on Tuesday March 24, 2020 @12:14AM (#22671848)

/usr/bin/env bash?

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by toraobo on Tuesday March 24, 2020 @02:45AM (#22672576)

It's common even for embedded systems which use busybox to provide /bin/bash because bash itself is not that large.

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by senorsmile on Monday March 23, 2020 @11:34PM (#22671618)

In my experience, Perl is available everywhere. Some sort of bourne shell is likely available everywhere, but Perl is a safe bet. (EDIT: actually, some systems have recently started removing Perl from their base I hear... Fedora?)

[ Parent | on HN ]

Re:Bashible: An Ansible-inspired deployment/automation tool ... by pfundstein on Tuesday March 24, 2020 @12:36AM (#22671981)

Neither are available on common small embedded systems that rely 90% on busybox.

[ Parent | on HN ]