Viktor Evdokimov viktor-evdokimov

Methods of Signing with GPG on MacOS

Last updated June 23, 2022

There are now two ways to approach this:

Using gpg and generating keys
Using Kryptonite by krypt.co

This Gist explains how to do this using gpg in a step-by-step fashion. Kryptonite is actually wickedly easy to use-but you will still need to follow the instructions

require 'csv'
require 'open-uri'

csv_text = open('http://www.vvv.hh.yyy.ggg/~hhhh/uuuu.csv')
csv = CSV.parse(csv_text, :headers=>true)
csv.each do |row|
  puts row
end

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

	#!/bin/sh
	exec 1>&2
	if test $(git diff --cached -S'binding.pry' --name-only \|
	LC_ALL=C tr -d '[ -~]\0' \| wc -c) != 0
	then
	cat <<\EOF
	Remove biniding.pry
	EOF
	exit 1
	fi

	const http = require('http')
	const { run, send, json } = require('micro')
	const PORT = process.env.PORT \|\| 8080
	const response = "Hi from MICROservice on K8S draft"
	const microHttp = fn => http.createServer((req, res) => run(req, res, fn))

	const server = microHttp(async (req, res) => {
	const js = await json(req);
	const statusCode = 200;
	const data = { ...js, response };

	# frozen_string_literal: true
	source "https://rubygems.org"
	git_source(:github) {\|repo_name\| "https://github.com/#{repo_name}" }
	gem "sinatra", "~> 2.0"
	gem "json", "~> 2.1"

	#!/bin/sh

	# Called by "git push" after it has checked the remote status,
	# but before anything has been pushed.
	#
	# If this script exits with a non-zero status nothing will be pushed.
	#
	# Steps to install, from the root directory of your repo...
	# 1. Copy the file into your repo at `.git/hooks/pre-push`
	# 2. Set executable permissions, run `chmod +x .git/hooks/pre-push`

	# Moving to a new branch
	# Unless there are other circumstances involved, this can be easily done by branching and rolling back.
	# Note: Any changes not committed will be lost.

	git branch newbranch # Create a new branch, saving the desired commits
	git reset --hard HEAD~1 # Move master back by 3 commits (GONE from master)
	git checkout newbranch # Go to the new branch that still has the desired commits

	#from https://stackoverflow.com/questions/1628563/move-the-most-recent-commits-to-a-new-branch-with-git

	# return which shell is used
	> echo $0
	-zsh