matt2005

"""
Copyright 2019 Jason Hu <awaregit at gmail.com>

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

ftuyama

// Access Volume Monitor: https://agile-cliffs-23967.herokuapp.com/binance

// Copy and past on chrome console:

var audio = new Audio("/static/beep.wav");
var audioCtx = new AudioContext();
var source = audioCtx.createMediaElementSource(audio);

// create a gain node
var gainNode = audioCtx.createGain();

AlexAtkinson

FOO_ENV Environment Variables

These variables, such as $GITHUB_ENV, $ENV0_ENV, etc., simply point at a file that is sourced to populate an environment with the contained code, much like a .bashrc file.

These enviornment variables, while convenient, present a great amount of difficulty if they're not understood. Errors like ambiguous redirect, or no such file or directory, are common. In the worst case they get deleted, in which case they'll have to be re-created with the default content.

Beyond the simple foobars that users might have with this convenience utility, they also present an additional challenge in that they may persist data that is deisrable to delete. Clearing this data is another challenge. See below for more.

Demo