jkeam

# get database info
heroku config:get DATABASE_URL -a app_name

# dump command
pg_dump --column-inserts --no-acl --no-owner -h host_name -U postgres_user -t table_name --data-only db_name > output_filename.dump

jkeam

# install postgres
sudo apt update
sudo apt install postgresql postgresql-contrib libpq-dev

# login as postgres user
sudo -i -u postgres

# log into psql shell
psql

jkeam

#!/bin/bash

#ifconfig en0 | grep 'inet ' | awk '{print $2}'
ipconfig getifaddr en0

jkeam

#!/bin/sh
#
# usage: getcert.sh remote.host.name [port]
#  eg) getcert.sh api.mailgun.net
#
RHOST=$1
RPORT=${2:-443}

# see cert
echo -n | openssl s_client -connect ${RHOST}:${RPORT} | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'

jkeam

Install These Tools:
https://github.com/pyenv/pyenv
https://github.com/pyenv/pyenv-virtualenv


Then in .zshrc add:
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

jkeam

awk '{printf "%s\\n", $0}' file

jkeam

#!/usr/bin/env ruby
require 'json'
require 'rexml/document'
include REXML

def fix_exshell_json(filename, url)
  json_file = JSON.parse File.read(filename)
  json_file['developmentUrl'] = url
  File.open(filename, 'w') { |file| file.puts(json_file.to_json) }
end

jkeam

digraph SimplestDiagrams {
    Zoo1
    "Zoo1" -> "Cat" 
    "Zoo1" -> "Dog"
    
     Zoo2
    "Zoo2" -> "Cat"
    "Zoo2" -> "Crow"
    
     Zoo3

jkeam

Installing a Gem on Heroku from a Private GitHub Repo

Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.

Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.

This method does not add your OAuth token to Gemfile.lock. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.

1. Generate an OAuth token from GitHub

jkeam

Installing a Gem on Heroku from a Private GitHub Repo

Sometimes you want to use a gem on Heroku that is in a private repository on GitHub.

Using git over http you can authenticate to GitHub using basic authentication. However, we don't want to embed usernames and passwords in Gemfiles. Instead, we can use authentication tokens.

This method does not add your OAuth token to Gemfile.lock. It uses bundle config to store your credentials, and allows you to configure Heroku to use environment variables when deploying.

1. Generate an OAuth token from GitHub