roppa

package crypto

import (
	"crypto/sha256"
)

// NewSHA256 ...
func NewSHA256(data []byte) []byte {
	hash := sha256.Sum256(data)
	return hash[:]

roppa

I am attesting that this GitHub handle roppa is linked to the Tezos account tz1iC7UNquWbwf24kW3sGdVtYCNE5EzmTSkT for tzprofiles

roppa

sudo rm -Rf ~/Library/Caches/com.microsoft.VSCode.ShipIt
sudo rm -Rf ~/Library/Caches/com.microsoft.VSCodeInsiders.ShipIt

roppa

{
	// Place your global snippets here. Each snippet is defined under a snippet name and has a scope, prefix, body and 
	// description. Add comma separated ids of the languages where the snippet is applicable in the scope field. If scope 
	// is left empty or omitted, the snippet gets applied to all languages. The prefix is what is 
	// used to trigger the snippet and the body will be expanded and inserted. Possible variables are: 
	// $1, $2 for tab stops, $0 for the final cursor position, and ${1:label}, ${2:another} for placeholders. 
	// Placeholders with the same ids are connected.
	// Example:
	// "Print to console": {
	// 	"scope": "javascript,typescript",

roppa

/**
Quick POC for game of life. Terrible side effects. Actually doing this in Rust but wanted to quickly knock something out in js
**/
let width = 40

function getCells() {
  return new Array(width * width).fill(false)
}

let cells = getCells()

roppa

#!/bin/bash

for f in $PWD/*;
  do 
    [ -d $f ]
    cd "$f"
    echo $f
    git pull origin master
  done;

roppa

#!/bin/bash

# To run ./repo.sh username
repos=( repo1 repo2 repo3 )
for i in "${repos[@]}"
do
	git clone git@github.com:$1/$i.git
done

roppa

PSQL

Magic words:

psql -U postgres

Some interesting flags (to see all, use -h):

• -E: will describe the underlaying queries of the \ commands (cool for learning!)
• -l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)

roppa

How to setup Let's Encrypt for Nginx on Ubuntu 16.04 (including IPv6, HTTP/2 and A+ SLL rating)

There are two main modes to run the Let's Encrypt client (called Certbot):

• Standalone: replaces the webserver to respond to ACME challenges
• Webroot: needs your webserver to serve challenges from a known folder.

Webroot is better because it doesn't need to replace Nginx (to bind to port 80).

In the following, we're setting up mydomain.com. HTML is served from /var/www/mydomain, and challenges are served from /var/www/letsencrypt.

roppa

npm i -g watch
watch 'npm run test' src