realies

## qemu_osx_rpi_raspbian_jessie.sh
# Install QEMU OSX port with ARM support
sudo port install qemu +target_arm
export QEMU=$(which qemu-system-arm)

# Dowload kernel and export location
curl -OL \
https://github.com/dhruvvyas90/qemu-rpi-kernel/blob/master/kernel-qemu-4.1.7-jessie
export RPI_KERNEL=./kernel-qemu-4.1.7-jessie

# Download filesystem and export location

## vagrant-cheat-sheet.md

      
              1 file
            
          
              309 forks
            
          
              33 comments
            
          
              649 stars
            
          
                wpscholar
                / vagrant-cheat-sheet.md
            
            
              Last active
              May 28, 2024 06:59
            
              
                Vagrant Cheat Sheet
              
          
    Typing vagrant from the command line will display a list of all available commands.
Be sure that you are in the same directory as the Vagrantfile when running these commands!
Creating a VM


vagrant init           -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.

Starting a VM


vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)


## gstreamer-build.sh
#!/bin/bash --debugger
set -e

BRANCH="master"
if grep -q BCM2708 /proc/cpuinfo; then
    echo "RPI BUILD!"
    RPI="1"
fi

[ -n "$1" ] && BRANCH=$1

## fix-wordpress-permissions.sh
#!/bin/bash
#
# This script configures WordPress file permissions based on recommendations
# from http://codex.wordpress.org/Hardening_WordPress#File_permissions
#
# Author: Michael Conigliaro <mike [at] conigliaro [dot] org>
#
WP_OWNER=www-data # <-- wordpress owner
WP_GROUP=www-data # <-- wordpress group
WP_ROOT=$1 # <-- wordpress root directory

## push_to_github.rb
# Committing changes to a repo via the Github API is not entirely trivial.
# The five-step process is outlined here:
#   http://developer.github.com/v3/git/
#
# Matt Swanson wrote a blog post translating the above steps into actual API calls:
#   http://swanson.github.com/blog/2011/07/23/digging-around-the-github-api-take-2.html
#
# I was not able to find sample code for actually doing this in Ruby,
# either via the HTTP API or any of the gems that wrap the API.
# So in the hopes it will help others, here is a simple function to
	# Install QEMU OSX port with ARM support
	sudo port install qemu +target_arm
	export QEMU=$(which qemu-system-arm)

	# Dowload kernel and export location
	curl -OL \
	https://github.com/dhruvvyas90/qemu-rpi-kernel/blob/master/kernel-qemu-4.1.7-jessie
	export RPI_KERNEL=./kernel-qemu-4.1.7-jessie

	# Download filesystem and export location
	#!/bin/bash --debugger
	set -e

	BRANCH="master"
	if grep -q BCM2708 /proc/cpuinfo; then
	echo "RPI BUILD!"
	RPI="1"
	fi

	[ -n "$1" ] && BRANCH=$1
	#!/bin/bash
	#
	# This script configures WordPress file permissions based on recommendations
	# from http://codex.wordpress.org/Hardening_WordPress#File_permissions
	#
	# Author: Michael Conigliaro <mike [at] conigliaro [dot] org>
	#
	WP_OWNER=www-data # <-- wordpress owner
	WP_GROUP=www-data # <-- wordpress group
	WP_ROOT=$1 # <-- wordpress root directory
	# Committing changes to a repo via the Github API is not entirely trivial.
	# The five-step process is outlined here:
	# http://developer.github.com/v3/git/
	#
	# Matt Swanson wrote a blog post translating the above steps into actual API calls:
	# http://swanson.github.com/blog/2011/07/23/digging-around-the-github-api-take-2.html
	#
	# I was not able to find sample code for actually doing this in Ruby,
	# either via the HTTP API or any of the gems that wrap the API.
	# So in the hopes it will help others, here is a simple function to