Remove package's dependencies (does not remove package):
brew deps [FORMULA] | xargs brew remove --ignore-dependencies
Remove package:
| /* | |
| ERB template chunk from The Feed's display of emails: | |
| <section class="postings postings--feed-style" id="postings" | |
| data-controller="pagination" data-pagination-root-margin-value="40px"> | |
| <%= render partial: "postings/snippet", collection: @page.records, as: :posting, cached: true %> | |
| <%= link_to(spinner_tag, url_for(page: @page.next_param), | |
| class: "pagination-link", data: { pagination_target: "nextPageLink", preload: @page.first? }) unless @page.last? %> | |
| </section> |
| // Tracking cursor position in real-time without JavaScript | |
| // Demo: https://twitter.com/davywtf/status/1124146339259002881 | |
| package main | |
| import ( | |
| "fmt" | |
| "net/http" | |
| "strings" | |
| ) |
| # config/initializers/redis.rb | |
| require 'redis' | |
| # Disables the `flushdb` and `flushall` commands. | |
| class Redis | |
| module DangerousCommands | |
| def flushdb | |
| raise 'This is EXTREMELY DANGEROUS! If you really want to EMPTY THE ENTIRE DATABASE, do it from `redis-cli`.' | |
| # You could call `super` here if you want to allow access in some circumstances. | |
| end |
| if ENV['REDIS_ACCESS_MODE'] == 'readonly' | |
| class Redis | |
| class Client | |
| WRITE_COMMANDS = ::Rails.cache.data.command.map { |a| a[0] if a[2].include?('write') }.compact.to_set.freeze | |
| def process(commands) | |
| if commands.flatten.any? { |c| WRITE_COMMANDS.include?(c.to_s) } | |
| raise NotImplementedError, "REDIS_ACCESS_MODE is set to 'readonly', disallowing writes" | |
| end |
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
| # if you want to monkey patch every controller, put this in initializers/active_admin.rb | |
| ActiveAdmin::ResourceController.class_eval do | |
| include ActiveAdmin::CSVStream | |
| end |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>App title</title> | |
| <% if ActionController::Base.asset_host %> | |
| <link rel="dns-prefetch" href="//<%= ActionController::Base.asset_host %>" /> | |
| <% end %> |
| #!/bin/bash | |
| aptitude -y install expect | |
| // Not required in actual script | |
| MYSQL_ROOT_PASSWORD=abcd1234 | |
| SECURE_MYSQL=$(expect -c " | |
| set timeout 10 |
| // | |
| // Backbone.Rails.js | |
| // | |
| // Makes Backbone.js play nicely with the default Rails setup, i.e., | |
| // no need to set | |
| // ActiveRecord::Base.include_root_in_json = false | |
| // and build all of your models directly from `params` rather than | |
| // `params[:model]`. | |
| // | |
| // Load this file after backbone.js and before your application JS. |