
g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry
Preview meta tags from the g.raphaelli.com website.
Linked Hostnames
10- 7 links tog.raphaelli.com
- 4 links togithub.com
- 2 links todocs.docker.com
- 1 link toblogs.aws.amazon.com
- 1 link todocs.aws.amazon.com
- 1 link togist.github.com
- 1 link togohugo.io
- 1 link topeterjshan.com
Search Engine Appearance
https://g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry
Docker S3-Backed Private Registry On Every Host
The HTML5 Herald
Bing
Docker S3-Backed Private Registry On Every Host
https://g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry
The HTML5 Herald
DuckDuckGo
https://g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry
Docker S3-Backed Private Registry On Every Host
The HTML5 Herald
General Meta Tags
9- titleDocker S3-Backed Private Registry On Every Host - g.raphaelli.com
- charsetutf-8
- viewportwidth=device-width,initial-scale=1
- descriptionThe HTML5 Herald
- author
Open Graph Meta Tags
6- og:urlhttp://g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry/
- og:site_nameg.raphaelli.com
- og:titleDocker S3-Backed Private Registry On Every Host
- og:descriptionUpdate - AWS has since released a private registry service I attended this talk at a GoLangPhilly meetup back in August where the speaker, Peter Shannon, detailed the setup his company has been using to run docker in production. Every host there runs a local docker registry server backed by S3. That was the first I’d heard of this setup. Usually posts discuss running a private registry in a dedicated spot (usually on AWS, behind an ELB) and funneling all docker pulls and pushes through it. Eliminating authentication issues and a single point of failure (except s3 of course) seem like a big win with little downside. I decided to try it out.
og:locale
en_us
Twitter Meta Tags
3- twitter:cardsummary
- twitter:titleDocker S3-Backed Private Registry On Every Host
- twitter:descriptionUpdate - AWS has since released a private registry service I attended this talk at a GoLangPhilly meetup back in August where the speaker, Peter Shannon, detailed the setup his company has been using to run docker in production. Every host there runs a local docker registry server backed by S3. That was the first I’d heard of this setup. Usually posts discuss running a private registry in a dedicated spot (usually on AWS, behind an ELB) and funneling all docker pulls and pushes through it. Eliminating authentication issues and a single point of failure (except s3 of course) seem like a big win with little downside. I decided to try it out.
Link Tags
4- stylesheet/css/normalize.min.css
- stylesheethttp://g.raphaelli.com/fontawesome/css/all.min.css
- stylesheethttps://fonts.googleapis.com/css?family=Roboto+Slab|Ruda
- stylesheet/css/styles.css
Links
20- http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html
- http://g.raphaelli.com/index.xml
- http://g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots
- http://g.raphaelli.com/posts/2015-12-14-ipython-elasticsearch
- http://peterjshan.com/speaking/2015/08/golangphilly-phillydevops-combined-meetup