Commit Graph

3 Commits

Author SHA1 Message Date
Gerhard Lazu
6c1d7ec19f
Fix install.sh when no version provided
This fixes a bug that I introduced in
https://github.com/dagger/dagger/pull/1819

Mistakes that get fixed before anyone notices never happened. Focus on
the learnings, quick fixes and let resilient systems emerge. 💪

Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2022-03-24 23:53:45 +00:00
Gerhard Lazu
6db19fcea2
Allow any published dagger version to be installed via install.sh
This also updates Getting Started - CI/CD in your local dev - Linux & Mac doc.
A few other related doc changes were pulled in by this.

I wanted to try different versions of dagger on Linux, and this was the
easiest way of doing that:

    curl -L https://dl.dagger.io/dagger/install.sh -O
    # make this change, and then:

    DAGGER_VERSION=0.2.0 sh install.sh
    # ...
    ./bin/dagger version
    dagger 0.2.0 (e499297e) linux/amd64

    DAGGER_VERSION=0.2.1 sh install.sh
    # ...
    ./bin/dagger version
    dagger 0.2.1 (69b4845d) linux/amd64

This change enables anyone to do the following instead:

    curl -L https://dl.dagger.io/dagger/install.sh \
    | DAGGER_VERSION=0.2.0 sh

Until this gets merged, you can test how this change works in practice
via this temporary file:

    curl -L https://dl.dagger.io/dagger/install-pr-1819.sh \
    | DAGGER_VERSION=0.2.0 sh

One thing which I was not sure about is how the file from this
repository ends up on https://dl.dagger.io/dagger/install.sh. I think
this is a manual process today, but I need to confirm this assumption.

Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
2022-03-24 23:28:07 +00:00
Sam Alba
43b43f7868 release: added install script
Signed-off-by: Sam Alba <sam.alba@gmail.com>
2021-05-03 17:20:45 -07:00