pch / welder Goto Github PK

I have a setup script which defines set -xeu. That script is to be run on a remote on which Fish is the default shell (it has bash). I get:

set: Variable can't be both exported and unexported
Standard input: set -xue # 'u' will give you warnings on unbound config variables
                ^

       set -- display and change shell variables.

   Synopsis
       set [SCOPE_OPTIONS]
       set [OPTIONS] VARIABLE_NAME VALUES...
       set [OPTIONS] VARIABLE_NAME[INDICES]... VALUES...
       set ( -q | --query ) [SCOPE_OPTIONS] VARIABLE_NAMES...
       set ( -e | --erase ) [SCOPE_OPTIONS] VARIABLE_NAME
       set ( -e | --erase ) [SCOPE_OPTIONS] VARIABLE_NAME[INDICES]...

set: Type “help set” for related documentation

This is clearly Fish's set and not Bash's set being used. My setup.sh defines a hash bang like so on the first line #!/bin/bash.

I'm using an (empty) sudo password.

Hi there!

I'm currently looking for an easy way to deploy an Elixir/ Phoenix application. Was Welder made for setting up servers only or for deployment as well? If so, how would I do it? Just create more playbooks like deploy, start, stop, migrate etc?

Thanks!

Initially, Ruby dependency was intended just as a convenient way to parse YAML. But if there's a better way to solve it without enforcing Ruby, I'll be happy to consider. Liquid also shouldn't be required if there's no *.liquid templates in the project directory.

I'll be happy to accept a PR that makes those dependencies optional.

When running welder run <my-playbook> I get:

[FAIL] No /opt/welder/<my-playbook>.yml file found

I've installed welder as per instructions. Welder is looking in the installation root for the playbook file.
The code responsible seems to be located here: https://github.com/pch/welder/blob/master/libexec/welder-run#L12. I believe the $WELDER_ROOT variable shouldn't be there.

While it is very uncommon to have ssh on different port, I believe it would be a great addition for

• Testing locally where one can spin-up containers which are usually bound to various ports.
• For those who actually have ssh on a different port.

Let me know if this makes sense to you. I'd be more than happy to submit a PR for this.