bvis

pipeline {
    agent { node { label 'swarm-ci' } }

    environment {
        TEST_PREFIX = "test-IMAGE"
        TEST_IMAGE = "${env.TEST_PREFIX}:${env.BUILD_NUMBER}"
        TEST_CONTAINER = "${env.TEST_PREFIX}-${env.BUILD_NUMBER}"
        REGISTRY_ADDRESS = "my.registry.address.com"

        SLACK_CHANNEL = "#deployment-notifications"

arun-gupta

1. kops: https://github.com/kubernetes/kops

   1. Getting Started Guide: https://github.com/kubernetes/kops/blob/master/docs/aws.md

   2. Installing Kubernetes on AWS with kops: https://kubernetes.io/docs/getting-started-guides/kops/

   3. Mulit-master Kubernetes Cluster on AWS with kops: http://blog.arungupta.me/multimaster-kubernetes-cluster-amazon-kops/

   4. Booting Kubernetes on Amazon Elastic Compute with kops: https://deis.com/docs/workflow/quickstart/provider/aws/boot/

   5. Setting up an HA Kubernetes Cluster in AWS with private topology with kops 1.5.1: https://www.nivenly.com/kops-1-5-1/

   6. Kubernetes on AWS: https://daemonza.github.io/2017/01/15/kubernetes-on-aws/

   7. Your 2nd day with Kubernetes on AWS: https://www.nivenly.com/2nd-hour/

2. Tectonic (Terraform): http://github.com/coreos/tectonic-installer

   1. Graphical installer: https://coreos.com/tectonic/docs/latest/install/aws/

aparrish

denji

1. Download docker-compose.yml to dir named sentry
2. Change SENTRY_SECRET_KEY to random 32 char string
3. Run docker-compose up -d
4. Run docker-compose exec sentry sentry upgrade to setup database and create admin user
5. (Optional) Run docker-compose exec sentry pip install sentry-slack if you want slack plugin, it can be done later
6. Run docker-compose restart sentry
7. Sentry is now running on public port 9000

• https://docs.docker.com/compose/compose-file/#env_file

simonw

How to recover lost Python source code if it's still resident in-memory

I screwed up using git ("git checkout --" on the wrong file) and managed to delete the code I had just written... but it was still running in a process in a docker container. Here's how I got it back, using https://pypi.python.org/pypi/pyrasite/ and https://pypi.python.org/pypi/uncompyle6

Attach a shell to the docker container

Install GDB (needed by pyrasite)

apt-get update && apt-get install gdb

dphuang2

function stringToNum(number){
    var out = parseFloat(number.toString().replace(',',''));
    return out;
}
function outputRecord(record, indicator, country, date, value){
    if(parseFloat(value).isNaN()){ // if the value is a string, then output value as string
        record.value = { 
            '${ID}' : indicator.toString(),
            '${CT}' : country.toString(),
            '${DT}' : parseInt(date),

kevindavenport

robertoestivill

#!/bin/bash

open -a "Google Chrome" --new --args --new-window \
'https://tweetdeck.twitter.com' \
'https://web.whatsapp.com' \
'https://blastersystems.slack.com/' \
'https://www.messenger.com/' \
'https://web.telegram.org/' \
'https://web.skype.com' \
'https://hangouts.google.com/' \

yunano

[Unit]
Description=consul agent
Requires=network-online.target
After=network-online.target

[Service]
EnvironmentFile=-/etc/sysconfig/consul
Environment=GOMAXPROCS=2
Restart=on-failure
ExecStart=/usr/local/sbin/consul agent $OPTIONS -config-dir=/etc/consul.d

myusuf3

To remove a submodule you need to:

• Delete the relevant section from the .gitmodules file.
• Stage the .gitmodules changes git add .gitmodules
• Delete the relevant section from .git/config.
• Run git rm --cached path_to_submodule (no trailing slash).
• Run rm -rf .git/modules/path_to_submodule (no trailing slash).
• Commit git commit -m "Removed submodule "
• Delete the now untracked submodule files rm -rf path_to_submodule