Jon Crenshaw jdcrensh

Retro gaming Raspberry Pi

There are many ways to build one, but this is mine!

Note that my build uses RetroPie, which is a highly configurable system. However, there could be a learning curve. This is especially true if you're not familiar with Linux or using the command line when you get into trouble. So keep that in mind! RetroPie is backed by a huge community, so help is usually just a Google search away.

Here's an alternate guide, but I only really used it to help me with overclocking so I could

Sample service script for debianoids

Look at LSB init scripts for more information.

Usage

Copy to /etc/init.d:

# replace "$YOUR_SERVICE_NAME" with your service's name (whenever it's not enough obvious)

Automatically push an updated file whenever it is changed

Linux

Make sure inotify-tools is installed (https://github.com/rvoicilas/inotify-tools)
Configure git as usual
Clone the git repository of interest from github and, if necessary, add file you want to monitor
Allow username/password to be cached so you aren't asked everytime

git config credential.helper store

	#!/bin/sh
	set -x
	set -e
	#
	# Docker build calls this script to harden the image during build.
	#
	# NOTE: To build on CircleCI, you must take care to keep the `find`
	# command out of the /proc filesystem to avoid errors like:
	#
	# find: /proc/tty/driver: Permission denied

	@RestResource(urlMapping = '/LimitProfiling/*')
	global with sharing class LimitProfilingCallout {

	@HttpPost
	global static void callMeMaybe() {
	RestRequest req = RestContext.request;
	RestResponse res = RestContext.response;

	Map<String, Object> data = (Map<String, Object>) JSON.deserializeUntyped(req.requestBody.toString());

	const streamBuffers = require('stream-buffers');
	const archiver = require('archiver');

	const zipDir = (dir) => {
	const output = new streamBuffers.WritableStreamBuffer({
	initialSize: (100 * 1024), // start at 100 kilobytes.
	incrementAmount: (10 * 1024), // grow by 10 kilobytes each time buffer overflows.);
	});
	const archive = archiver('zip');
	archive.on('end', () => {

	/**
	* Compares String concatenation performance vs StringBuilder.
	* At around 21000 iterations, actual time spent is nearly identical. At higher iterations,
	* StringBuilder comes out ahead in less actual time spent and with lower CPU usage. However in
	* lower iterations, concatenation wins both measurements.
	*
	* Another consideration is that the StringBuilder pattern does not seem to affect the heap
	* size limit at all, which could be a bug with Apex profiling.
	*/

	public class Base62 {

	public static final String ALPHABET = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789";

	public static final int BASE = ALPHABET.length();

	private Base62() {}

	public static String fromBase10(int i) {
	StringBuilder sb = new StringBuilder("");

	var sweetAlert = require('sweetalert2');
	sweetAlert('Hello World!', 'It works!', 'success');

	.mtk4 {
	font-style: italic;
	}