Create a Meteor app and put the client_/server_ files in a client/server directories. Also, create a public dir to save the uploaded files.
// This gist is meant to help you load a json datafile into a Meteor application. More specifically, it's useful to migrate or bootstrap a Mongo datacollection. | |
// The easiest way to do this task is to open up three command shell windows. | |
// As a few of the commands will take over the command shell and direct their output to stdout. | |
// first, export your data to a file | |
// data.json | |
// run mongod so we can create a staging database | |
// not that this is a separate instance from the meteor mongo and minimongo instances |
#!/bin/bash | |
sudo kextunload -b org.virtualbox.kext.VBoxUSB | |
sudo kextunload -b org.virtualbox.kext.VBoxNetFlt | |
sudo kextunload -b org.virtualbox.kext.VBoxNetAdp | |
sudo kextunload -b org.virtualbox.kext.VBoxDrv | |
sudo kextload /Library/Extensions/VBoxDrv.kext -r /Library/Extensions/ | |
sudo kextload /Library/Extensions/VBoxNetFlt.kext -r /Library/Extensions/ | |
sudo kextload /Library/Extensions/VBoxNetAdp.kext -r /Library/Extensions/ |
# -*- mode: ruby -*- | |
# vi: set ft=ruby : | |
# Preventing kernel panics - VirtualBox 4.1 and Mac OS X Lion 10.7. | |
# | |
# This happens on my Macbook Air Mid-2011 Core i7. Every few hours, with | |
# one or (particularly) more VMs running, you will get a kernel panic. | |
# | |
# Some reading: | |
# https://www.virtualbox.org/ticket/9359 |
#!/bin/bash | |
# __ | |
# _____ ____ _/ |_ ____ ____ _______ | |
# / \ _/ __ \ \ __\_/ __ \ / _ \ \_ __ \ | |
# | Y Y \\ ___/ | | \ ___/ ( <_> ) | | \/ | |
# |__|_| / \___ > |__| \___ > \____/ |__| | |
# \/ \/ \/ | |
# | |
# .___ | |
# __| _/ __ __ _____ ______ |
sudo apt-get install zsh
Getting zsh to work in ubuntu is weird, since sh
does not understand the source
command. So, you do this to install zsh
wget https://github.com/robbyrussell/oh-my-zsh/raw/master/tools/install.sh -O - | zsh
and then you change your shell to zsh
chsh -s `which zsh`
Revised date: 07/11/2012
Between us [company name] and you [customer name]
We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.
Revised date: 07/11/2012
Between us [company name] and you [customer name]
We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.