ajayfroiden

#!/bin/bash
set -euo pipefail
IFS=$'\n\t'

# Ubuntu 20.04 dev Server
# Run like (without sudo) - bash install_lamp.sh
# Script should auto terminate on errors

export DEBIAN_FRONTEND=noninteractive

cooclsee

Proxmox - SPICE client setup for MacOS

1. Install a working (and compiled) version of virt-viewer. You may view the homebrew package's upstream source on GitHub.

   brew tap jeffreywildman/homebrew-virt-manager
   brew install virt-viewer

2. Once that's installed should be able make a call remote-viewer with a pve-spice.vv file downloaded from proxmox web interface

csantanapr

set -e, -u, -o pipefail

The "set" lines These lines deliberately cause your script to fail. Wait, what? Believe me, this is a good thing. With these settings, certain common errors will cause the script to immediately fail, explicitly and loudly. Otherwise, you can get hidden bugs that are discovered only when they blow up in production.

set -euo pipefail is short for:

set -e
set -u

richardlampitt

.glyphicon {
  font-family: "fontawesome";

  &.glyphicon-chevron-up {
  .fa-chevron-up();
  }
  &.glyphicon-chevron-right {
  .fa-chevron-right();
  }
  &.glyphicon-chevron-left {

blowsie

$fa-font-path: "~font-awesome/fonts";
@import '~font-awesome/scss/font-awesome';

.glyphicon {
  @extend .fa;
  &.glyphicon-asterisk {
    @extend .fa-asterisk;
  }
  &.glyphicon-plus {
    @extend .fa-plus;

cfxd

.wp-video, video.wp-video-shortcode, .mejs-container, .mejs-overlay.load {
	width: 100% !important;
	height: 100% !important;
}
.mejs-container {
	padding-top: 56.25%;
}
.wp-video, video.wp-video-shortcode {
	max-width: 100% !important;
}

Synchro

<?php
/**
 * This is an example of a practical encoder and decoder for base-62 data in PHP
 * It differs from the majority of examples in that it's fast enough for moderate data sizes, unlike multiprecision converters
 * To be practical, base-62 encoding needs to use internal chunking and padding because base-62 does not fit exactly into any integral number of bits
 * This means the output is not quite compatible with multiprecision conversions,
 * but the encoded data retains all the desirable properties of base-62, so (unlike any base-64 encoding) it's URL, DNS, email address and pathname safe
 * @author     Marcus Bointon <[email protected]>
 * @copyright  2011 Marcus Bointon
 * @license    http://www.opensource.org/licenses/mit-license.html MIT License