… subimage

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

If you're running a Rails app in Google App Engine's flexible environment, it takes a bit of setup to get to a rails console attached to your deployed environment. I wanted to document the steps for my own reference and also as an aid to others.

Open the Google App Engine -> instances section of the Google Cloud Platform (GCP) console.
Select the "SSH" drop-down for a running instance. (Which instance? Both of my instances are in the same cluster, and both are running Rails, so it didn't matter for me. YMMV.) You have a choice about how to connect via ssh.
1. Choose "Open in browser window" to open a web-based SSH session, which is convenient but potentially awkward.
2. Choose "View gcloud command" to view and copy a gcloud command that you can use from a terminal, which lets you use your favorite terminal app but may require the extra steps of installing the gcloud command and authenticating the gcloud command with GCP.

When should you use DateTime and when should you use Time?

It's a common misconception that [William Shakespeare][1] and [Miguel de Cervantes][2] died on the same day in history - so much so that UNESCO named April 23 as [World Book Day because of this fact][3]. However because England hadn't yet adopted [Gregorian Calendar Reform][4] (and wouldn't until [1752][5]) their deaths are actually 10 days apart. Since Ruby's Time class implements a [proleptic Gregorian calendar][6] and has no concept of calendar reform then there's no way to express this. This is where DateTime steps in:

>> shakespeare = DateTime.iso8601('1616-04-23', Date::ENGLAND)
=> Tue, 23 Apr 1616 00:00:00 +0000
>> cervantes = DateTime.iso8601('1616-04-23', Date::ITALY)
=> Sat, 23 Apr 1616 00:00:00 +0000

Ember.Console

This is a set of helpers for finding the application's currently active models/routes/controllers/etc. This isn't a straightforward process because of how Ember (rightly) encapsulates application objects, but it's useful in debugging environments to be able to quickly access them. And with the beta release of Ember Data, the store is not easily accessible without helpers either.

Usage

All helpers can be called directly if you provide them an application instance:

	# Rails production setup via SQLite3 made durable by https://litestream.io/
	# Copy this to Dockerfile on a fresh rails app. Deploy to fly.io or any other container engine.
	#
	# try locally: docker build . -t rails && docker run -p3000:3000 -it rails
	#
	# in production you might want to map /data to somewhere on the host,
	# but you don't have to!
	#
	FROM ruby:3.0.2

	#!/usr/bin/env sh
	# Steps to fix Atom not updating properly on Mac OS, as described at
	# https://discuss.atom.io/t/i-am-unable-to-update-to-the-latest-version-of-atom-on-macos-how-do-i-fix-this/40054

	dirs=(/Applications/Atom.app/ ~/Library/Caches/com.github.atom.ShipIt ~/Library/Application\ Support/com.github.atom.ShipIt)

	for dir in "${dirs[@]}"; do
	echo "$dir"
	if [ -d "$dir" ]; then
	echo "Exists: $dir"

	#!/bin/bash

	apt-get install libxml2-dev libssl-dev libffi-dev libxslt1-dev python-dev libjpeg-dev
	pip freeze --local >pipfreeze.txt
	tr '\n' ' ' < pipfreeze.txt >pipfreeze2.txt
	pip install --upgrade --force-reinstall `cat pipfreeze2.txt`

	#!/usr/bin/env ruby

	toc = "# Table of Contents\n"
	newmd = ""

	ARGF.each_line do \|line\|
	newmd << line
	next if !line.start_with?("#")

	heading = line.gsub("#", "").strip



	var BackboneAdapterMethods = {
	hide : function(){
	this.invoke('hide');
	},
	attr : function(map){
	this.invoke('writeAttribute',map);
	},
	text: function() {

	module Fixtures
	#
	# Set up fixtures that will be defined once during startup
	# and (perhaps) rolled back at the beginning of each test run
	#
	def fixtures &block
	if block_given?
	instance_eval &block
	@fixtures = {}
	(instance_variables - [:@fixtures]).each do \|fresh\|