Boston Python Workshop/Friday handout/OS X 10.6 or 10.5

From OpenHatch wiki
< Boston Python Workshop‎ | Friday handout
Revision as of 23:24, 1 March 2011 by imported>Paulproteus

Install git

It's an insult in British English, but git is also an awesome version control tool. Here's how you install it:

Go to this page on google code and download the latest file ending in "-x86_64-leopard.dmg" (1.7.2.3 as of this writing). If you're at a workshop and you need this file, please ask a volunteer - we might have it on a thumb drive, and that'd save you a bunch of time downloading. Once it's downloaded, double click to open. You'll see something like this:

File:Git-screenshot.png

Double-click the .pkg file to install. Once that's done, close all your open Terminal windows, and open a new one. Cut and paste the following into the new Terminal window: 

    git --version

It should respond with something like "git version 1.7.2.3".

Tell git who you are

  • Open up a new Terminal window.
  • git config --global user.name "Your Actual Name"
  • git config --global user.email "Your Actual Email" (Must be same email you use to sign up for Heroku [see below]. Also must be accessible from the workshop.)

If this doesn't produce an error, congratulations! You have a successful install of git and you can move on to the next section.

Django

  • Open a Terminal and type:
cd /tmp/
curl -L  http://www.djangoproject.com/download/1.2.5/tarball/  -o Django-1.2.5.tar.gz
tar zxvf Django-1.2.5.tar.gz
cd Django-1.2.5
sudo python setup.py install

Make sure Django is working

  • Open a Python prompt, and type this in:
import django

If you get an error, get help! Otherwise, you're done.

Create an SSH public key

You'll need one of these to push your work to Github.

  • Open up a new Terminal window.
  • ssh-keygen -C "Your Actual Email" -t rsa (email should match git config setting)
  • Hit enter to accept default location for ssh key.
  • Hit enter to accept blank passphrase (if computer is shared with other people, as in a work laptop, you should create a passphrase). Hit enter again to accept blank passphrase (or enter passphrase again).
  • Output of ssh-keygen command
  • Your brand-new public key is now stored at ~/.ssh/id_rsa.pub.

Put your SSH key on Github

Follow Github's instructions:

Install the KomodoEdit text editor

We'll be using the KomodoEdit text editor during the workshop, though you are free to use a different editor if you prefer. It must be a plain-text editor, such as vi or Textmate. Microsoft Word and other word processing programs won't work. If in doubt, use KomodoEdit.

Installation steps:

  • Download the KomodoEdit installer. If you're at a workshop and you need this file, ask a volunteer. We may have it on a thumb drive, which will save you a lot of download time.
  • Double-click the file once it's downloaded.
  • It will open an installer with a KomodoEdit icon and a picture of your Applications folder. Something like this:

File:Komodo-Edit-5.png

  • Drag KomodoEdit into your Applications folder.
  • Unmount the installer disk image by dragging it from your desktop to the trash.

Verify you can create a new Django app

  • Create a folder on the desktop called django_projects
  • Open a new Terminal window and type the following with a return at the end of each line:
   cd ~/Desktop/django_projects
   django-admin.py startproject test
  • Both commands should provide no output.
  • Once that's finished, type the following in the Terminal window with a return at the end of each line:
   cd test
   python manage.py runserver
  • The first command should produce no output. The second command will put out a bunch of output, then just sit there until you cancel it (2 steps from now).
  • In your browser, go to http://localhost:8000/
  • Back in the Terminal window where you ran python manage.py runserver, type control-c to kill the server.


If you already have Firefox

Open it, and then go to the Firefox menu (top left of the screen). Select "About Mozilla Firefox."

File:Firefox-menu.png

You'll get a window, like the one below, that shows you what version of Firefox you have. Write down that number!

File:Firefox-version.png

Now go to the Firefox homepage and see what the current version of Firefox is. If it's the same major version (such as 3.6 - you can ignore the third part of the number) then you're good. You don't need to upgrade. If it's a different major version, then you need to upgrade. Download it from the Firefox homepage and double-click to install. If you're at a workshop and you need this file, please ask a volunteer. We may have it on a thumb drive and it'll save you a bunch of download time.

If you don't have Firefox yet

Go to the Firefox homepage and click the big download button. If you're at a workshop, please ask a volunteer to see if we have it on a thumb drive. It'll save you a bunch of download time. Once you have the file, double click and follow the instructions to install.

Install the SQLite Manager Firefox Plugin

Open Firefox, and then go to the Tools menu and select "Add-ons." Click the "Get Add-ons" button at the top. Enter "SQLite" where it says "Search all Add-ons." The first thing that comes up should be SQLite Manager. Click "Add to Firefox" and then follow the instructions to install it.

If you have trouble installing, double-check that your Firefox version is at least 3.6.


Verify your database is set up

  • Open a new Terminal window.
  • cd ~/Desktop/ruby_on_rails/test_app
  • rails generate scaffold user name:string email:string address:text active:boolean
  • rake db:migrate
  • rails server
  • Go to http://localhost:3000/users -> New user -> create a user to make sure we can save to db. (The window where you ran rails server will display debugging information as you do so.)
  • In your Terminal window where you ran rails server, type control-c to kill the server.

Verify git is working

  • Open a new Terminal window.
  • cd ~/Desktop/ruby_on_rails/test_app
  • git init (Output of "git init" command)
  • git add . (Note the dot) (May get line ending warnings; safe to ignore.)
  • git commit -m "initial commit" (Output of initial check-in)
  • git log (We're just checking to make sure it worked. Verify that it has the right user and commit message.)
Retrieved from "https://wiki.openhatch.org/wiki/Boston_Python_Workshop/Friday_handout/OS_X_10.6_or_10.5?oldid=5680"