Daniel Sczepansky danskycode

Google / YouTube Authentication using a Brand Account

Below describes the only way I was able to get (programmatic) access to the YouTube Analytics API on behalf of our Brand Account. Google documentation is convoluted, to say the least, so if you know a more straightforward way, please do share.

Getting a Client ID and Refresh Token

Create a Project in the Developers Console - https://console.developers.google.com/
Go to the Library tab and enable desired APIs (e.g. YouTube Analytics)
Go to OAuth consent screen and make project external. Select Test mode

Unofficial Bash Strict Mode

Sometimes a programming language has a "strict mode" to restrict unsafe constructs. E.g., Perl has use strict, Javascript has "use strict", and Visual Basic has Option Strict. But what about bash? Well, bash doesn't have a strict mode as such, but it does have an unofficial strict mode:

set -euo pipefail

set -e

Effective Modern CMake

Getting Started

For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.

After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft

VideoJS, React and Typescript

WARNING: A work in progress, this is a first attempt at getting VideoJs working in a Typescript and React Enviroment.

This was inspired from the VideoJS React Tutorial - (see also Brightcover Player with React and Typescript)

Prerequistes Using TypeScript-React-Starter: https://github.com/Microsoft/TypeScript-React-Starter

Then npm install packages

README

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.)

	import os
	import sys
	import datetime
	from glob import glob
	from argparse import ArgumentParser

	# settings

	projectNamePrefix = "vlog-"
	presetName = "Default" # You have to define this preset by your self. <----

	<#
	References:
	- https://docs.microsoft.com/en-us/dotnet/api/system.net.websockets.clientwebsocket?view=netframework-4.5
	- https://github.com/poshbotio/PoshBot/blob/master/PoshBot/Implementations/Slack/SlackConnection.ps1
	- https://www.leeholmes.com/blog/2018/09/05/producer-consumer-parallelism-in-powershell/
	#>

	$client_id = [System.GUID]::NewGuid()

	$recv_queue = New-Object 'System.Collections.Concurrent.ConcurrentQueue[String]'

	#cloud-config

	package_update: true

	manage_resolv_conf: true
	resolv_conf:
	nameservers:
	- '8.8.8.8'
	- '8.8.4.4'
	- '1.1.1.1'

	sudo apt install curl gnupg2 ca-certificates lsb-release
	echo "deb http://nginx.org/packages/ubuntu `lsb_release -cs` nginx" \| sudo tee /etc/apt/sources.list.d/nginx.list
	curl -fsSL https://nginx.org/keys/nginx_signing.key \| sudo apt-key add -

	sudo apt update
	NGINX_VERSION=$(apt show nginx \| grep "^Version" \| cut -d " " -f 2 \| cut -d "-" -f 1)
	# take note of the nginx version in the "stable" release. e.g. 1.14.2
	echo NGINX version $NGINX_VERSION
	wget https://hg.nginx.org/pkg-oss/raw-file/default/build_module.sh
	chmod a+x build_module.sh

	<?php
	// This file walks you through the most common features of PHP's SQLite3 API.
	// The code is runnable in its entirety and results in an `analytics.sqlite` file.


	// Create a new database, if the file doesn't exist and open it for reading/writing.
	// The extension of the file is arbitrary.
	$db = new SQLite3('analytics.sqlite', SQLITE3_OPEN_CREATE \| SQLITE3_OPEN_READWRITE);

	// Errors are emitted as warnings by default, enable proper error handling.