Sergei Ryabkov sryabkov

Instructions

Save the docker-compose.yml and config.yml in the same directory on one of your volumes on the NAS.
SSH in and use docker-compose up -d
Test the mirror with curl --head http://NAS-IP:55000
Start up docker daemons with the following option or put this in the daemon config file or copy into Docker for Mac/Windows settings. --registry-mirror=http://NAS-IP:55000
Pull an image and then check that it is cached in your mirror with curl http://NAS-IP:55000/v2/_catalog
- or check that a large image isn't slow after the first pull :)

Notes

progrium/bashstyle

Bash is the JavaScript of systems programming. Although in some cases it's better to use a systems language like C or Go, Bash is an ideal systems language for smaller POSIX-oriented or command line tasks. Here's three quick reasons why:

It's everywhere. Like JavaScript for the web, Bash is already there ready for systems programming.
It's neutral. Unlike Ruby, Python, JavaScript, or PHP, Bash offends equally across all communities. ;)
It's made to be glue. Write complex parts in C or Go (or whatever!), and glue them together with Bash.

This document is how I write Bash and how I'd like collaborators to write Bash with me in my open source projects. It's based on a lot of experience and time collecting best practices. Most of them come from these two articles, but here integrated, slightly modified, and focusing on the most bang for buck items. Plus some ne

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

	[
	{
	"text": "Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.",
	"author": "Martin Golding"
	},
	{
	"text": "All computers wait at the same speed.",
	"author": "Unknown"
	},
	{

	# source: http://st-on-it.blogspot.com/2010/01/how-to-move-folders-between-git.html
	# First of all you need to have a clean clone of the source repository so we didn't screw the things up.

	git clone git://server.com/my-repo1.git

	# After that you need to do some preparations on the source repository, nuking all the entries except the folder you need to move. Use the following command

	git filter-branch --subdirectory-filter your_dir -- -- all

	# This will nuke all the other entries and their history, creating a clean git repository that contains only data and history from the directory you need. If you need to move several folders, you have to collect them in a single directory using the git mv command.