jedi4ever

#!/bin/bash

DOCKER_IP=$(ip addr show docker0|grep "inet "|sed -e 's/^[ ]*//g'| cut -d ' ' -f 2| cut -d '/' -f 1)

docker stop redis_0
docker stop redis_1
docker stop sentinel_0
docker stop sentinel_1
docker stop sentinel_2

jedi4ever

Looking for the correct syntax


rsync -avz <host-dir> | docker exec rsync --server --daemon <inside-container-dir>

jedi4ever

// Proof of concept of monkey patching net.connect to make it support SRV records
// If require a monkey patched connect function before any other requires we can make a generic fix for handling SRV records
// We need of course to handle a few different cases & more robust error handling
// We can require a lib and even specify a filter for which hosts to resolve SRV and which not

var net = require('net');
var dns = require('dns');

// Set a specific Nameserver to be used
dns.setServers(['172.17.42.1']);

jedi4ever

#cloud-config

write_files:
  - path: /etc/systemd/system/docker.service.d/increase-ulimit.conf
    owner: core:core
    permissions: 0644
    content: |
      [Service]
      LimitMEMLOCK=infinity
  - path: /etc/ntp.conf

jedi4ever

I was asked to get some feedback on the following definition:

Dear Mr. Debois,

I would like to ask you for some feedback on the following definition drafts for the terms release engineering and DevOps.

Here, at RWTH Aachen University in Germany, we try to find definitions for those terms as part of a seminar in software engineering. Moreover, >in my work, I try to point out the differences between release

jedi4ever

Some notes on remote debugging mac builds on Travisci.  It's hard to tell when something hangs what the cause it. Trial and error via commits is tedious. And on Mac , sometimes it's the gui asking for input. So I worked my around to get the access I needed for faster debugging a build.

#################################################
# Enable remote ssh access to travisci build for debugging
#################################################
# Add a key so we can login to travisci vm
- cat ssh/travisci.pub >> ~/.ssh/authorized_keys
- chmod 600 ssh/travisci
  
# Install netcat

jedi4ever

http://testflightapp.com/install/0ad4aa4dee1873848fd900cb9bc14d61-MTMyMTk5Mjk/

jedi4ever

After adding crashlytics code (crashlytics.sh) & Patching the xcodeproject file (crashlytics.rb)

• It will work in xcode but not in cordova anymore.

• This is because xcoder writes the .xcodeproj file in a format that node-xcode doesn't understand.

• you need to 'beautify/sanitize' the file again.

  • brew install xcproj
  • and run xcproj -P <path to your xcodeproj file> touch

• now you are ready to go in cordova

jedi4ever

#!/bin/bash
set -ex

# This scripts allows you to upload a binary to the iTunes Connect Store and do it for a specific app_id
# Because when you have multiple apps in status for download, xcodebuild upload will complain that multiple apps are in wait status

# Requires application loader to be installed
# See https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/SubmittingTheApp.html
# Itunes Connect username & password
USER=bla

jedi4ever

Current setup

• npm install from public repo
• use of github URLs for private dependencies:
  • PRO: easy to use, using #master always fetches latests
  • BAD: npm install downloads every time, need to npm link or rm -rf node_modules to make sure
• rebuild of consolidated/minified files every time, using Git version
  • BAD: results in consistent build overwriting
  • IMPROVE: using hash of result and upload to cloudfront

Improved flow: