Heroku introduced a major update today to the platform. In addition to the press release and blog post, here is a list of all updated content:
Devcenter.heroku.com
Heroku introduced a major update today to the platform. In addition to the press release and blog post, here is a list of all updated content:
Devcenter.heroku.com
web: bin/python test-webapp.py |
module.exports = { | |
pivotal: { | |
TOKEN: 'TOKEN' | |
PID: 'PID', | |
}, | |
sprintly: { | |
USER: "USER_EMAIL", | |
ID: 'PRODUCT_ID', | |
KEY: 'API_KEY' | |
}, |
This is how I debug SystemStackError when there is no stack trace.
My first attempt was:
begin
a_method_that_causes_infinite_recursion_in_a_not_obvious_way
rescue SystemStackError
puts caller
end
#Overview drip is an awesome command line tool that can be used to dramatically lower perceived JVM startup time. It does this by preloading an entirely new JVM process\instance and allowing you to simply use the preloaded environment. This has extraordinary results with jruby.
We reduced time to run rake environment
from 13 seconds to a mere 3.5 seconds. This is actually at or near MRI 1.9.3p327 (with falcon patch) speeds!
Adding a few addition jruby options will reduce startup time even further (down to 1.69 seconds).
#Install Drip Install drip if you haven't already (see https://github.com/flatland/drip)
sass -c -I app/assets/stylesheets/ app/assets/stylesheets/**/*.scss |
This document is obsolete, all the docs for porting are now at https://github.com/mitsuhiko/pocoo-sprint-18052013
Versioning is an anti-pattern | |
============================= | |
We often say "use the right tool for the job", but when managing change | |
in software systems, we always use versioning. Hypermedia APIs are | |
actually hindered by introducing versioning and manage change in a | |
different way. With that in mind, there are also a lot of options for | |
managing change in a Hypermedia API. We'd like to change our service and | |
break as few clients as possible. Versioning is only one way to manage | |
change, though... and my contention is that it's not appropriate for |
Say there's a Go app at github.com/supermighty/app
, which has a package a
that references b
.
If I fork that repository to github.com/ericlathrop/app
, now the local file $GOPATH/github.com/ericlathrop/app/a/something.go
still has the line
import ("github.com/supermighty/app/b")
so when I edit $GOPATH/github.com/ericlathrop/app/b/something.go
, my changes are never seen in a
because it's still using the original copy of b
!
The workaround is to symlink the original repository path to the fork's path:
package main | |
import ( | |
"bytes" | |
"fmt" | |
"io" | |
"log" | |
"mime/multipart" | |
"net/http" | |
"os" |