Version: 1.9.8
Platform: x86_64
First, install or update to the latest system software.
sudo apt-get update
sudo apt-get install build-essential chrpath libssl-dev libxft-dev
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
oldContainers="$(docker ps -f "status=exited" | grep -E 'Exited \(.*\) [5-9] h|Exited \(.*\) \d\d h' | awk '{ print $1 }')" | |
echo -e -n "\nRemoving containers older than 4 hours" | |
if [ "$oldContainers" != "" ]; then | |
echo "" | |
docker rm $oldContainers | |
else | |
echo "...none found." | |
fi |
#!/usr/bin/env python | |
import boto3 | |
import argparse | |
class StaleSGDetector(object): | |
""" | |
Class to hold the logic for detecting AWS security groups that are stale. | |
""" | |
def __init__(self, **kwargs): |
# Log into your vault instance if you haven't already | |
vault login root | |
# Enable the transit secret engine | |
vault secrets enable transit | |
# Create a key | |
vault write -f transit/keys/my-key | |
# Read the key, nothing up my sleeves | |
vault read transit/keys/my-key | |
# Write some base64 encrypted data to the transit endpoint | |
vault write transit/encrypt/my-key plaintext=$(base64 <<< "my secret data") |
# start vault in dev mode | |
VAULT_UI=true vault server -dev -dev-root-token-id="password" | |
# write some secrets for our example usage | |
curl --request POST \ | |
--silent \ | |
--header "X-Vault-Token: password" \ | |
--header "Content-Type: application/json" \ | |
--data '{ "options": { "cas": 0 }, "data": { "username": "administrator", "password": "hunter2" } }' \ | |
http://127.0.0.1:8200/v1/secret/data/dev | jq '.' |
""" | |
Get Vault credentials recursively as json. | |
Requirements: requests lib. Run pip to install it: | |
$ pip install requests | |
To run this command: | |
$ python get_credentials.py <initial url> <token> |
#!/bin/bash | |
defaults write com.oracle.workbench.MySQLWorkbench NSRequiresAquaSystemAppearance -bool yes | |
echo "Successfully patched!" | |
echo "Now restart MySQL Workbench to see the Workbench in light theme." | |
#Restart MySQL Workbench after executing this. |
####Rets Rabbit http://www.retsrabbit.com
Rets Rabbit removes the nightmare of importing thousands of real estate listings and photos from RETS or ListHub and gives you an easy to use import and Web API server so you can focus on building your listing search powered website or app.