John Whitley jwhitley

Firebase Environments

At the time of writing this gist (January 4th, 2017), I was unable to find true sandboxing to separate development and production environments for a Firebase project. The closest we can get is to create two separate Firebase projects -- one for development and one for production.

Pros

Complete separation and isolation of all Firebase features.
Freedom to experiment without risking the corruption of production data.

Cons

There is no way to copy production data to your development project (that I am aware of).
Any settings changes made to your development project also needs to be manually applied to your production project.

	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">
	<dict>
	<key>Ansi 0 Color</key>
	<dict>
	<key>Blue Component</key>
	<real>0.31090480089187622</real>
	<key>Green Component</key>
	<real>0.31097450852394104</real>

	{"scores": [ {"naam":"David",
	"comp":3,
	"thingy": 80,
	"parts": [{"test": "3", "score": 7},
	{"test": "4", "score": 12},
	{"test": "5", "score": 12}]
	},
	{"naam":"David",
	"comp":2,
	"thingy": 100,

	set deviceID to (do shell script "diskutil list \| awk '/YourBootcampPartition/ {print $NF}'")
	do shell script "sudo bless -device /dev/" & deviceID & " -legacy -setBoot -nextonly"
	tell application "Finder" to restart