Anyone get this working on Heroku?

[gabehoffman]

I have it working fine on my own dev box, and it responds with different versions just fine. When I push it to Heroku it's only using v1, even though v2 is the default.

Not sure if it's me or if there is Heroku caching issues. Anyone try that yet?

[hookercookerman]

hmmm strange; have your tried local development with cache classes set to true prehaps that might identify the problem

[gabehoffman]

the way I'm doing it is in V1 of the API controller, I call

API::V1::TeachingsController
ActiveModel::VersionSerializer.default :v1

in V2 I call
API::V2::TeachingsController
ActiveModel::VersionSerializer.default :v2

in v2 I'm generating a random pic url, just to make sure that it's not caching and that's using v2

On my local dev machine, it's working just like I want it to, I load it to Heroku and it only uses v1, does heroku just read the first default and keeps it there? I'm just curious if the data is binding differently on the cloud than on my local machine.

Can you only call one default, or should I call it the version explicitly in the responds_with?