#GoogleCloudSummit 2017 in Munich

While Amazon Web Services reported another record quarter with $4,53B in October 2017, and Microsoft reporting 93% growth of their cloud business, Google is the third major player in the market for cloud services.

At the same time, Google is not (yet) explicitly reporting numbers on their cloud offering. However, “all other” businesses, including Play Store,  also showed impressive 42% growth recently.

To demonstrate how serious the company is about their cloud products, Google demonstrated their commitment in roadshows, the Google Cloud Summit. Among others, like in Paris or Singapore, the Summit was held in Munich On December 6th in the MOC Munich.

Following a keynote between 9am an 11am, Google prepared 4 tracks covering diverse, cloud oriented topics in the areas of Application Development, Big Data & Machine Learning, Infrastructure & Operations, Startup. These tracks had continuous talks between 11am and 6pm, touching all topics from the field you could think of, starting with containers, docker and Kubernetes, going over IoT and Industry 4.0, touching Artificial Intelligence and Machine Learning, to Data Loss Protection and GDPR. All that along with Innovation and Agility in the context of security and privacy.

To round up the event,  outside the track rooms had an exhibition of selected cloud partners, from consultancy to implementation service, but also SaaS offerings leveraging the Google Cloud Platform.

While the market news seem that Google is late to the game, their commitment and quality of offering surely put them in an interesting spot and an alternative to the other two cloud vendors. The cloud summit definitely answered questions on Googles capabilities.

ssl and https with letsencrypt!

nomorecubes.net now (finally) leverages https!

It has a certificate from letsencrypt, automatically verified by the service, maintained and deployed by docker-letsencrypt-nginx-proxy-companion.

The deployment has been considerably easy through docker-compose, adding the container to the existing nginx-proxy like this:

version: '2'

 image: jwilder/nginx-proxy
 container_name: nginx-proxy
 - "80:80"
 - "443:443"
 - "./certs:/etc/nginx/certs:ro"
 - "/etc/nginx/vhost.d"
 - "/etc/nginx/conf.d"
 - "/usr/share/nginx/html"
 - "/var/run/docker.sock:/tmp/docker.sock:ro"
 image: jrcs/letsencrypt-nginx-proxy-companion
 - "/var/run/docker.sock:/var/run/docker.sock:ro"
 - "./certs:/etc/nginx/certs:rw"
 - nginx-proxy

Docker 1.10

Docker announced version 1.10 past week. The new release contains more than 100 improvements over the previous version. New features include better resource management, a more flexible docker-compose file format and improvements to security. These are in particular through user namespace isolation, implementation of seccomp for syscall filtering and an authorization plugin to restrict access to Docker engine features.

We’re pleased to announce Docker 1.10, jam-packed with stuff you’ve been asking for. It’s now much easier to define and run complex distributed apps with Docker Compose. The power that Compose brou…

via: Docker Blog
Release notes.