Minikube requires that VT-x/AMD-v virtualization is enabled in BIOS. To check that this is enabled on OSX / macOS run:
sysctl -a | grep machdep.cpu.features | grep VMX
If there's output, you're good!
###Sketch trial non stop
Open hosts files:
$ open /private/etc/hosts
Edit the file adding:
127.0.0.1 backend.bohemiancoding.com
127.0.0.1 bohemiancoding.sketch.analytics.s3-website-us-east-1.amazonaws.com
Within GitHub it is possible to set up two types of SSH key - account level SSH keys and and repository level SSH keys. These repository level SSH keys are known in GitHub as deploy keys.
Deploy keys are useful for deploying code because they do not rely on an individual user account, which is susceptible to change, to “store” the server keys.
There is, however, an ‘issue’ with using deploy keys; each key across all repositories on GitHub must be unique. No one key can be used more than once. This becomes a problem when deploying to repositories to the same server with the same user. If you create two keys, the SSH client will not know which key to use when connecting to GitHub.
One solution is to use an SSH config file to define which key to use in which situation. This isn’t as easy as it seems.. you might try something like this:
At FreightHub, we’re building the backbone of global trade. We are revolutionizing logistics by making it easier, faster, and more cost efficient to move goods from any point A to point B in the world – on container ships, airplanes, trucks and trains. By radically automating processes and designing for a superior user experience we make buying and selling goods anywhere on the globe as efficient as never before.
If you want to create impact with your work, solve real-world problems, and digitize a multi-trillion-€ industry that fosters global prosperity, we’d love you to join FreightHub!
import subprocess | |
import os | |
import re | |
import sys | |
import argparse | |
import httplib, urllib | |
import time | |
""" | |
# place this file at /home/ethos/check_hash_reboot.py |
function BINANCE_PRICE(coinsymbol, pair) { | |
var url = "https://api.binance.com/api/v3/ticker/price?symbol="+coinsymbol.toUpperCase()+pair.toUpperCase() | |
var response = UrlFetchApp.fetch(url, {'muteHttpExceptions': true}); | |
var json = response.getContentText(); | |
var data = JSON.parse(json); | |
return data.price | |
} | |
/* |
#!/usr/bin/env python3 | |
import os | |
# 1. Save this file in /home/ethos/monitor.py on your ethOS | |
# 2. Change permission to make it executable | |
# chmod 0755 /home/ethos/monitor.py | |
# 3. Run crontab | |
# # crontab -e | |
# 4. Schedule a cron task to execute every 5 minutes | |
""" |
Accessing a subnet that is behind a WireGuard client using a site-to-site setup
We want to access a local subnet remotely, but it is behind a NAT firewall and we can't setup port forwarding. Outgoing connections work, but all incoming connections get DROPPED by the ISP's routing policy.
#!/bin/bash | |
# This script install kafka 2.2.0 | |
# on a centos 7 machine | |
## RUN AS SUDO | |
if [[ $EUID -gt 0 ]] | |
then | |
echo "Please run as root/sudo" | |
exit 1 | |
fi |