Skip to content
Website assets for DurHack hackathon πŸ’£
HTML JavaScript CSS
Branch: master
Clone or download
Pull request Compare This branch is 87 commits ahead of thien:master.
Latest commit 9480214 Sep 6, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
graphics Add Mahek to original photos Jun 9, 2019
src Change Karl to PG adviser Sep 6, 2019
.gitignore
LICENSE Initial commit Sep 23, 2016
README.md Update README Jul 20, 2019
screenshot.png add screenshot Sep 14, 2018

README.md

DurHack

hello world

These are website assets for the DurHack hackathon (the fourth one, as of the write-up of this README).

Quick Start

Hopefully, it should be as trivial as cloning the repo, cding into the repository, and slapping the following commands into the terminal (assuming node.js is installed):

cd src/
npm start

Having trouble with node v12? Try using v10. nvm is a great way to set this up.

Development

You can run the asset watcher (which will re-build the assets every time you change them) with:

npm run watch

Relevant JS and CSS files to edit are in the following two directories respectively:

src/assets/js/
src/assets/sass

Do not edit the contents of src/assets/vendor/.

deployment

Presently, we've used a Digital Ocean box which is covered through the Github Student Pack. pm2 is used to run the service as a daemon, with nginx acting as a reverse proxy. SSL certificates were created using Let's Encrypt (A good tutorial on how to do this yourself can be found here.) Optionally, there are lots of open source scripts that will act as a git webhook, allowing changes to be deployed as soon as changes are pushed into your repo (similar to how Heroku works), but I'm not sensible enough to allow that to be deployed.

blah blah blah ok w/e but can I use this for my own hackathon website?

Sure, but obviously don't use our logo and colourscheme or whatever. That'll be silly.

You can’t perform that action at this time.