| #!/bin/sh | |
| # Configure homebrew permissions to allow multiple users on MAC OSX. | |
| # Any user from the admin group will be able to manage the homebrew and cask installation on the machine. | |
| # allow admins to manage homebrew's local install directory | |
| chgrp -R admin /usr/local | |
| chmod -R g+w /usr/local | |
| # allow admins to homebrew's local cache of formulae and source files | |
| chgrp -R admin /Library/Caches/Homebrew |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.
This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.
There is a companion feature matrix of various tools. Comments are welcome in the same manner.
| # Ubuntu has a stupid policy of not cleaning up boots because they deem | |
| # unknowable whether a kernel is valid or not (even if booted). Combined with | |
| # the default Ubuntu setup that creates a ridiculously small /boot that is | |
| # bound to be filled in a few months worth of updates, you have a recipe for a | |
| # failure during upgrade, leading to being unable to update or remove anything | |
| # and having to mess with apt and dpkg innards by hand. | |
| # This may work for Debian too. | |
| # This one liner keeps /boot fresh and clean by removing the currently | |
| # running kernel version as well as the latest one (which may not be |
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
apt-get update && apt-get install gdb
| #!/bin/bash | |
| # | |
| # using ec2 tools | |
| # | |
| # Marcus Vinicius Fereira ferreira.mv[ at ].gmail.com | |
| # 2011-11 | |
| ### | |
| ### programs |
| import aiohttp | |
| import asyncio | |
| async def get_body(url): | |
| response = await aiohttp.request('GET', url) | |
| raw_html = await response.read() | |
| return raw_html | |
| async def main(): | |
| # run them sequentially (but the loop can do other stuff in the meanwhile) |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
create different ssh key according the article Mac Set-Up Git
$ ssh-keygen -t rsa -C "[email protected]"
| #!/usr/bin/env python | |
| import sys, os, time | |
| def newest_mtime(path): | |
| """Returns timestamp of newest file under path.""" | |
| newest_time = 0 | |
| for root, dirs, files in os.walk(path): | |
| for fname in files: | |
| mtime = os.stat(os.path.join(root, fname)).st_mtime |