Yes you can do it with pip3
(or pip
).
And it is simple.
Now we assume you have two computers, both have python3 and pip3 installed, and:
hostA
has internet connectionhostB
does not have internet connection
// 3D Dom viewer, copy-paste this into your console to visualise the DOM as a stack of solid blocks. | |
// You can also minify and save it as a bookmarklet (https://www.freecodecamp.org/news/what-are-bookmarklets/) | |
(() => { | |
const SHOW_SIDES = false; // color sides of DOM nodes? | |
const COLOR_SURFACE = true; // color tops of DOM nodes? | |
const COLOR_RANDOM = false; // randomise color? | |
const COLOR_HUE = 190; // hue in HSL (https://hslpicker.com) | |
const MAX_ROTATION = 180; // set to 360 to rotate all the way round | |
const THICKNESS = 20; // thickness of layers | |
const DISTANCE = 10000; // ¯\\_(ツ)_/¯ |
#!/bin/bash | |
NOW=$(date '+%d-%m-%y') | |
BDIR=/opt/mailcow-dockerized/backups/backup-${NOW} | |
mkdir $BDIR | |
MAILCOW_BACKUP_LOCATION=$BDIR /opt/mailcow-dockerized/helper-scripts/backup_and_restore.sh backup all | |
cp /opt/mailcow-dockerized/mailcow.conf $BDIR/. | |
tar -czvf /opt/mailcow-dockerized/backups/backup-${NOW}.tar.gz $BDIR | |
gpg --encrypt --sign -r [email protected] -o /opt/mailcow-dockerized/backups/backup-${NOW}.tar.gz.gpg --passphrase-file /path/to/file --batch --pinentry-mode loopback /opt/mailcow-dockerized/backups/backup-${NOW}.tar.gz | |
scp -P 1337 /opt/mailcow-dockerized/backups/backup-${NOW}.tar.gz.gpg user@host:/home/user/backups/. | |
rm /opt/mailcow-dockerized/backups/backup-${NOW}.tar.gz.gpg |
<# | |
.SYNOPSIS | |
Uses Win32_Fan class to return information about fans in a system. | |
.DESCRIPTION | |
This script first defines some functions to decode various | |
WMI attributed from binary to text. Then the script calls | |
Get-WmiObject to retrieve fan details, then formats that | |
information (using the functions defined at the top of the script. | |
.NOTES |
This gist assumes you are migrating an existing site for www.example.com — ideally WordPress — to a new server — ideally Ubuntu Server 16.04 LTS — and wish to enable HTTP/2 (backwards compatibile with HTTP/1.1) with always-on HTTPS, caching, compression, and more. Although these instructions are geared towards WordPress, they should be trivially extensible to other PHP frameworks, other FastCGI backends, and even non-FastCGI backends (using proxy
in lieu of fastcgi
in the terminal Caddyfile stanza).
Quickstart: Use your own naked and canonical domain names instead of example.com and www.example.com and customize the Caddyfile and VCL provided in this gist to your preferences!
These instructions target Varnish Cache 4.1, PHP-FPM 7.0, and Caddy 0.10. (I'm using MariaDB 10.1 as well, but that's not relevant to this guide.)
#!/usr/bin/env bash | |
set -eufo pipefail | |
SUDO="" | |
if [ "$EUID" -ne 0 ]; then | |
SUDO="sudo" | |
if ! [ -x "$(command -v $SUDO)" ]; then | |
echo "Error: Running script as non-root and $SUDO is not installed. Exiting." >&2 | |
exit 1 |
<html> | |
<head> | |
<title>jQuery add / remove textbox example</title> | |
<script type="text/javascript" src="jquery-1.3.2.min.js"></script> | |
<style type="text/css"> | |
div{ | |
padding:8px; | |
} |