Public | Automated Build

Last pushed: 2 years ago
Short Description
SSE Docker Builds
Full Description

#Crazy Train

We're going off the rails on a crazy train


Crazy train is the new improved SSE Website. It's powered by Jekyll and auto deploys using webhooks. It's pretty cool.

Local Installation



git submodule init
git submodule update --remote
npm install
bower install

You should rerun the above commands if someone updates our git submodules, gems, npm modules, or bower packages.


bundle exec jekyll serve

Now visit localhost:4000.

Things that won't work

If you are running this locally, parts of it won't work. Thanks to the cross origin policy,
events won't be populated. Also any of the governing docs pages (primary officers policy, constitution) won't work becasue those pages are created properly deployment.

Other than that, you should be fine.


The SSE website has a lot of parts.


Crazy Train

Crazy train is the jekyll portion of the site. There are 3 submodules: crazy-train-pages, crazy-train-posts, governing-docs, and meeting-minutes. Website team does not have push access to any of these submodules. They are for the officers.


Just commit and push to the repos to create a post or a page. Inside of the main crazy-train repo, there is a Rakefile with rake task rake new_post. That will generate a new post for you in the post directory.

If you need images, there are image directories in both posts and pages. The path to these images are /assets/images/posts/YOUR_IMAGE.EXT and /assets/images/pages/YOUR_IMAGE.EXT respectively.

Auto Deploy

To make everyone's life a lot simpler, crazy-train auto-deploys when changed thanks to Github Webhooks. site-auto-deploy, our daemon written in sinatra, is running on both the production and staging VMs listening for post requests. The following webhooks are set up:

  • crazy-train: Push to master
  • crazy-train-posts: Push to master
  • crazy-train-pages: Push to master
  • governing-docs: Push to master
  • crazy-train: Push to development
  • crazy-train-posts: Push to master
  • crazy-train-pages: Push to master
  • governing-docs: Push to master

The deploy daemon on relevant actions will pull down the latest changes, attempt to build them into a tmp directory. If the build is successful, it will copy the changes to _site and deploy. If the build fails, the person who pushed will recieve an email saying the build has failed and to fix their changes. Notable problems in this process are:

  1. You will recieve two emails if pushing to one of the submodules (one from production, one from staging)
  2. The email doesn't include an error message.

Both of these will be fixed in the future.

Theoretically, the rest of the site (QDB, Scoreboard, WTF, and Pinnochio) could be autodeployed but those webhooks aren't set up.


In a private repo, you will find our production nginx conf. If you make any changes to it and you have sudo access, go pull it down and restart nginx. If you don't have sudo access, tell someone who does to do it.


WTF was our old rails site. Since the event system on WTF is still needed, a stripped down version of it is running that only includes Events. This is on a branch, only-events. It soon will be merged into master. You can find this portion of the site here. If you are an officer, you can log in using the same credentials you use for email and the file share.

Docker Pull Command
Source Repository