syfun syfun

Dockerfile: Remote build cache optimization for COPY (on Windows)

With Docker (especially with Buildkit) you have the ability to share your images as build cache for other computers.

When running the following docker build command, Buildkit will download cache information from the images, referenced with --cache-from.

export IMAGE="my-registry.example.com/myproject/myapp:feature-1234"
export IMAGE_LATEST="my-registry.example.com/myproject/myapp:latest"
export DOCKER_BUILDKIT=1

Directory Structure

The sources of the project follows this structure:

/src
  /app
    /{domain}
      /actions.ts
 /actions.spec.ts

注意：本文内容适用于 Tmux 2.3 及以上的版本，但是绝大部分的特性低版本也都适用，鼠标支持、VI 模式、插件管理在低版本可能会与本文不兼容。

Tmux 快捷键 & 速查表 & 简明教程

启动新会话：

tmux [new -s 会话名 -n 窗口名]

恢复会话：

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

	import asyncio
	import psycopg2

	# dbname should be the same for the notifying process
	conn = psycopg2.connect(host="localhost", dbname="example", user="example", password="example")
	conn.set_isolation_level(psycopg2.extensions.ISOLATION_LEVEL_AUTOCOMMIT)

	cursor = conn.cursor()
	cursor.execute(f"LISTEN match_updates;")

	# ...
	urlpatterns = [
	# ...
	path('graphql', GraphQLView.as_view(playground=True))
	]

	# Ubuntu 14.04 don't have nsenter - the straight forward way required me to install build tools and etc.
	# I preferred to keep the system clean and install nsenter in a container and then copy the command to the host
	# Note - its also possible to run nsenter from a container (didn't tried) https://github.com/jpetazzo/nsenter

	# start a container
	docker run --name nsenter -it ubuntu:14.04 bash

	## in the docker
	apt-get update
	apt-get install git build-essential libncurses5-dev libslang2-dev gettext zlib1g-dev libselinux1-dev debhelper lsb-release pkg-config po-debconf autoconf automake autopoint libtool

	def gettags = ("git ls-remote -t -h ssh://jenkins@<mygitpath>/repo/some.git feature/*").execute()

	return gettags.text.readLines()
	.collect { it.split()[1].replaceAll('refs/heads/', '') }
	.unique()
	.findAll { it.startsWith('<some more pattern>') }

	from sqlalchemy.ext.declarative import declarative_base
	from sqlalchemy import Integer, Column
	from postgresql_json import JSON
	Base = declarative_base()

	class Document(Base):
	id = Column(Integer(), primary_key=True)
	data = Column(JSON)

	#do whatever other work

	package main

	import (
	"bytes"
	"fmt"
	"io"
	"log"
	"mime/multipart"
	"net/http"
	"os"