kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity
This repository has been archived on 2024-04-08. You can view files and clone it, but cannot push or open issues or pull requests.
6c1d7ec19f
dagger/docs
History
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
..
administrator Use unique IDs for all existing doc pages 2022-02-10 07:38:11 +00:00
core-concepts Add BrowserOnly component to avoid SSG errors 2022-03-24 16:02:27 -03:00
getting-started Allow any published dagger version to be installed via install.sh 2022-03-24 23:28:07 +00:00
introduction Default docs to Europa 2022-03-09 20:12:50 +00:00
knowledge-base docs: migrate from 0.1 2022-03-10 16:50:37 -08:00
learn Merge pull request #1837 from marcosnils/feat/docs_os_select 2022-03-24 23:10:32 +00:00
reference Remove old docs 2022-02-23 12:20:01 -07:00
tests Fix the missing property "on" for getting started github action 2022-03-23 15:50:22 +01:00
use-cases Temporarily remove Use Cases from the Europa docs sidebar 2022-03-04 18:58:17 +00:00
1001-install.md fix: Build from source instructions 2022-01-28 11:38:04 +01:00
new.sh Add front matter to new docs 2022-03-08 11:32:10 -01:00
README.md Answer a few contributor questions via a docs README 2022-02-18 15:58:23 +00:00

README.md

FAQ

The intent behind this README is to answer contributor questions regarding docs.dagger.io.

What happens to a new doc page after the PR gets merged?

It gets automatically deployed to docs.dagger.io.

The doc URL will use the slug property from the doc markdown metadata.

Given slug: /1001/install/, the live URL will be docs.dagger.io/1001/install

How can I run docs locally?

You will need to have yarn and Node.js v16 installed.

From the top-level dir - cd ../ - run the following command: make web

This will install all dependencies, start the docs web server locally and open localhost:3000 in your browser.

How can I add a new doc page?

From the docs dir, run ./new.sh doc-title

This will create a new Markdown file for the new doc page, i.e. docs/1214-doc-title.md

This new doc will not be added to the navigation. We prefer to keep the organisation of doc pages, and writing them separate. For the time being - 2022 Q1 - the focus is on writing self-contained doc content. Don't worry about where to fit this content, it's enough to keep this in mind: Writing effective documentation.

What else should I keep in mind as I add new doc pages?