Quick Tips for a Better Hackathon w. Heroku

heroku-battlehacks.md

http://bit.ly/heroku-battlehack

Quick Tips for a Better Hackathon w. Heroku

1. Invest every second in your app,. avoid rabbit holes

• Heroku makes building and deploying basically every modern language as simple as git push heroku master. Visit heroku.com/{ruby, php, node, etc.} to watch a ~60 second 'Hello World' on Heroku video.
• You can have everyone up and running with Mongo, Postgres or any of over 150 Heroku Add-ons in moments - check-out our new Heroku Elements page for inspiration.
• Heroku has three interfaces, the Heroku Dashboard, the Heroku Toolbelt, and of course the API. So you can opt for the interface that you feel most comfortable with.

2. Building apps is a team sport,. and Heroku & GitHub make kicking-ass together, possible.

• You can always deploy directly to Heroku with Git: git push heroku master, but the GitHub integration will ensure that your team is always ready to show-off the latest iteration of your hack! This post will have you up and running quickly: Heroku + GitHub
• Visit the Heroku DevCenter and read up on adding collaborators to your Heroku application. It's simple and allows other members of your team to manage your app as you would.
• With Review Apps Heroku will spin up a temporary test app for every pull request that's opened on GitHub, complete with freshly provisioned add-ons. This makes it easy to ensure the latest feature you've merged works!

3. Take risks, but have a safety net

• You deploy a new version of your application, everything breaks, it's ok we've all been there - the good news is every deploy on Heroku (or configuration change) creates a new release, and rolling back to a previous release is really, really simple.

4. "Web process failed to bind to port within 60 seconds of"

Heroku dynamically assigns a port to your application, it's made available to your application via. the PORT config var. In Node, you'd bind to the port like: server.listen(process.env.PORT || 5000)

5. You have many resources at your disposal

• The Heroku DevCenter
• Heroku Support
• Creager on Twitter or Creager via. Email

6. The Heroku Command Line Tool is awesome, use it

• Type $ heroku help to see a list of available help topics and then $ heroku help {TOPIC} to view the details of that topic (e.g. heroku help pg to see all the available Postgres commands).
• Use -a {app-name} to manage your application, regardless of your current working directory
• Use logs -t to tail your logs in real time
• Turn it off, and then back on again w. heroku restart
• heroku status displays the current Heroku platform status, you can also view it onlin: https://status.heroku.com/
• heroku ps will display the current state of your processes
• heroku open will open your app in the browser

7. Kicking-Ass is also hard work, so take a moment and celebrate when you ship a new iteration.

The Heroku Button below will deploy & configure this app (keep in mind I build it at 2 AM last night) Now just use Heroku's deploy-hooks add-on (heroku addons:add deployhooks:http --url={yourUrl}) to play your favorite tune whenever you ship a new iteration, Dance.

8. 01000001 01101100 01110111 01100001 01111001 01110011 11100010 10000000 10100110 01100001 01101110 01100100 00100000 01001001 00100000 01101101 01100101 01100001 01101110 00100000 01100001 01101100 01110111 01100001 01111001 01110011 00100000 01101100 01100101 01100001 01110110 01100101 00100000 01110100 01101000 01100101 01101101 00100000 01110111 01100001 01101110 01110100 01101001 01101110 01100111 00100000 01101101 01101111 01110010 01100101