g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry

Preview meta tags from the g.raphaelli.com website.

Linked Hostnames

10

Search Engine Appearance

Google

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
    • title
      Docker S3-Backed Private Registry On Every Host - g.raphaelli.com
    • charset
      utf-8
    • viewport
      width=device-width,initial-scale=1
    • description
      The HTML5 Herald
    • author
  • Open Graph Meta Tags

    6
    • og:url
      http://g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry/
    • og:site_name
      g.raphaelli.com
    • og:title
      Docker S3-Backed Private Registry On Every Host
    • og:description
      Update - 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.
    • US country flagog:locale
      en_us
  • Twitter Meta Tags

    3
    • twitter:card
      summary
    • twitter:title
      Docker S3-Backed Private Registry On Every Host
    • twitter:description
      Update - 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
    • stylesheet
      http://g.raphaelli.com/fontawesome/css/all.min.css
    • stylesheet
      https://fonts.googleapis.com/css?family=Roboto+Slab|Ruda
    • stylesheet
      /css/styles.css

Links

20