assafshomer

> sudo chmod a+wx utxo.sh
> sudo chmod a+wx address.sh
> sudo chmod a+wx balance.sh

>./balance 1myaddress 

assafshomer

sudo yum install -y git gcc make readline-devel openssl-devel

git clone git://github.com/rbenv/rbenv.git ~/.rbenv
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
echo 'eval "$(rbenv init -)"' >> ~/.bashrc
source ~/.bashrc

# Install ruby-build system-widely
git clone git://github.com/rbenv/ruby-build.git /tmp/ruby-build
cd /tmp/ruby-build

assafshomer

#Model 

@user.should have(1).error_on(:username) # Checks whether there is an error in username 
@user.errors[:username].should include("can't be blank")  # check for the error message 

#Rendering
response.should render_template(:index)

#Redirecting 
response.should redirect_to(movies_path)

assafshomer

#! /usr/bin/env bash

# Insert a USB key.
# if needed initialize it with MS/DOS FAT and MBR

# Download the Mint ISO image
# Convert the ISO -> IMG
hdiutil convert -format UDRW -o linuxmint-18.3-mate-64bit linuxmint-18.3-mate-64bit.iso

# Run a diskutil list to know the device for the USB key, e.g.: /dev/disk3

assafshomer

# Start the RP
# launch a terminal window
# Type the following command and hit `Enter`

bash <(curl -s https://raw.githubusercontent.com/assafshomer/rpcc/master/config-rp/scripts/install-ruby.sh)

# This will take about 15-20 minutes to run. In the end the pi should reboot. 
# When it does, type the next command and hit `Enter` (should take a similar amount of time)

bash <(curl -s https://raw.githubusercontent.com/assafshomer/rpcc/master/config-rp/scripts/install-coincooler.sh)

assafshomer

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step)

   git clone [email protected]

assafshomer

Adding PIXEL to Raspbian Lite

Flash Raspbian Lite as normal. Run raspi-config and setup whatever you would to for console only mode. I usually change password, hostname and activate SSH server as a initial setup.

Adding wifi from console (optional)

sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

assafshomer

#!/bin/bash

# --------------------------------------------------------------------------------------------
# Installs Ruby 2.5 using rbenv/ruby-build on the Raspberry Pi (Raspbian)
# --------------------------------------------------------------------------------------------

# Time the install process
START_TIME=$SECONDS

# Install git + dependencies

assafshomer

#!/bin/bash

# --------------------------------------------------------------------------------------------
# Installs Ruby 2.5 using rbenv/ruby-build on the Raspberry Pi (Raspbian)
#
# Run from the web:
#   bash <(curl -s https://gist.githubusercontent.com/blacktm/8302741/raw/install_ruby_rpi.sh)
# --------------------------------------------------------------------------------------------

# Welcome message

assafshomer

"#{`git rev-parse HEAD`} (commit no. #{`git rev-list --count HEAD`.strip} on '#{`git branch`.split(/\n/).select{|e| e=~/\*/}.first.split(/\s/).last}' branch)"