bryanbraun

Example Git Branching Diagram

You can use this diagram as a template to create your own git branching diagrams. Here's how:

1. Create a new diagram with diagrams.net (formerly draw.io)
2. Go to File > Open From > URL
3. Insert this url (it points to the xml data below): https://gist.githubusercontent.com/bryanbraun/8c93e154a93a08794291df1fcdce6918/raw/bf563eb36c3623bb9e7e1faae349c5da802f9fed/template-data.xml
4. Customize as needed for your team.

---

HelioCampos

Database migration best practices for Rails

Never ever change data on schema changes! [1]

Use rake tasks to change the data! [1]

This decouples a deployment from completed migrations. Give us control of the data manipulation proccess by encapsulatin it in on place. need to remember to:

1. Run it in one of the ways bellow: a. Add this rake task the deployment script or;

smithclay

Recipe for running strange binaries in AWS Lambda

In general, the command ldd and the environment variable LD_LINKER_PATH is your best friend when running new, untested binaries in Lambda. My process (which I want to get around to automating one day, maybe using Packer), goes like this:

1. Run an EC2 instance with the official AWS Lambda AMI.
2. Get binary you want to run in AWS Lambda running on the instance (either by installing from a package manager or compiling). 
3. Run ldd -v ./the-binary. Note all of the shared libraries it requires. You’ll need to remember these.
4. Copy the binary to your local machine. Upload the binary with your AWS Lambda function code that runs the ldd command inside the handler function using the process execution library from your language of choice. In node, this works just fine: console.log(require('child_process').execSync('ldd -v ./the-binary'))
5. Note any shared libraries that are missing in the function output. Copy those over from the EC2 instance to a direct

EthraZa

SET NAMES utf8;
SET time_zone = '+00:00';
SET foreign_key_checks = 0;
SET sql_mode = 'NO_AUTO_VALUE_ON_ZERO';

CREATE TABLE `cfop` (
  `id` char(4) COLLATE utf8_unicode_ci NOT NULL,
  `descricao` varchar(200) COLLATE utf8_unicode_ci NOT NULL,
  `aplicacao` varchar(530) COLLATE utf8_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`id`)

brianburridge

namespace :json do
  desc "Export all data to JSON files"
  task :export => :environment do
    Rails.application.eager_load!

    ActiveRecord::Base.descendants.each do |model|
      file = File.open(File.join(Rails.root, "db", "export", "#{model.table_name}.json"), 'w')
      file.write model.all.to_json
      file.close
    end

mitchwongho

# Assuming an Ubuntu Docker image
$ docker run -it <image> /bin/bash

rxaviers

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

digitaljhelms

Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

andreyvit

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

jwo

class Api::RegistrationsController < Api::BaseController
  
  respond_to :json
  def create

    user = User.new(params[:user])
    if user.save
      render :json=> user.as_json(:auth_token=>user.authentication_token, :email=>user.email), :status=>201
      return
    else