Any news about it ?
Thanks,
Clément
On Nov 25, 11:16 am, Clément clmntlx...@gmail.com wrote:
Hi,
I have exactly the same behaviour... And did the same trick as you..
I have not enough time to investigate deeper for the moment :/
Thanks,
Clém
On Nov 23, 6:01 pm, Jesse Clark
I had the same problem back at the beginning of November with a
vendored Acts as statemachine gem and got this response;
Hi John,
Sorry, this was a regression introduced in Bundler 1.0.3. This is
fixed in the upcoming bundler 1.0.4. You'll need change this line in
your Gemfile:
gem aasm, :path
Hi there,
I have an app on heroku at the moment and so far we've just been using git
on heroku as our main repository.
We need to switch things around so we use github most of the time and have a
separate app for staging and testing.
I found this excellent guide for setting up github with
I have a few delayed_jobs that require data to be loaded from the
database and kept in memory. I've set up an initializer to load that
data (this is a Rails 3 app), but I'm not sure how to only run it on a
worker process and not my dynos. I noticed, while tooling around in
`heroku console`, that
Hi Guys,
The datamodel in our little heroku application is set up so there are
no data dependencies between users. We would like our scaling story
to be as we add users, we add nodes where the nodes can be totally
independent (separate web server, separate db) from one another. (We
don't want
Feezing-cloud-50??
On 1 Dec 2010 19:46, Chris Kramp chris.kr...@gmail.com wrote:
Hi All,
I am following railstutorial.org and am attempting to push my first
app (named first_app) to heroku. I get the following output:
first_app heroku list
You have no apps.
first_app heroku create
Hi Carson,
that's an interesting scaling model, but it doesn't map well onto the way
Heroku is architected. The Heroku model runs many distributed processes
throughout our single shared cloud. You don't have any nodes in a
traditional sense, but each web server dyno and background worker is
On Nov 25, 2:21 pm, Dennis dennismaj...@gmail.com wrote:
I also had to revert back from 3.0.3 to 3.0.1 - the Paperclip gem gave
a temp_file method not found error msg while attempting to upload an
image.
I believe Paperclip has since been fixed. There's a change sitting in
master about this:
