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 todoapp example contains a Netlify plan which uses the latest dagger
additions: do & Client API. We are thinking of merging the examples
repository into this one to make working with this easier. This is a
step in that direction.
We are not using the yarn package so that we can revert
https://github.com/dagger/dagger/pull/1673 without breaking this
implementation.
The GitHub Action is WIP, we will continue with that tomorrow:
https://github.com/dagger/dagger-for-github/issues/24
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>
So that it's easy for anyone to jump to the new docs that we are
currently working on, and intend to replace the existing docs with.
While I would have preferred to link to the local dev page, it's still
stuck in the PR state, currently blocked on another PR:
https://github.com/dagger/dagger/pull/1586
Also added a link to the pre-Europa docs, so that it's easy to go back.
While at it, drop "Sidebar" from the name of sidebars, and replace
tutorial with a more descriptive name.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
The goal is to capture the shape of the new docs. It is not meant to be
final, but it should be as close as possible. We only want the bare
minimum for new users that on-board with Dagger Europa. As soon as the
new europaSidebar replaces replaces the existing one, the previous docs
will still remain available - doc IDs are unique and permanent. We will
do this by simply changing the default `slug: /` to point to the Europa
Docs entrypoint, which is doc 1200.
Helpful Docusaurus link re multiple sidebars:
https://docusaurus.io/docs/sidebar/multiple-sidebars
The new pages are numbered from `1200` onwards. This is meant to reflect
the `0.2.0` Dagger version. This numbering felt more meaningful than
just continuing to increment existing numbers.
I didn't want to be "wasteful" with the digits and start at `2000`, but
that was my first instinct.
I am keen on getting this live on https://docs.dagger.io/1200/local-ci.
Anything that is not in production, is inventory. Inventory is bad.
The goal is to allow anyone that has a link to get a feel for the new
docs as soon as possible, so that we can all see how they improve in
real-time, and steer them continuously towards the desired state. We
should be aware of the timeline, and not muck about, but instead
evaluate constantly how close are we to "flipping the switch".
Remember, the best releases are those where switches are flipped (e.g.
`--europa)`. The feature will have been out there for weeks (maybe even
months), improved by talking to users and then one day realising that we
are done, and just enabling it by default. It's the same principle
behind these docs.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
