2010
01.13

OpenPeer update

For those of you wondering what we’ve been doing, the honest truth is that not much has gotten done. For the last week I’ve been too busy to delegate out tasks to people, and doing it all from my netbook isn’t helping. However, I am happy to share that I finished writing the deployment system for the developers.

image

The OpenPeer deployment system basically takes the pain out of loading code for testing. The process for reloading a site with new code is simply pressing the reload button. The system then will:

  1. Lock the site from being reloaded by someone else
  2. Remove all files inside the site’s folder
  3. Checkout the code from our SVN repository
  4. Copy configuration and other files from a template folder
  5. Run SQL files in the _deploy folder to insert table structure and test data
  6. Unlock the site

The amount of time this tool will save us is very much worth the 3 hours it took to write and debug it.

Also this weekend I got around to installing and configuring nginx on vps2. It does a very good job and is much more memory efficient and quicker then apache. I still have apache running on an alternate port for SVN, and yet it manages to use up RAM. Oh well.

4 comments so far

Add Your Comment
  1. If you don’t make this (well, pretty much all of OpenPeer) open source that’s gonna be quite ironic indeed.

  2. I don’t think sourceforge or google code is opensource. Why does OpenPeer need to be.

  3. Sourceforge was fully open-source a while ago.
    But it just feels wrong if a project for aiding distribution of open source software for the spirit (unlike Google Code and SF who do it for the money) keeps their own software closed.

  4. I’ll consider it later.