Chris Born pelted

Stimulus cheatsheet

Website: https://stimulusjs.org/
GitHub repo: https://github.com/stimulusjs/stimulus
Handbook: https://stimulusjs.org/handbook/introduction
Discourse: https://discourse.stimulusjs.org/

Lifecycle callbacks

initialize: once, when the controller is first instantiated
connect: anytime the controller is connected to the DOM

Chapter 1. Models

The Model layer should also contain the business logic of your application.

ANTIPATTERN: VOYEURISTIC MODELS

Class: A class defines the characteristics of an object, including the details of what it is (its attributes) and what it can do (its methods).

Method: A method exists on a class and defines what the class can do.

Encapsulation: Ideally, the code for a class should be relatively self-contained through encapsulation, which is the concealment of functional details of a class from the other objects that call its methods. This is typically done by limiting the methods other objects are allowed to call and exposing a public interface through which an object is exposed to the world. In Ruby, this is done with the public, protected, and private keywords.

Cheat Sheet: Simple Authentication in Rails 6 with `has_secure_password`

The goal of this cheatsheet is to make it easy to add hand-rolled authentication to any rails app in a series of layers.

First the simplest/core layers, then optional layers depending on which features/functionality you want.

`Specs`
AUTHOR	Ira Herman
LANGUAGE/STACK	Ruby on Rails Version 4, 5, or 6

Thoughts about Rails Presenters

This is a collection of links, examples and rants about Presenters/Decorators in Rails.

The "Decorator" pattern slowly started gaining popularity in Rails several years ago. It is not part of core Rails, and there's many different interpretations about how it should work in practice.

Jay Fields wrote about it in 2007 (before he switched back to Java and then Clojure): http://blog.jayfields.com/2007/03/rails-presenter-pattern.html

	name: build

	on: [push, pull_request]

	jobs:
	build:
	runs-on: ubuntu-latest

	steps:
	- uses: actions/checkout@v1

	# Some very helpful asserts to add on top of MiniTest, includes ordered array
	# and set comparison, ActiveRecord attribute validation, and layout assertions
	# This was originally written by @madrobby for Freckle: https://letsfreckle.com

	module MiniTest
	module Assertions
	def assert_layout(layout, message=nil)
	assert_equal "layouts/#{layout}", @response.layout, message
	end

	# Based on https://gist.github.com/1205828, in turn based on https://gist.github.com/1182136
	class BootstrapLinkRenderer < ::WillPaginate::ActionView::LinkRenderer
	protected

	def html_container(html)
	tag :div, tag(:ul, html), container_attributes
	end

	def page_number(page)
	tag :li, link(page, page, :rel => rel_value(page)), :class => ('active' if page == current_page)

	require "rest-client"

	begin
	exists = RestClient.head("http://google.com").code == 200
	rescue RestClient::Exception => error
	exists = (error.http_code != 404)
	end

	puts "exists=#{exists}"

	# This should be run on a new Linode Ubuntu 32-bit 10.04 image as root to prepare it for Nginx, PHP, MySQL, Node, CouchDB environment

	# To start, something like this works:
	# scp prepare_server.sh [email protected]:/root

	# First, install basic linux utilities (compilers, git, libssl)

	cd /root
	mkdir /src
	cd src