Carlos Araya caraya

Realtime Database triggers with Cloud Functions for Firebase - source

This gist contains the source code in my video series about Realtime Database triggers. You can watch the three parts here:

Part 1 (intro, onCreate)
Part 2 (onUpdate, infinite loops)
Part 3 (onDelete, transactions)

index.ts contains the Cloud Functions code, and dialog.ts contains the script to run

running:

bash create-vod-hls.sh beach.mkv

will produce:

    beach/
      |- playlist.m3u8
 |- 360p.m3u8

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
It is free, with no quotas.
Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.

	<?php
	/**
	* Plugin Name: Scripts-To-Footer Exclude AMP
	* Description: Exclude all AMP scripts from being moved to the footer by the Scripts To Footer plugin. All AMP scripts have async anyway so they do not need to be moved to the footer for performance.
	* Author Name: Weston Ruter
	* Plugin URI: https://gist.github.com/westonruter/90c8cbfd9cb4d3882a461b5e71aa10e5
	* Gist Plugin URI: https://gist.github.com/westonruter/90c8cbfd9cb4d3882a461b5e71aa10e5
	*/

	add_filter( 'stf_exclude_scripts', function( $scripts ) {

	const observer = new PerformanceObserver((list) => {
	for (const entry of list.getEntries()) {
	// `name` will be either 'first-paint' or 'first-contentful-paint'.
	const metricName = entry.name;
	const time = Math.round(entry.startTime + entry.duration);

	ga('send', 'event', {
	eventCategory: 'Performance Metrics',
	eventAction: metricName,
	eventValue: time,

	ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
	brew install caskroom/cask/brew-cask
	brew cask install google-chrome
	ln -sf ~/Applications/Google\ Chrome.app /Applications
	brew cask install megasync
	ln -s '/opt/homebrew-cask/Caskroom/megasync/latest/MEGAsync.app' '/Applications/MEGAsync.app'
	brew cask install dropbox
	brew cask install google-drive
	brew cask install iterm2
	brew cask install spectacle

	The only requirements for popup footnotes in iBooks are:
	* Ebook has to be an EPUB3
	* epub:type "noteref" and "footnote"

	So you can link to a totally separate document, as you normally would for endnotes,
	but include the attributes so the <a> link behaves differently in iBooks, instead triggering the popup.

	Original reference link would look something like this (in a file called ch001.html):

	<a epub:type="noteref" href="footnote.html#note1">1</a></div>

	<!doctype html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	</head>
	<body>
	<div class="viewport"></div>

	<script src="//cdnjs.cloudflare.com/ajax/libs/three.js/r58/three.min.js"></script>
	<script src="//threejs.org/examples/js/controls/OrbitControls.js"></script>

	var data = "do shash'owania";
	var crypto = require('crypto');
	crypto.createHash('md5').update(data).digest("hex");

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<title>Test</title>
	<style>
	.slogan span:nth-child(odd) {
	color: red;
	}
	</style>
	</head>