Cyrus Stoller cyrusstoller

Process goes something like this:

bundle update webpacker
rails webpacker:binstubs
yarn upgrade @rails/[email protected] # or 'add' instead of upgrade
yarn upgrade webpack-dev-server@"'3.1.4'  # or 'add' instead of upgrade
yarn add webpack-cli

bundle exec rails webpacker:install # don't do this! the scrpit seems to overwrite the @rails/webpacker version to 3.5.3

OverEncrypt

This is a guide that I wrote to improve the default security of my website https://fortran.io , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.

WARNING: if you mess up settings, lose your certificates, or decide to no longer maintain HTTPS certs, these steps can and will make your domain inaccessible.

I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate secure.example.com domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.

The best resources that I've found for explaining these steps are https://https.cio.gov , https://certificate-transparency.org , and https://twitter.com/konklone

Comprehensions in Python the Jedi way

by Bjørn Friese

Beautiful is better than ugly. Explicit is better than implicit.

-- The Zen of Python

I frequently deal with collections of things in the programs I write. Collections of droids, jedis, planets, lightsabers, starfighters, etc. When programming in Python, these collections of things are usually represented as lists, sets and dictionaries. Oftentimes, what I want to do with collections is to transform them in various ways. Comprehensions is a powerful syntax for doing just that. I use them extensively, and it's one of the things that keep me coming back to Python. Let me show you a few examples of the incredible usefulness of comprehensions.

Ember Best Practices

Some thoughts and ideas on best practices building Ember apps after 2 years building and maintaining 6+ apps. This is less about the obvious best practices, like use ember-cli, and more along the lines of when to use what technique. As with every best practice there are exceptions to every rule.

Ember data

Ember data relationships

Routing

TL;DR

Create a backup:

pg_dumpall > mybackup.sql

Perform the upgrade:

sudo pg_dropcluster 9.4 main --stop

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
Atomic/related changes all in one commit is something worth striving for. Having your dev

	# app/helpers/application_helper.rb
	module ApplicationHelper
	# active_storage_item could be a blob or variant object
	def proxy_url(active_storage_item, options = {})
	options.merge!(host: ENV['ASSETS_HOST']) if ENV['ASSETS_HOST'].present?

	# proxy: 'true' allows you to stil have the original functionality while
	# being able to proxy through a CDN. You've got to ensure that your CDN
	# forwards this param otherwise active storage will always do the default
	# behavior which is a redirect to the service.

	import React from "react";
	import { render } from "react-dom";

	const ParentComponent = React.createClass({
	getDefaultProps: function() {
	console.log("ParentComponent - getDefaultProps");
	},
	getInitialState: function() {
	console.log("ParentComponent - getInitialState");
	return { text: "" };

	# Ensure you have brew cask installed http://caskroom.io
	brew install caskroom/cask/brew-cask

	# Install Docker Toolbox (this will install docker machine and virtualbox)
	brew cask install dockertoolbox

	# Create a linux machine for docker container to run on
	docker-machine create --driver virtualbox default

	# Add ENV variables for the machine to your profile (and restart your terminal)

	#!/bin/bash

	# This script can be used in "run & hope" mode or you can use it as a recipe to
	# do things manually - you probably want the latter if you really care about
	# the data in your databases.
	# Happy hacking
	# /Eoin/

	# Tell bash to stop if something goes wrong
	set -e