Integrates:
The code below displays a single paginated table with a simple filter.
Inspired by this article
#!/bin/bash | |
# Script location : /srv/bin/npm_backup.sh | |
# npm_home : Location of nginx-proxy-manager installation | |
# backup_target : Folder name for backup | |
npm_home=/srv/nginx-proxy-manager | |
backup_target=/media/Backups/nginx-proxy-manager | |
# Import protected variables | |
source /srv/bin/.env | |
# Create Backup |
import requests | |
from requests.auth import HTTPDigestAuth | |
def get_json(cgi, user, password, headers={'Accept': 'application/json'}): | |
response = requests.get(cgi, auth=HTTPDigestAuth(user, password), headers) | |
response_json = response.json() | |
return response | |
# in the case of Heatmap, if want to get key values, | |
# heatmap_response_json['HeatMap'][0].keys() |
Integrates:
The code below displays a single paginated table with a simple filter.
Inspired by this article
UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker
now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.
Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start
# Install it as a yum package instead of throgh pip (will save you from lots of hassle) | |
# first get epel | |
sudo amazon-linux-extras install epel | |
# then install supervisor | |
sudo yum install supervisor |
Latest News: http://site.api.espn.com/apis/site/v2/sports/football/college-football/news
Latest Scores: http://site.api.espn.com/apis/site/v2/sports/football/college-football/scoreboard
#!/bin/bash | |
# Thanks to all the nice folks @seemoo-lab for making this possible. | |
# See: https://github.com/seemoo-lab/nexmon | |
# This script should be run as root (i.e: sudo ./nexmon.sh) from the /home/pi/ directory! | |
function info { | |
tput bold; | |
tput setaf 3; | |
echo $1; |
Follow these steps to remove all archives from an AWS vault. After this is finished, you will be able to delete the vault itself through the browser console.
This will create a job that collects required information about the vault.
$ aws glacier initiate-job --job-parameters '{"Type": "inventory-retrieval"}' --account-id YOUR_ACCOUNT_ID --region YOUR_REGION --vault-name YOUR_VAULT_NAME
version: '2.1' | |
services: | |
transmission: | |
container_name: transmission | |
image: dperson/transmission | |
restart: unless-stopped | |
depends_on: | |
- plex | |
network_mode: host | |
environment: |
#!/usr/bin/env python | |
# -*- coding: utf-8 -*- | |
# | |
# This is how I used it: | |
# $ cat ~/.bash_history | python bash-to-zsh-hist.py >> ~/.zsh_history | |
import sys | |
import time |