Skip to main content

Installing OpenConferenceWare on Ubuntu

I've been working a soon-to-be-released app called "OpenCFSummitWare" (a.k.a. "Engage" but that name was taken on Google Code) for a while now, and it's the application we'll be using to manage proposals, scheduling, and attendee information for OpenCF Summit.

The inspiration for the application is the excellent OpenConferenceWare that was created for the Open Source Bridge conference. Obviously we want to run a CFML conference on a CFML app, but it saved me countless hours by having an extremely strong model on which to base our new application.

OpenConferenceWare is written in Ruby, and since I have zero experience with Ruby (at this point anyway) it took a bit of work to install the app and get it up and running. With a bit of help from the OpenConferenceWare Google Group and some tenacity I got it running, so I thought I'd share the step-by-step process here.

Note that this assumes you're starting with a clean system or at least one that hasn't ever had Ruby (and some of the other tools outlined below) installed on it. You can do this all in one shot, and probably in a much more logical order, so what you see here is the step-by-step I went through as I ran into missing items while trying to install OpenConferenceWare. (Note that I am * not* doing the optional MySQL database steps, so I think it uses SQLite by default.)
  1. Install git:
    sudo apt-get install git
  2. Clone the OpenConferenceWare git repo:
    git clone git://github.com/igal/openconferenceware.git
  3. Install Ruby:
    sudo apt-get install ruby
  4. Install Ruby Gems:
    sudo apt-get install rubygems1.8
  5. Install additional tools necessary for building and compiling:
    sudo apt-get install ruby1.8-dev build-essential gcc autoconf libtool
  6. Install the MySQL development libraries:
    sudo apt-get install libmysqlclient-dev
  7. Install XML/XSLT libraries:
    sudo apt-get install libxml2-dev libxslt1-dev
  8. Install SQLite3 libraries:
    sudo apt-get install libsqlite3-dev
  9. Install rake:
    sudo apt-get install rake
  10. Install the bundler gem:
    sudo gem install bundler
  11. Install the MySQL gem:
    sudo gem install mysql
  12. Create a symlink to the bundle command:
    sudo ln -s /var/lib/gems/1.8/bin/bundle /usr/local/bin/bundle
  13. Go into the openconferenceware project directory you cloned in step 2 above:
    cd openconferenceware
  14. Install the necessary libraries for the application:
    bundle install
  15. Update the styles:
    rake bridgepdx:styles
  16. Set bridgepdx to be the default theme.
    1. Navigate to openconferenceware/config
    2. Create a new file called theme.txt
    3. Add the following line to theme.txt:
      bridgepdx
    4. Save the file
  17. In the openconferenceware directory, create the databases:
    rake db:create:all
  18. Finish the database creation, populate database with sample data, and set the admin password:
    rake setup:sample
    (If you don't want any sample data, just do rake setup instead of rake setup:sample)
  19. Startup the app:
    ruby script/server
  20. Navigate to http://localhost:3000/admin and log in!
Pay special attention to step 16 if you're getting an error along the lines of "bridgepdx theme broken"--that simply means you haven't set a default theme in openconferenceware/config/theme.txt

Final note: this setup is intended for running on a local development box, not for production! If you're interested in additional performance and security settings for production, make sure and check out the installation instructions on github.

Thanks to Igal and the entire team for such a great open source conference management app on which I could model the app we'll be using for OpenCF Summit!

Comments

thecrumb said…
Looking forward to seeing what you come up with! I was considering hacking on Mura if we ever do another NCDevCon... definitely a need for a nice conference app in the CFML space.
Matthew Woodward said…
I'll keep you posted Jim--should have something live and limping (or maybe even kicking) in another week or so.

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…