you can use a database for openid storage. ruby-openid comes with generators to do this too. I think it's something like:
./script/generate open_id_authentication_tables MigrationName ./script/generate upgrade_open_id_authentication_tables MigrationName On Sat, Jan 16, 2010 at 1:30 PM, Solly <[email protected]> wrote: > Hi, > I am using OpenID in my Heroku app HWFeed (http://hwfeed.heroku.com). > Currently, I have the ruby-openid gem setup to put its store in "tmp/ > openid", but from the Heroku description of the tmp folder, I would > think that this is not the best option. Ruby-openid supports a > memcache option, but the Heroku memcached addon is in beta. Is the > file-based store ok, or should I switch to the memcache store, and > apply for the beta of the memcached addon, or is there some other > store type that works best with Heroku? To anyone currently using > openid and Heroku: what is your experience, and what works best? > > Best Regards > Solly > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<heroku%[email protected]> > . > For more options, visit this group at > http://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 [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
