Copy Config Vars from One Heroku App to Another

Bradford Fults — Tue, 17 Sep 2024 14:07:21 +0000

Below is a quick little script I threw together to copy config vars from one Heroku app to another, e.g. when trying to create a staging or test app that [largely] mirrors another.

It relies on a Heroku app.json to specify which config vars are required, combined with a dump of your other app’s config vars via heroku config --shell -a <app-name> >foo.env to get the <env-file> input.

#!/usr/bin/env ruby
# frozen_string_literal: true

require 'json'

# Usage: env-setter <app.json> <env-file> [-a <heroku-app-name>]

app_json_file   = ARGV[0]
env_file        = ARGV[1]
env_var_keys    = []
heroku_app_name = nil

# parse command line -a switch to get Heroku app name
if ARGV.include?('-a')
  heroku_app_name = ARGV[ARGV.index('-a') + 1]
end

# Pull required config vars from app.json
begin
  parsed_json = JSON.parse(File.read(app_json_file))
  env_var_keys = parsed_json['env'].map {|k,v| k if v.is_a?(Hash) && v['required'] }.compact
rescue JSON::ParserError, EOFError
  puts "Error parsing JSON file: #{app_json_file}"
  exit 1
end
# puts "Required config vars from app.json: #{env_var_keys.join(', ')}"

# Pull env vars from env file
begin
  env_vars = Hash[*File.readlines(env_file).map(&:chomp).map { |line| line.split('=', 2) }.flatten]
rescue EOFError
  puts "Error reading env file: #{env_file}"
  exit 1
end
# puts "Loaded env var names from #{env_file}: #{env_vars.keys.join(', ')}"

# Check if any required env vars are missing
missing_vars = env_var_keys - env_vars.keys
if missing_vars.any?
  puts "Missing required env vars from #{env_file}: #{missing_vars.join(', ')}"
  exit 1
end

# Set config vars on Heroku if app name provided
if heroku_app_name
  puts "Setting config vars on Heroku app #{heroku_app_name}..."
  system('heroku', 'config:set', '--app', heroku_app_name, *env_vars.map {|k,v| "#{k}=#{v}" }.flatten)
end

Keybindings in Terminal in VS Code

Bradford Fults — Thu, 16 May 2024 22:35:55 +0000

I’ve been trying to use VS Code’s integrated Terminal function (Ctrl+`) and one of the most annoying things was that some of my long-used keybindings in my shell (used to be bash, now zsh) were not working.

Specifically:

Ctrl+r – Do a reverse command search in the terminal.
Ctrl+a – Move the cursor to the beginning of the current line.
Ctrl+e – Move the cursor to the end of the current line.

I know the latter two originate in Emacs, but I don’t much care about the history as much as I care about matching my 25+ years of muscle memory: I expect the cursor to move and instead I get an ugly ^A or ^E showing up on my terminal line, without any cursor movement.

Anyway, this was a complicated endeavor to figure out, but I resolved it thusly:

Fixing Ctrl+r

~~I updated the VS Code keybinding for Ctrl+r to just allow VS Code to take over the reverse search dialog entirely, which is fine for me:~~

# Command: Open Keyboard Shortcuts (JSON)
{ "key": "ctrl+r", "command": "workbench.action.terminal.runRecentCommand", "when": "terminalFocus"}
# Just kidding: this was slow; see below

Update: I reverted to zsh’s Ctrl+r functionality

Because VSCode’s was horribly slow after a few weeks of commands:

# Command: Open Keyboard Shortcuts (JSON)
{
    "key": "ctrl+r",
    "command": "-workbench.action.openRecent"
}

Fixing Ctrl+a and Ctrl+e

First, I disabled keyboard “chords” in the terminal context because I don’t use chords at all, much less in the Terminal:

# Command: Open User Settings (JSON)
"terminal.integrated.allowChords": false

Then I finally figured out that VS Code is booting my zsh shell with different options from Terminal.app, and thus I needed to explicitly set a mode in my .zshrc:

# ~/.zshrc
set -o emacs

So now I have my Ctrl keybindings back and I can move forward happily with Terminal embedded within VS Code.

DEV Community: Bradford Fults

Copy Config Vars from One Heroku App to Another

Keybindings in Terminal in VS Code

Fixing Ctrl+r

Update: I reverted to zsh’s Ctrl+r functionality

Fixing Ctrl+a and Ctrl+e