Skip to content

Instantly share code, notes, and snippets.

View asnapper's full-sized avatar
👷‍♂️

asnapper asnapper

👷‍♂️
View GitHub Profile
@asnapper
asnapper / README.md
Created June 1, 2018 23:12 — forked from mosquito/README.md
Add doker-compose as a systemd unit

Docker compose as a systemd unit

Create file /etc/systemd/system/[email protected]

[Unit]
Description=%i service with docker compose
Requires=docker.service
After=docker.service
@asnapper
asnapper / article.md
Created December 11, 2015 21:50 — forked from zubairov/article.md
Running a docker private registry on EC2

tl;dr This blog post describes the best way to host private Docker Registry instance on Amazon EC2 and Amazon S3. You can skip the lyrics and go to the 'Resources' section to get the ECS Task Definition JSON.

When working with microservices nowadays you can hardly avoid using Docker. After building your first Docker container your next step woudl be to share it with the world (or your colleauge). To achieve it you have three alternatives:

  1. Use a Docker Hub or any other SaaS registry.
  2. Deploy your own instance of open source Docker Registry project (now called 'Distribution').
  3. Buy an enterprise version of the Docker registry which is based on open source docker registry project with some addons from Docker Inc.

For a small project the Docker Hub 'way' is the best alternative, you can host one 'private' image for free, where commercial pricing plans will allow you to upload more. For a more serious projects we would like to re

// ==UserScript==
// @id disable-portal@asnapper
// @name IITC plugin: Disable Portal
// @category Tweaks
// @version 0.0.1.20140205.104101
// @updateURL none
// @downloadURL none
// @description [local-2014-02-05-104101] Allows you disable specific portals for plugins like fly-links
// @include https://www.ingress.com/intel*
// @include http://www.ingress.com/intel*