In the installer instruction for Windows it is claimed that the dagger binary is placed inside the System32 folder if permissions allow it, which seems to be no longer part of the install.ps1 script (and seems like a bad idea anyways).
Signed-off-by: Jan Gräfen <223234+jangraefen@users.noreply.github.com>
This also accounts for dagger.io/dagger/core split introduced in
https://github.com/dagger/dagger/pull/1866
We should hold this merge until we are ready to cut the release,
otherwise links & some instructions will be broken until we release
v0.2.3.
Even though I would have preferred to have docs/update-version.sh in
Dagger, this is the quickest thing for now.
Related to https://github.com/dagger/dagger/issues/1854
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
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>
We're currently running markdownlint in CI and we didn't have a target
for that in our makefile. Adding that to prevent rejected PR's due to
markdown linting errors
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
This is a quick fix to attempt to automatically select the user's OS tab
on the pages that requires so which potentially avoids users following
incorrect docs
Signed-off-by: Marcos Lilljedahl <marcosnils@gmail.com>
So that we get auto-formatting and syntax checking in our code editor.
The only snippets which have not been extracted are either terminal
output, or file fragments (e.g. CUE) which are not valid standalone files.
Resolves https://github.com/dagger/dagger/issues/1715
While at it, do a few fly-by improvements:
- beta.1 -> beta.2
- add CUE & BuildKit links
- up -> do
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
There are a few outstanding tasks, but they can be finished tomorrow.
This is just the beginning of many refinements, so it's all good 🙌
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
The idea is to start simple and get users a good feel for how this works
within 5 minutes or less. We should cover the three popular OSes, and
ensure that everything works as expected.
At the end of this, users will have Dagger set up for local CI/CD, and
know how to make a change to the example app and re-run the build, test
& deploy loop.
This is part of https://github.com/dagger/dagger/issues/1327
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
