Discover gists

Manually upgrade OpenSSH on OS 10.9.x

NOTE: Installation and testing was done on a clean Mavericks (OS 10.9) installation

Install Brew:

Install Homebrew prereqs:

xcode-select --install

Install Homebrew

Complete Recent Discord Quest

Note

This no longer works in browser!

Note

This no longer works if you're alone in vc! Somebody else has to join you!

How to use this script:

Accept the quest under User Settings -> Gift Inventory

Transparent Restaurant Backend

In this task, you're going to implement a REST API for a interacting with a menu of a restaurant. The menu is given to you as a JSON file which you will parse and perform operations on. The required features will be listed below.

Description

In this restaurant, honesty is extremely promoted. So extreme, that the restaurant declares that differing quality of ingredients are used in their meals. Like that's not enough, it also allows the customers to choose the ingredients of each meal in different qualities. Each ingredient has the following quality levels:

low: the cheapest
medium: moderate

Install Zsh and Oh-my-zsh on CentOS 7

Based on this article

ALL INSTALLATIONS ASSUME YES WHEN PROMPTED, that's what -y does

This script can be copy paste to ssh as is. No hands installation. :-)

yum install zsh -y

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

A Typical directory structure for running tests using `unittest`

Ref : stackoverflow

The best solution in my opinion is to use the unittest [command line interface][1] which will add the directory to the sys.path so you don't have to (done in the TestLoader class).

For example for a directory structure like this:

new_project

├── antigravity.py

	#!/bin/sh
	# Reset Parallels Desktop's trial and generate a casual email address to register a new user
	rm /private/var/root/Library/Preferences/com.parallels.desktop.plist /Library/Preferences/Parallels/licenses.xml
	jot -w pdu%d@gmail.com -r 1

	# .conkyrc

	background yes
	use_xft yes
	xftfont Droid:normal:size=10
	xftalpha 1
	update_interval 1.0
	top_cpu_separate true
	total_run_times 0
	own_window yes

	#!/bin/bash
	#
	# * For DSM v7.x *
	#
	# How to use this script:
	# 1. Get your 3 PEM files ready to copy over from your local machine/update server (privkey.pem, fullchain.pem, cert.pem)
	# and put into a directory (this will be $CERT_DIRECTORY).
	# Personally, I use this script (https://gist.github.com/catchdave/3f6f412bbf0f0cec32469fb0c9747295) to automate steps 1 & 4.
	# 2. Ensure you have a user setup on synology that has ssh access (and ssh access is setup).
	# This user will need to be able to sudo as root (i.e. add this line to sudoers, <USER> is the user you create):

	# This is a anonymized version of the script I use to renew all my SSL certs
	# across my servers. This will not work out of the box for anyone as your network will be
	# different. But may be useful starting place for others.
	#
	# I use a cronjob that runs this every week. It only replaces certificates when a certificate has been renewed.

	# Renews/creates cert from letsencrypt & places it where it needs to be.
	# Currently, that is:
	# * Nginx (local for plex)
	# * Plex Media Server