Brad Clark bdashrad

Brew Bundle Brewfile Tips

Copyright & License

Unless otherwise noted (either in this file or in a file's copyright section) the contents of this gist are Copyright ©️2020 by Christopher Allen, and are shared under spdx:Creative Commons Attribution Share Alike 4.0 International (CC-BY-SA-4.) open-source license.

Sponsor

If you more tips and advice like these, you can become a monthly patron on my GitHub Sponsor Page for as little as $5 a month; and your contributions will be multipled, as GitHub is matching the first $5,000! This gist is all about Homebrew, so if you like it you can support it by donating to them or becoming one of their Github Sponsors.

Questions to ask your interviewer

Management

What problem do you solve and why would I give you money to solve it?
When’s the last time someone went above and beyond the call of duty at the company/on the team? What did they do?
What are the current goals that the company is focused on, and how does this team/role work to support hitting those goals?
What are the projects in this company you think are really key to its future and how would a motivated person go about getting on them?
What do you see as your largest technical challenge currently?
Pain Points beyond headcount
What is a project you wish a new member of the team could take on?

About

This gist will show how to setup Raspbian Stretch as a headless Bluetooth A2DP audio sink. This will allow your phone, laptop or other Bluetooth device to play audio wirelessly through a Rasperry Pi.

Motivation

A quick search will turn up a plethora of tutorials on setting up A2DP on the Raspberry Pi. However, I felt this gist was necessary because this solution is:

Automatic & Headless - Once setup, the system is entirely automatic. No user iteration is required to pair, connect or start playback. Therefore the Raspberry Pi can be run headless.
Simple - This solution has few dependencies, readily available packages and minimal configuration.
Up to date - As of December 2017. Written for Raspbian Stretch & Bluez 5.43

Prerequisites

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

Extracting Emoji From Slack!

Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.

If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3

HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.

Follow along...

#A script to post back to Slack via the webhooks API

##why this exists?

Slack's own hubot adapter needs the hubot installation to be accessible via web. This can be problematic in some cases, as a security risk.

This hack let's you run your Hubot behind a firewall, and connect to Slack via the IRC gateway.

To respond, Hubot uses the incoming webhooks end-point of Slack.

	name: CI

	# This workflow will purposely fail a check, then change that status to success.
	# It will then approve and merge itself when a PR has been created.
	# This is certainly not something you should usually do and I take no responsibility for how it's used.
	# This is for informational purposes only.

	on:
	# Triggers the workflow on pull request events but only for the main branch
	pull_request:

	# Copyright (C) 2018 Jameel Al-Aziz
	# Modified for simplicification and use within CoreOS.
	#
	# Copyright (C) 2006-2016 Amazon.com, Inc. or its affiliates.
	# All Rights Reserved.
	#
	# Licensed under the Apache License, Version 2.0 (the "License").
	# You may not use this file except in compliance with the License.
	# A copy of the License is located at
	#

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	input {
	elasticsearch {
	hosts => [ "HOSTNAME_HERE" ]
	port => "9200"
	index => "INDEXNAME_HERE"
	size => 1000
	scroll => "5m"
	docinfo => true
	scan => true
	}