mjul

Fixing GPG "Inappropriate ioctl for device" errors

6th November 2016 Linux 24 Comments https://d.sb/B5N 

    Error: gpg: using "D5673F3E" as default secret key for signing 
    Error: gpg: signing failed: Inappropriate ioctl for device 
    Error: gpg: [stdin]: sign+encrypt failed: Inappropriate ioctl for device

davecoutts

# Install Ubiquiti Unifi Controller on Ubuntu 20.04.
# As tested on a fresh install of ubuntu-20.04.1-live-server, August 22nd 2020.
# Thanks to https://gist.github.com/tmuncks for posting the updated install steps.

sudo apt update
sudo apt install --yes apt-transport-https

echo 'deb https://www.ui.com/downloads/unifi/debian stable ubiquiti' | sudo tee /etc/apt/sources.list.d/100-ubnt-unifi.list
sudo wget -O /etc/apt/trusted.gpg.d/unifi-repo.gpg https://dl.ui.com/unifi/unifi-repo.gpg

jdbohrman

#!/bin/bash -x
export curl
export jq
export RANCHER_IP=34.70.139.14
export CLUSTER_NAME=test-cluster-new
export OUTPUT_DIR=/var/lib/rancher/k3s/server/manifests

while true; do
  curl -sLk https://${RANCHER_IP}/ping && break
  sleep 5

jdbohrman

ssh_authorized_keys:
- github:jdbohrman
write_files:
- encoding: ""
  content: |-
    #!/bin/bash
    mkdir -p '/var/lib/rancher/k3s/server/manifests/'
    curl -L https://gist.githubusercontent.com/jdbohrman/714bb13d8b8404f647174d9132f5f320/raw/de0c3825d03aa84c70f95e7a4445802e53dabddb/call-rancher.yaml >> /var/lib/rancher/k3s/server/manifests/call-rancher.yaml
  owner: root
  path: /etc/rc.local

msurguy

Follow this guide to integrate bar chart reports into your Laravel application. Reports like the following come with this guide:

• Total number of Orders by day
• Total number of Users subscribed by day
• etc

The library used for the charts is: http://www.oesmith.co.uk/morris.js/

First put this into your page that will have the reports (in the Blade view) to include Morris library:

taldanzig

Routing tips for VPNs on OS X

When VPNs Just Work™, they're a fantastic way of allowing access to a private network from remote locations. When they don't work it can be an experience in frustration. I've had situations where I can connect to a VPN from my Mac, but various networking situations cause routing conflicts. Here are a couple of cases and how I've been able to get around them.

Specific cases

Case 1: conflicting additional routes.

In this example the VPN we are connecting to has a subnet that does not conflict with our local IP, but has additional routes that conflict in some way with our local network's routing. In my example the remote subnet is 10.0.x.0/24, my local subnet is 10.0.y.0/24, and the conflicting route is 10.0.0.0/8. Without the later route, I can't access all hosts on the VPN without manually adding the route after connecting to the VPN: