<div class="cta-map-container"> | |
<!-- REMOVE THIS SECTION BELOW?--> | |
<a id="img_map" href="/ADD-HYPERLINK-HERE"><img src="http://news.cliniccompare.co.uk/sites/default/files/filemanager/UK%20Taboola%20Map%204.png" alt="UK map"></a> | |
<!-- REMOVE THIS SECTION ABOVE?--> | |
<svg version="1.1" id="svg_map" xmlns="http://www.w3.org/2000/svg" xmlns:x="&ns_extend;" xmlns:i="&ns_ai;" xmlns:graph="&ns_graphs;" x="0px" y="0px" viewBox="125 -1112 1450.9 2375" xml:space="preserve" width="305px" height="500px"> | |
<metadata id="metadata211"> | |
<sfw xmlns="&ns_sfw;"> | |
<slices></slices> |
module DeepGroup | |
class Grouping | |
IDENTITY = -> v { v } | |
def initialize(state) | |
@state = state | |
@groupings = [] | |
@mapping = IDENTITY | |
end |
- 13" Macbook Pro 3.3 GHz i7 (late 2016)
- Microsoft Surface Book (2016)
- Dell up3216q 32" monitor
class AddFieldsToDelayedJobs < ActiveRecord::Migration | |
def change | |
add_column :delayed_jobs, :signature, :string, index: true | |
add_column :delayed_jobs, :args, :text | |
end | |
end |
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 |
I don't like Sprockets, but it's the easiest and best choice for lots of Ruby on Rails projects. When looking for a better way to manage my JavaScript assets and an improved developer story, my current tool of choice is webpack. While I wish Rails supported drop-in asset pipelines the way that Phoenix does, it's not hard to use webpack with Rails.
A quick note on how I'm currently handling Blue/Green or A/B deployments with Terraform and AWS EC2 Auto Scaling.
In my particular use case, I want to be able to inspect an AMI deployment manually before disabling the previous deployment.
Hopefully someone finds this useful, and if you have and feedback please leave a comment or email me.
I build my AMI's using Packer and Ansible.
In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.
At the moment GraphQL allows 2 types of queries:
query
mutation
Reference implementation also adds the third type: subscription
. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.
page.execute_script("$('.selectize-input input').val('ber')") | |
sleep 0.5 | |
page.execute_script("$('.selectize-input input').keyup()") | |
sleep 0.5 | |
page.execute_script("$('.full-name').mousedown()") | |
# https://github.com/brianreavis/selectize.js/blob/master/src/selectize.js |