Pencarian

Rss Posts

 

 

 

The community mourns the passing of Richard “Cyberlot” Thomas – Keith Casey

Dec 13, 2010

This post was lifted wholesale from Cal Evans’s post from DevZone. I think he summed it up well and I had nothing to add.

Today, the PHP community mourns the passing of a friend. Three weeks ago, Richard Thomas, community member and friend to all who knew him passed away. I had planned on writing this post today and am ashamed that I put it off so long. Thanks to Jeff Moore’s post and Paul M. Jones’s post I was reminded of my duty to my friend.

I didn’t know Richard as well as some. I hung out with him on IRC and we swapped work horror stories and coding tips whenever we met at conferences. I was privileged to see him just days before he passed when we were both at CodeWorks Portland. I got to talk to him for a bit at lunch and between sessions. Sadly for me, that conversations centered around topics so trivial that I don’t even recall the details, just that fact that it was with Richard.

From Jeff’s blog:

Richard is survived by his wife Lisa and four year old daughter Nicollette. Donations are being accepted to assist them. Even if you haven?t had contact with Richard, consider making a donation if you?ve done freelance work, as Richard was doing at the time of his death. Donations can be sent to:

Niki Fund, 4818 Davis Place #G, Renton WA, 98055

While I never like to hijack a moment, Paul made an excellent point on his post that I’ll repost here for all because it is sagely advice from a man I highly respect.

And now, a practical note: A lot of PHP folk out there are freelancers or independent consultants, or are in other kinds of unstable job situations. If you are one of these, and you have a family, *please* consider purchasing term life insurance to take care of your loved ones if you pass suddenly. Get it even if you are very young. It is not expensive. It?s not the only thing you should do to prepare, but it?s an important thing.

Richard died at his computer doing what he loved, programming. We will miss you Richard, the world is a little darker place without you.

Admittedly, I only knew Richard in passing. We’d met at a couple conferences and he was at CodeWorks last month. I wish I’d gotten to know him a little bit better.

CodeIgniter Community Voice – HOWTO: Set up a CodeIgniter project in Subversion

Jun 08, 2010

EllisLab is blessed with two of the greatest communities that can be found anywhere on the internet in ExpressionEngine and more recently CodeIgniter.  Despite being a relative newcomer to the scene, the people attracted to CodeIgniter are among the smartest, most talented and down-to-earth developers around today.  From time to time we want to highlight some of these talented people, and we’ve asked them to lend their voice to ours.  Have your voice.  I hope you enjoy what they have to say as much as I did.

This week, our Community Voice author is Bruce Alderson, known on the forums as madmaxx, who has written a wonderful guide on how he uses subversion with CodeIgniter.  Bruce is an elder web monkey and systems programmer.  He totally digs the craft of building software, making cool stuff, and causing people to laugh so hard liquids are forced from their nose.  He’s currently the Chief Monkey at Discovery Software and author of the not-at-all famous robotpony.ca.  (Go read the one about shaving your yak)


After working with CodeIgniter for a few months (and WordPress for a few years), I?ve settled on a way to set up web projects that works well for development, deployment, and source control. Note that this style of layout only works on systems like Mac and Linux that have useful symlinks.

First, the folder layout


some-domain.com/
    
app/
        
config/
        
controllers/
        (
etc)
    
public/
        .
htaccess           -> ../site-extras/.htaccess
        favicon
.ico         -> ../site-extras/favicon.ico
        js
/                 -> ../site-extras/js
        images
/             -> ../site-extras/images
        system
/
            
application/    -> ../../app/
    
site-extras/
         
js/
         
images/
        .
htaccess

The layout favours a vhost setup, and splits your code and resources out of the CodeIgniter sources. Splitting your stuff from the CodeIgniter stuff lets you link your Subversion repository to theirs, so that you can keep it in sync with their development.

How it’s done

  1. Set up your source tree (not including the symlinks or CodeIgniter source) and add to your Subversion repo.
  2. Add a svn link to CodeIgniter’s repo (via svn propedit svn:externals, with public http://dev.ellislab.com/svn/CodeIgniter/tags/v1.6.2/) and run a svn update to grab the framework.  See the Subversion docs for details.
  3. Copy the CI application folder to the site root (as app), remove the .svn folders, symlink to application, and add it to your local svn repo.
  4. Symlink the other site-extras to the public webserver root, and configure your local machine (and public webserver) to point to this root for the domain’s virtual host setup.
  5. Alternatively, you can modify the $application_path to point to ../public/app/ (I’m not sure which is better yet).  See the CodeIgniter docs on apps for more details.

You now have a CodeIgnitor project ready for development. You can keep up-to-date with CodeIgniter updates, deploy easily, and get at your code without wading through extra levels of hierarchy.

Discuss this article