fcrozat/distribution
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #13352 from thaJeztah/add_missing_codehints

Browse Source 
Add missing code-hints, and minor markdown edits
This commit is contained in:
Usha Mandya 2021-08-16 12:15:19 +01:00 committed by GitHub
commit 3fe6fc4dd4
3 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/garbage-collection.md
View File

@ -100,7 +100,7 @@ gives a clear indication of items eligible for deletion.
The config.yml file should be in the following format: The config.yml file should be in the following format:
``` ```yaml
version: 0.1 version: 0.1
storage: storage:
filesystem: filesystem:

2
docs/notifications.md
View File

@ -159,7 +159,7 @@ request coming to an endpoint.
An example of a full event may look as follows: An example of a full event may look as follows:
``` ```http request
GET /callback HTTP/1.1 GET /callback HTTP/1.1
Host: application/vnd.docker.distribution.events.v1+json Host: application/vnd.docker.distribution.events.v1+json
Authorization: Bearer <your token, if needed> Authorization: Bearer <your token, if needed>

3
docs/storage-drivers/s3.md
View File

@ -84,6 +84,7 @@ The following AWS policy is required by the registry for push and pull. Make sur
] ]
} }
``` ```
See [the S3 policy documentation](http://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html) for more details. See [the S3 policy documentation](http://docs.aws.amazon.com/AmazonS3/latest/dev/mpuAndPermissions.html) for more details.
# CloudFront as Middleware with S3 backend # CloudFront as Middleware with S3 backend
@ -135,7 +136,7 @@ are still directly written to S3.
The following example shows a minimum configuration: The following example shows a minimum configuration:
``` ```yaml
... ...
storage: storage:
s3: s3: