All is good now. Its always the little things:)

On May 6, 1:52 pm, joshmckin <joshmc...@gmail.com> wrote:
> Correct Mike and why I went with Chris's suggestion. I set my
> config.cache_store = :dalli_store and it appear to fix my problem and
> initial testing seems to be good. I'll post an update if it fails.
>
> On May 6, 1:48 pm, Mike Abner <mike.ab...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Dynos aren't guaranteed to run on the same machine, so they won't 
> > necessarily share the same /tmp directory. Best bet is to never rely on it 
> > being there or having the right data.
>
> > Mike
>
> > On Friday, May 6, 2011 at 11:39 AM, joshmckin wrote:
> > > Actually it caches to the tmp folder which is available in Heroku.
> > > Plus:http://devcenter.heroku.com/articles/caching-strategies#fragment_caching
> > > confirms fragment caching as an option.
>
> > > My state that it has something do with memcache was incorrect, as like
> > > you said it writes to the file system. We have multiple dynos running,
> > > I wonder if that may be causing the issue.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Heroku" group.
> > > To post to this group, send email to heroku@googlegroups.com.
> > > To unsubscribe from this group, send email to 
> > > heroku+unsubscr...@googlegroups.com.
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/heroku?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to