installing git on CentOS 5.3

(required in order to get many many other useful things)

sudo rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm
sudo yum install git

that link will change depending on your version of CentOS, and of course it changes over time. Look it up at https://fedoraproject.org/wiki/EPEL

VIrtualBox fullscreen: my favorite guide

http://digitizor.com/2009/05/26/how-to-install-virtualbox-guest-additions-for-a-linux-guest/

gem list error

I've been getting this error frequently during or after running a process which uses Ruby intensively. So far I have no solution other than restart. It also affects all other gem commands, including gem --version.

$ gem list
line 5: [path]: Argument list too long
line 5: [path]: Unknown error: 0

I'm still looking into how to fix this.

Run mysql script from command prompt

mysql -u [username] < path/[filename.sql]

how do you use rspec to test database relationships in rails?

I don't know, but I'm finding out. 

add "mate" to your path in OSX (to call TextMate)

To add "mate" to the path of OSX (i.e TextMate) you could do stuff in the terminal, or you could do 

Help > Terminal Usage > Create Link

and achieve the same result. Sometimes the GUI is useful. 

on the beach

I'm in Chicago, on the "beach" with some other TWUXXers getting our environments set up for next week, when we're on a small project spike... using Rails 3.0, JBehave, some other stuff...

On an unrelated note, I'm trying to get Bugzilla installed and configured. Conclusion: why are we using this anyway?

I went to a RoR101 session at lunch today... was interesting but the audience was very diverse in knowledge level.

The grocery store convenient to the Aon center is http://www.bockwinkels.com/

installing BugZilla

http://bugzilla.darwinports.com/

http://www.bugzilla.org/docs/2.18/html/installation.html

First, install MacPorts

go to /opt/local/bin

install https://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=20719 <- must be registered as a dev w Apple to do this

sudo port install bugzilla

run the ./checksetup.pl file is in /opt/local/www/Bugzilla

follow instructions... 

current error: Error in tempfile() using data/params.XXXXX: Parent directory (data/) does not exist at Bugzilla/Config.pm line 313

way to solve this error: follow the instructions in 5. in QUICKSTART and create the database

(I haven't solved this yet)

1. get appleid
2. get xcode and therefore db46
3. continue installing bugzilla

Configuring db46

Error: db46 requires the Java for Mac OS X development headers.

Error: Download the Java Developer Package from: <https://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=20719>

Error: Target org.macports.configure returned: missing Java headers

http://comments.gmane.org/gmane.os.apple.macports.user/22266

"Apple's most recent security update prior to Mac OS X 10.6.5 (presumably included in 10.6.5 also) deletes a file that was previously part of the OS, and is now only part of that development package. We don't know why Apple made this change, only that db46 and a handful of other ports break without it, so we detect this and advise you how to fix it."

http://yoodey.com/how-fix-db46-problem-macport-installation-or-install-db46-mac-os-x-1065

Bugzilla Quick Start Guide 

==========================

(or, how to get Bugzilla up and running in 10 steps)

Christian Reis <kiko@async.com.br]]>

This express installation guide is for "normal" Bugzilla installations,

which means a Linux or Unix system on which Apache, Perl, MySQL or PostgreSQL

and a Sendmail compatible MTA are available. For other configurations, please

see Section 4 of the Bugzilla Guide in the docs/ directory. 

1. Decide from which URL and directory under your webserver root you

   will be serving the Bugzilla webpages.

2. Unpack the distribution into the chosen directory (there is no copying or

   installation involved). 

3. Run ./checksetup.pl, look for unsolved requirements, and install them.

   You can run checksetup as many times as necessary to check if

   everything required has been installed.

   These will usually include assorted Perl modules, MySQL or PostgreSQL,

   and a MTA.

   After a successful dependency check, checksetup should complain that

   localconfig needs to be edited.

4. Edit the localconfig file, in particular the $webservergroup and 

   $db_* variables. In particular, $db_name and $db_user will define

   your database setup in step 5.

   If you want to change platforms, operating systems, severities and

   priorities, this can also be done in localconfig at this time.

5. Using the name you provided as $db_name above, create a MySQL database

   for Bugzilla. You should also create a user permission for the name

   supplied as $db_user with read/write access to that database.

   If you are not familiar with MySQL permissions, it's a good idea to

   use the mysql_setpermission script that is installed with the MySQL

   distribution, and be sure to read Bugzilla Security - MySQL section

   in the Bugzilla Guide or PostgreSQL documentation.

6. Run checksetup.pl once more; if all goes well, it should set up the

   Bugzilla database for you. If not, return to step 5.

   checksetup.pl should ask you, this time, for the administrator's

   email address and password. These will be used for the initial

   Bugzilla administrator account.

7. Configure Apache (or install and configure, if you don't have it up

   yet) to point to the Bugzilla directory. You should enable and

   activate mod_cgi, and add the configuration entries

        Options +ExecCGI

        AllowOverride Limit 

        DirectoryIndex index.cgi

   to your Bugzilla <Directory> block. You may also need

        AddHandler cgi-script .cgi

   if you don't have that in your Apache configuration file yet.

8. Visit the URL you chose for Bugzilla. Your browser should display the

   default Bugzilla home page. You should then log in as the

   administrator by following the "Log in" link and supplying the

   account information you provided in step 6.

9. Scroll to the bottom of the page after logging in, and select

   "parameters". Set up the relevant parameters for your local setup. 

   See section 4.2 of the Bugzilla Guide for a in-depth description of

   some of the configuration parameters available.

10. That's it. If anything unexpected comes up:

    - read the error message carefully,

    - backtrack through the steps above, 

    - check the official installation guide, which is section 4 in the

      Bugzilla Guide, included in the docs/ directory in various

      formats.

Support and installation questions should be directed to the

mozilla-webtools@mozilla.org mailing list -- don't write to the

developer mailing list: your post *will* be ignored if you do.

Further support information is at http://www.bugzilla.org/support/

rvm set default ruby to system

rvm reset

Iteration 4, Tues

Rewriting functional tests and Twist tests after adding universal login requirement to all application functionality is interesting and it depends on how you're implementing it. This will be an ongoing debate tomorrow.

The option to create a custom aspect ratio in Picasa is very very useful for creating images and banners of precisely the correct size for various websites, in this case a 760x100 Etsy store banner.