Skip to content

Instantly share code, notes, and snippets.

Michiel van Baak mvanbaak

View GitHub Profile
View gist:e98b7b622ea2c8ab626d51cb88e27406
#!/bin/sh
# default commands for osx to make it nicer to work with
##########################
# General UI?UX settings #
##########################
# Set hostname (hex of MVB9APPS)
sudo scutil --set ComputerName "0x4d56423941505053"
sudo scutil --set HostName "0x4d56423941505053"
View check-deleted-amis.py
# -*- coding: utf-8 -*-
from __future__ import print_function
import json
import boto3
# SNS Config
sns_topic_arn = "arn:aws:sns:eu-west-1:AWS-ACCOUNT-ID:SNS-TOPIC"
sns_subject = "ASGs Missing AMIs"
View gist:9b86b4b89c21eff0e47650b90ba816b2
To make sure our work can be pushed back to upstream mautic/mautic we have to keep
our fork up-to-date from time to time. Also, making changes should follow the following
workflow to make it easy to track bugs/pull-requests etc.
## Updating our fork
Github itself has a document about syncing forks. Read it here: https://help.github.com/articles/syncing-a-fork/
Quick copy/paste list:
cd dev/mautic/mautic
git fetch origin -a -p
@mvanbaak
mvanbaak / aws-libmemcached.log
Created Feb 13, 2017
aws libmemcached 1.0.18 compile error 01
View aws-libmemcached.log
Script started on Mon 13 Feb 2017 10:35:44 PM UTC
[root@yip-app tmp]# git clone https://github.com/awslabs/aws-elasticache-cluster-client-libmemcached.git
Cloning into 'aws-elasticache-cluster-client-libmemcached'...
remote: Counting objects: 1545, done.
Receiving objects: 0% (1/1545)
Receiving objects: 1% (16/1545)
Receiving objects: 2% (31/1545)
Receiving objects: 3% (47/1545)
Receiving objects: 4% (62/1545)
Receiving objects: 5% (78/1545)
View keybase.md

Keybase proof

I hereby claim:

  • I am mvanbaak on github.
  • I am mvanbaak (https://keybase.io/mvanbaak) on keybase.
  • I have a public key whose fingerprint is 2445 523D 2EC9 83CA 4E00 7119 AA00 E07D 71C9 46BD

To claim this, I am signing this object:

You can’t perform that action at this time.