eznj

const int c = 261;
const int d = 294;
const int e = 329;
const int f = 349;
const int g = 391;
const int gS = 415;
const int a = 440;
const int aS = 455;
const int b = 466;
const int cH = 523;

obedmhg

// ==UserScript==
// @name          Append ProjectId BCC
// @description   It will appen the project Id to the project name.
// @version       0.0.1
// @include       /atg/
// @author        Obed Murillo
// @require http://code.jquery.com/jquery-latest.js
// @grant         none
// ==/UserScript==

noahp

Caveats

• NOTE: I had to reboot after doing this to eliminate display artifacts.
• Also, the dock doesn't appear to support using both of the displayport ports simultaneously :'(
• And MST (https://en.wikipedia.org/wiki/DisplayPort#Multi-Stream_Transport_(MST) ) doesn't seem to work on this dock, so you can't daisy chain monitors.

TLDR

1. download driver from http://www.displaylink.com/downloads/ubuntu
2. unpack

reginadiana

Titulo ou Arte do Projeto

renato-zannon

Running the script inside a docker container

If you wish to test whether your docker container won't have issues when the old Root certificate expires, you can run the script inside the container itself.

In order to do this, follow these steps:

1. Download the verify-lets-encrypt.sh script from the gist
2. Bring up your application container as you usually do - with docker-compose up, docker run, via VS Code etc
3. Run docker ps, and look for any application containers that are up; the NAMES column is the easiest for that
4. From the same folder where you've downloaded the script, run docker exec -i /bin/sh < verify-lets-encrypt.sh; this will run the script inside the container