kjuulh/dagger
Archived
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity

Updated the Installer and Docs

Browse Source 
Updated Installer script and Docs accordingly to comments.
Now it does not request anymore the personal token to be produced.

Signed-off-by: alefesta <afesta@alfweb.com>
This commit is contained in:
alefesta
2021-06-30 17:54:12 +02:00
parent 40042204c5
commit 189fb715eb
2 changed files with 15 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/install.md
View File

@@ -37,16 +37,10 @@ sudo mv ./bin/dagger /usr/local/bin
## Option 2 (Windows): Run a shell script
Since Dagger repository is currently private, we have to use a workaround
to be able to run the script and match the latest release.
This workaround will be removed once the repo will become public.
To generate a personal access token on GitHub follow the guidelines at [Create a personal access token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)
From a terminal, run the following command:
```shell
$personalToken= <INSERT YOUR PERSONAL TOKEN>
curl https://releases.dagger.io/dagger/install.ps1 -OutFile install.ps1 ; ./install.ps1 -PersonalToken $personalToken; rm install.ps1
curl https://releases.dagger.io/dagger/install.ps1 -OutFile install.ps1 ; ./install.ps1; rm install.ps1
```
We try to move the dagger binary under `C:\Windows\System32` but