All credit goes to phlco, going forward I'll be amending a few things and adding customs to the script some of which will be taken from http://lapwinglabs.com/blog/hacker-guide-to-setting-up-your-mac
A work in progress to automate the set up of a student's development machine.
Paste this script into a Terminal prompt:
bash <(curl -s https://raw.github.com/ga-instructors/installfest_script/mac_os/install.sh)
The script first runs any software updates and then checks for Xcode.
If Xcode is installed the script continues.
- We then clone the repo onto the student's machine
- Remove Macports or RVM
- Installs homebrew and some formulae
- Sets up git
- Installs Sublime and Sublime settings (package manager and base packages)
- Installs additional apps like Chrome, HipChat and Spectacle
- Sets up RBenv and installs bundler, pry and rails
- Adds solarized to Terminal
bash <(curl -s https://raw.github.com/ga-instructors/installfest_script/ubuntu/install.sh)
Don't use yet! Is not in working condition.
When weighing the options, we decided not use Vagrant to ensure all students were working in a common environment for three main reasons:
- ownership
- simplicity
- Heroku
We want the students to feel as if they are in control of their environments. That is, they should be able, within reason, to customize and optimize their coding experience as they see fit. Using a common install and then stepping away feels like a good way to set a baseline while allowing them ownership. While they could do the same with virtual machine, that undermines the entire reson of forcing them to work in a virtualized environment.
The precept holds as well: let's help them grow as individuals, and not enforce uniformity upon them. It seems to me weirdly patronizing to force them to work in an environment we've created, instead of giving them the tools to begin building their own.
Sure, having the students install Vagrant and run a VM may seem like it takes fewer steps than running this overcooked install script. But it's also removing a fair amount of agency. They don't afterwards have to interact with their dev envrionment, but only because of a reliance upon multiple layers of incredibly complicated software. It's giving the students "the magic" up front, which we've often seen lead to a number of questions we can't answer and misconceptions that are hard to clear up.
As long as we are pushing our repos to Heroku for deployment, a VM seems unnecessary. But if we begin using a different and customizable hosting environment, and teaching students basics concerning DevOps, it may make sense to use Chef and Vagrant to configure servers and deploy.
We expect to build virtual machines using the script and then have torrent links available here.