jaydorsey

require 'base64'

file = File.open('path/to/file.ext', 'rb') # Read the image as binary
base64 = Base64.strict_encode64(file.read) # This gives you a string you can assign to a constant/variable

tmpfile = Tempfile.new(Base64.strict_decode64(base64)) # Decode and create a temporary file

Digest::MD5.file(tmpfile).base64digest # This is one way to create a checksum on the file
File.size(tmpfile) # You can also get a file size

jaydorsey

# frozen_string_literal: true

class MyStuff
  OOPS = 'Oops'
  
  def self.call
    Rails.logger.warn { OOPS }
  end
end

jaydorsey

# Lines marked with pry are just for testing in a rails console

require 'rspec/mocks' # pry
include RSpec::Mocks::ExampleMethods # pry

# This bypasses the warning that the method isn't called inside of a test
RSpec::Mocks.with_temporary_scope do # pry
  stub_const(
    'MyClass',
    instance_double(

jaydorsey

# An example of class/instance methods w/ modules
module Foo
  def self.included(base)
    base.extend(ClassMethods)
  end

  def foo
    puts 'Bar.new.foo prints this'
  end

jaydorsey

# these are examples; maybe not the right flags
gem install ffi -v '1.12.2' -- -- with-cflags="-Wno-error=implicit-function-declaration"
bundle config build.ffi --with-cflags=\"-Wno-error=implicit-function-declaration\"

jaydorsey

This is a strategy I use to find unused code in ruby projects. These instructions are for macOS, but you only need access to the tools for this to work.

1. Install unused following the instructions here
2. Install universal-ctags. I use the brew instructions here
3. Generate your tag file from your project root, including your library methods as well. I typically run /usr/local/bin/ctags . $(bundle list --paths) to add all of my library methods for the project. This has some other benefits, like allowing code-jumping in vim

   Bonus: You can set this command up as a git hook to run every time you make changes to your code locally. I have an example of this here

4. Once this command is done, you can look at the tags file in your repository root to make sure it's populated with data correctly (`cat tags | w

jaydorsey

---
name: Run Integration Tests

on: [workflow_dispatch]

# .github/workflows/integration.yml
#
# You manually trigger this from your Github actions. Maybe after merging to main, and triggering
# a deploy out to your pre-production environment
#

jaydorsey

# frozen_string_literal: true

# This script uses the platform-api gem to retrieve secrets from Heroku apps, pipelines, and test
# environments. This can be used to generate an inventory of all your secrets, so you can cross-reference
# it to determine if you had any pipeline/test secrets which were compromised as part of the recent
# Heroku breach
#
# I suggest importing these CSVs into a database, adding a couple metadata fields (compromised:boolean, 
# notes:text, environment:string, status:string) and writing some SQL to come up with a list of secrets
# that were re-used across different environments

jaydorsey

If your Gemfile has a privately hosted package referenced similar to this:

gem 'sekret', git: 'https://github.com/my-private-group/sekret.git', branch: 'main'

You may see a prompt when running bundle install, or other bundler commands, to enter your github username & password.

To resolve this, you need to generate a token and add it to your system.

Generating a token

jaydorsey

# frozen_string_literal: true

# db/migrate/20211227213338_create_users.rb
#
# This is an example of what the Users table might have been created as
# or would look like before the migration from a boolean field to an enum
class CreateUsers < ActiveRecord::Migration[7.0]
  def change
    create_table :users do |t|
      t.string :name, null: false