Skip to content

Crash Plan

eturk edited this page Nov 21, 2012 · 33 revisions

Eventually, the clock will break. This will (hopefully) prepare you for varying degrees of messed up.

1. Get the backup clock running.

There is a version of the clock running online at all times. Disconnect from the CCTV system, then direct the web browser on the clock computer to http://fhsclock.com. Hit F11 and you should have a clock. However, there are a few issues with this. Some generic schedules and themes are already there, so activate whatever you need.

2. SSH into the clock from another computer.

From one of the Macs in AV, open Terminal and SSH into the clock computer.

ssh -l fhsav clock@192.168.1.104

Now you can do work on the clock.

3. Check things out.

Check to see if MongoDB is running.

ps awwx | grep mongo

See if Redis is running.

ps awwx | grep redis

Check if there are any ruby instances running.

ps awwx | grep ruby

4. Reload the code base.

Once you've SSH'd in:

cd /var/www/clock
bundle exec thin stop
git add .
git stash && git stash clear
git pull origin master
bundle exec thin start -e production -p 5000 -d

5. Use the legacy version.

There's a stable version that you can use if need be.

cd /var/www/clock
bundle exec thin stop
git add .
git stash && git stash clear
git checkout legacy
bundle exec thin start -e production -p 5000 -d

If this all fails, re-install Ubuntu, then follow the Installation directions.

Clone this wiki locally