Last night, we threw our first-ever Heroku Users Group meetup, and it was a hit!
Fifty Heroku users, add-on developers, entrepreneurs, and more gathered at our new office to get to know the Heroku team and swap stories with each other. We heard about some of the remarkable applications people are building on the platform, and we’re very excited to publicize those more — at future HUGs, in our newsletter, and here on the blog.
For this first meetup, though, we decided to open the curtains around Heroku’s inner workings a bit. Adam gave a great talk about five new features that should make life easier, particularly for people working on large-scale applications:
- Logging enhancements
- Release management
- Postgres add-on
- Custom error pages
- Process inspection
While most of these are still in beta testing, you can use
heroku ps right now to take a look at your processes. Rest assured that you’ll be hearing more about each of them shortly, though.
After Adam’s talk, we brought up several members of the team to sit on a panel and answer questions from the audience (and from our earlier call to #askheroku questions on Twitter) We heard excellent questions, and dug into some of the inner workings of our routing mesh, plans for the future, and more. See below for some of the questions and answers.
We wrapped up the night at Bloodhound, where our friends from Basho joined us to co-sponsor a drink-up, where we all got the chance to meet and speak with even more people doing great work.
All in all, we’re very happy with how the HUG turned out, and we’re looking forward to putting on more events in the future. Stay tuned to Twitter and the blog for more news.
Questions from #askheroku
Soon! 9 is part of the Postgres add-on that Adam talked about, and is on track to be available within a month or so.
Git over http/https is something that we’ve investigated, but we don’t have a firm date for making it available yet.
You’ve been able to do this for a while now! Take a look at the docs for more details.
This one’s a little more in-depth, so we’ll work on getting a blog post about it up in the near future.