erikhansen

See also this alternative approach: https://gist.github.com/cmtickle/8900629447429126ffd7ff84e56ec780#to-patch-code-in-appcode

If you need to patch an M2 extension that isn't available to be installed via Composer, and you're concerned about losing edits directly to files in app/code/<Vendor> directory, you can install and then patch the extension locally using these steps:

1. Copy the extension into an arbitrary folder location like app/code/packages/VendorName/ModuleName (this assumes this module has a composer.json file with the package name of vendorname/module-modulename)

2. Run this command to add your custom package location to the composer repositories list:

   composer config repositories.vendorname/module-modulename path app/packages/VendorName/ModuleName
   

3. Require the extension:

LukeSmithxyz

# Luke's config for the Zoomer Shell

# Enable colors and change prompt:
autoload -U colors && colors
PS1="%B%{$fg[red]%}[%{$fg[yellow]%}%n%{$fg[green]%}@%{$fg[blue]%}%M %{$fg[magenta]%}%~%{$fg[red]%}]%{$reset_color%}$%b "

# History in cache directory:
HISTSIZE=10000
SAVEHIST=10000
HISTFILE=~/.cache/zsh/history

davidalger

# Include gem used for Slack deploy notifications
require 'capistrano/slackify'

# Load custom tasks from `lib/capistrano/tasks` if you have any defined
Dir.glob('lib/capistrano/tasks/*.rake').each { |r| import r }

davidalger

General cheatsheet

• https://tmuxcheatsheet.com/
• https://gist.github.com/MohamedAlaa/2961058

long buffer support

Add the following to ~/.tmux.conf for long buffer support and ability to write to file afterwards:

set-option -g history-limit 250000

perryholden

<?php
/**
 * dangerous_functions.php
 * Perry Holden <perry.holden@gmail.com>
 *
 * Usage: php dangerous_functions.php [type: folder|file] [folder_or_filename]
 * Example: php dangerous_functions.php folder vendor/businessname/module-name
 */

if (!isset($argv[1])) {

erikhansen

#!/bin/bash
# This script crawls all urls in a /sitemap.xml file and loads them, effectively priming the cache
# Usage: ./warm_cache.sh www.example.com

time wget --quiet https://$1/sitemap.xml --output-document - | \
    egrep -o "https?://[^<]+" | \
    grep $1 | \
    grep -v "jpg" | \
    xargs -i -d '\n' curl --output /dev/null --silent --write-out '%{http_code} %{time_total}ms %{url_effective} \n' {}

erikhansen

#!/bin/bash
# stop on errors
set -e
# turn on debugging if you're running into issues
#set -x

# Static variables
ENVIRONMENT=$1
RED='\033[0;31m'
NC='\033[0m' # No Color

CNanninga

#!/bin/bash

SOURCE_DB_NAME="example_prod"
SOURCE_ROOT_DIR="/var/www/prod"
SOURCE_DUMP_FILENAME=example_prod_$(date +%F).sql.gz

TARGET_DB_NAME="example_stage"
TARGET_ROOT_DIR="/var/www/stage"
TARGET_SSH_USER="www-stage"
TARGET_SSH_HOST="stage.example.com"

gboudreau

Generating Authy passwords on other authenticators

---

*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August

---

This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.

davidalger

<?php

header('Cache-Control: private');
phpinfo();