JamesChevalier

attr_encrypted is a nice gem for encrypting fields in Rails.

You add this line to a model: attr_encrypted :field_name, key: ENV['attr_encrypted_key']. I used rake secret to generate that attr_encrypted_key referenced in that line.

The field itself needs to be created in a particular way in the migration:

add_column :table_name, :encrypted_field_name,    :text
add_column :table_name, :encrypted_field_name_iv, :text

JamesChevalier

from newspaper import Article

def lambda_handler(event, context):
    url = event['url']
    article = Article(url)
    article.download()
    article.parse()

    return {
        'content' : article.text

JamesChevalier

function getBoundingBox(data) {
  var bounds = {}, coordinates, point, latitude, longitude;

  // Loop through each "feature"
  for (var i = 0; i < data.features.length; i++) {
    coordinates = data.features[i].geometry.coordinates;

    if(coordinates.length === 1){
      // It's only a single Polygon
      // For each individual coordinate in this feature's coordinates...

JamesChevalier

# Create the empty hash
nestable_hash = Hash.new { |hash, key| hash[key] = Hash.new(&hash.default_proc) }

# Populate the hash with multiple levels of data
nestable_hash[:level_one][:level_two][:level_three][:level_four] = 'mic check'
nestable_hash[:level_one][:level_two_a][:level_three_a]          = [1, 2, 1, 2]

# The hash structure is now:
# {
#   level_one: {

JamesChevalier

# template file

# Use a 4096 bit RSA key instead of 2048
# rsa-key-size = 4096

# Register with the specified e-mail address
email = {{ server_admin_email }}

# Generate certificates for the specified domains
domains = {{ domain_name }}

JamesChevalier

• There's a page that displays a list of Posts.
• Each Post in the list links out to its individual Post page.
• Both pages contain a form to add a new Post - this is the Component.
• Additionally, the form can be shown/hidden.

The problem is that the actions need to exist in all possible Routes.

The new-post component bubbles up to whichever Route it's being called in. I'm calling it from the Posts Route, so I need to handle the savePost there... I'm also calling it from the Post Route, so I need to handle the savePost there, as well.

JamesChevalier

console.log('Loading event');
var AWS = require('aws-sdk');
var dynamodb = new AWS.DynamoDB();

exports.handler = function(event, context) {
    console.log("Request received:\n", JSON.stringify(event));
    console.log("Context received:\n", JSON.stringify(context));

    var tableName = "OurBlogDemo";
    var datetime = new Date().getTime().toString();

JamesChevalier

console.log('Loading event');

// Twilio Credentials 
var accountSid = '';
var authToken = '';
var fromNumber = '';

var https = require('https');
var queryString = require('querystring');

JamesChevalier

I'm using Overpass Turbo: http://overpass-turbo.eu/

This is the query I'm using to collect all places that are Admin Level 8 within California:

[out:json];
area['admin_level'='4']['name'='California'];
(relation['admin_level'='8'](area););
out;

JamesChevalier

The scenario here is that you've got a lot of commits on the master branch that should have been committed to a feature branch. You want to reset master back to the last commit, and you don't want to lose your work. The process below is fairly specific to SourceTree.

1. Create a new branch named placeholder at the point that you want to restore to ... This will be deleted later, after everything is confirmed ok.
   • In SourceTree: right click the commit, choose Branch..., name it placeholder, and click Create Branch
   • Push this to origin
2. Create a new branch at your latest commit ... This is the branch that will contain further work, so you should stick to your typical feature branch naming conventions.
   • In SourceTree: switch back to the branch for that latest commit and create a new branch from there

• Push this to origin