Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance documentation regarding registries file #119

Merged
merged 1 commit into from
Nov 20, 2023
Merged

Enhance documentation regarding registries file #119

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,10 +52,12 @@ It is also possible to put all authentication information in a secret file. This
* registry: the registry to authenticate against, eg `registry.gitlab.com`
* login: the user to authenticate as
* password: the password to authenticate with
Lines starting with `#` are comments, and are ignored, as are invalid lines.

Lines starting with `#` are comments, and are ignored, as are invalid lines. Make sure this file ends with a new line. Otherwise your last line in the file will be ignored ([here is why](https://stackoverflow.com/a/729795/1752287)).
Here is an example:
```
blog registry.gitlab.com gitlab+deploy-token-5123674 ssw2Nrd2

```
Create and edit that file locally, eg at the location `private/shepherd-registries-auth`, and create the docker secret with
```
Expand Down