Create file /etc/systemd/system/[email protected]
[Unit]
Description=%i service with docker compose
Requires=docker.service
After=docker.serviceCreate file /etc/systemd/system/[email protected]
[Unit]
Description=%i service with docker compose
Requires=docker.service
After=docker.servicetl;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:
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* |
| diff --git a/code/portal_detail_display.js b/code/portal_detail_display.js | |
| index 45a179d..4bf4120 100644 | |
| --- a/code/portal_detail_display.js | |
| +++ b/code/portal_detail_display.js | |
| @@ -2,24 +2,6 @@ | |
| // main code block that renders the portal details in the sidebar and | |
| // methods that highlight the portal in the map view. | |
| -window.disabledGUID = []; | |
| - |