"The new Docker Registry 2.0 was released on April 16th, 2015. It was completely rewritten in Go with added support for the new Docker Registry HTTP API V2 (thus only working with Docker 1.6+), promising to provide faster and more secure distribution of images. If you work with Docker and for some reason decided not to use the public Docker Hub, a private Docker Registry is an essential part of your architecture. But even if you don't have private images, you will likely need to use your own registry in production/testing for efficiency.
The default installation, however, runs without encryption and authentication. I was wondering what's involved in securing it. There is an official tutorial on how to configure TLS on a registry server. TLS/SSL is absolutely necessary for any secure setup, but I also wanted to enable an authentication mechanism. The Configuration Reference document describes two authentication options supported by Docker Registry itself: so-called silly and token solutions. The silly one is apparently only useful for very limited development use-cases. The token solution seems to be more serious, but because of the lack of documentation (at the time of writing), I decided to find an alternative approach to secure it. In this article I'm going to show you how to set up the Docker Registry 2.0 with username/password authentication and SSL using the official Docker Registry image and a custom configured nginx as a proxy server."
"Google Container Registry provides secure, private Docker image storage on Google Cloud Platform.
While Docker provides a central registry to store public images, you may not want your images to be accessible to the world. In this case, you must use a private registry.
The Google Container Registry runs on Google Cloud Platform, so can be relied upon for consistent uptime and security. The registry can be accessed through an HTTPS endpoint, so you can pull images from any machine, whether it's a Google Compute Engine instance or your own hardware."
"At DataSift, we've standardised on using Git for our source control, using GitHub to host our public and private Git repositories, and using GitFlow as our common workflow
This website explains how we've adapted GitFlow and the GitFlow tools git extension for working with GitHub. This is how we work internally, and we're sharing this in the hope that others find it useful too."
"Clocker features:
Automatically create and manage multiple Docker hosts in cloud infrastructure
Intelligent container placement, providing:
resilience
fault tolerance
easy scaling
maximum resource utilisation of hosts
maximum application performance
Use of any public or private cloud as the underlying infrastructure for Docker Hosts
Deployment of existing Brooklyn/CAMP blueprints to Docker locations, without modification."
"1. The Government has already made a commitment to Big Data by classifying it as one of the 'Eight Great Technologies' which will propel the UK to future growth and help it stay ahead in the global race. The 'Information Economy Strategy' reports on the increase in data being generated and the importance of new types of computing power in order to reap the economic value of the data.
2. This paper sets out to cover the following areas:
a) Defining Big Data
b) High-level trends in Big Data
c) Opportunities for Big Data applications
3. In developing this paper, a 'community of interest' has been established
comprising policy leads and analysts from across government with an interest in Big Data. This paper draws on their insights, insights from the private sector, academics, and the extensive open source literature on the Big Data topic."
Security is part of everyday life. We lock our doors, protect our banking information with passwords that are usually so complicated that we tend to forget them. Using common sense to secure systems is just good practice. It's really easy to assume that because a system is internal, there is no need to enable authentication ...
"Athens provides a server for Go Modules that you can run. It serves public code and your private code for you, so you don't have to pull directly from a version control system (VCS) like GitHub or GitLab."
In this post I present the development model that I've introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful.