Skip to content

Instantly share code, notes, and snippets.

Jason Garber jgarber623

View GitHub Profile
View .sonarwhalrc.md

This configuration works, but doesn't include any rule customization:

{
  "extends": [
    "web-recommended"
  ],
  "formatters": [
    "codeframe"
  ],
View 01-digitalocean-debian-packages.md

The following packages are included by default on a fresh DigitalOcean droplet using Debian 9.3 (stretch):

adduser/now 3.115 all [installed,local]
apt/now 1.4.8 amd64 [installed,local]
apt-utils/now 1.4.8 amd64 [installed,local]
aptitude/now 0.8.7-1 amd64 [installed,local]
aptitude-common/now 0.8.7-1 all [installed,local]
base-files/now 9.9+deb9u3 amd64 [installed,local]
base-passwd/now 3.5.43 amd64 [installed,local]
View pine64-ubuntu-packages.md

The following packages are included by default on a fresh installation of Ubuntu Xenial using ayufan-pine64's xenial-minimal-pine64-bspkernel-0.7.18-117.img.xz image:

adduser/xenial,now 3.113+nmu3ubuntu4 all [installed]
alsa-utils/xenial,now 1.1.0-0ubuntu5 arm64 [installed]
apt/xenial-updates,now 1.2.24 arm64 [installed]
apt-utils/xenial-updates,now 1.2.24 arm64 [installed]
base-files/xenial-updates,now 9.4ubuntu4.5 arm64 [installed]
base-passwd/xenial,now 3.5.39 arm64 [installed]
bash/xenial-security,xenial-updates,now 4.3-14ubuntu1.2 arm64 [installed]
View chip-debian-packages.md

The following packages are included by default on a fresh installation of Debian Jessie using the official C.H.I.P. "headless" 4.4 image:

acl/now 2.2.52-2 armhf [installed,local]
adduser/now 3.113+nmu3 all [installed,local]
alsa-utils/now 1.0.28-1 armhf [installed,local]
apt/now 1.0.9.8.2 armhf [installed,local]
apt-utils/now 1.0.9.8.2 armhf [installed,local]
avahi-autoipd/now 0.6.31-5 armhf [installed,local]
avahi-daemon/now 0.6.31-5 armhf [installed,local]
View pine64-debian-packages.md

The following packages are included by default on a fresh installation of Debian Stretch using ayufan-pine64's stretch-minimal-pine64-bspkernel-0.7.19-118.img.xz image:

adduser/stable,now 3.115 all [installed]
alsa-utils/stable,now 1.1.3-1 arm64 [installed]
apt/now 1.4.7 arm64 [installed,upgradable to: 1.4.8]
apt-transport-https/now 1.4.7 arm64 [installed,upgradable to: 1.4.8]
apt-utils/now 1.4.7 arm64 [installed,upgradable to: 1.4.8]
avahi-daemon/stable,now 0.6.32-2 arm64 [installed]
base-files/stable,now 9.9+deb9u1 arm64 [installed,upgradable to: 9.9+deb9u2]
View microformats-ruby-logo.svg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View keybase.md

Keybase proof

I hereby claim:

  • I am jgarber623 on github.
  • I am jgarber623 (https://keybase.io/jgarber623) on keybase.
  • I have a public key ASDDFKTabL_Tvexkbp-wE5Ee3X6LvbPTenhQJflrjb6KUwo

To claim this, I am signing this object:

View firefox-service-worker.md

Reproducing an odd bug in Firefox 44 (stable) on OS X El Capitan related to browser cache and Service Workers.

Enabled Add Ons:

With browser cache enabled

  1. Unregister Service Workers in about:serviceworkers.
@jgarber623
jgarber623 / asset-pipeline.md
Last active Aug 29, 2015
Answering some of @mrmrs_ questions about Rails' Asset Pipeline
View asset-pipeline.md

I'd like to have an easily modular and configurable build system with proper logs set up. Seems non-trivial.

I'm not totally sure what you have in mind. Can you expand on what you mean by "configurable build system with proper logs"…?

I'd also like visibility into how these includes work and where some of the imported third party stuff actually comes from.

Ah, yes. The Asset Pipeline's load paths situation is a bit of black magic. To my knowledge, there are at least four places a Rails app will look for assets:

  1. In gems (e.g. Compass, Breakpoint, etc.). This is the least obvious since the files you want to include don't appear in the folder structure of your project. You simply include them in, say application.css.scss by doing @import 'breakpoint';.
  2. In lib/assets.
You can’t perform that action at this time.