Re: Sunspot and geo search
If you're using WebSolr, you shouldn't need to do anything special to get spatial search working -- just consult the Sunspot API docs for the #near method (geo search) and #coordinates method (geo indexing). No particular ETA on Sunspot 1.2 -- hopefully within a few weeks though. On Mon, Jul 26, 2010 at 20:28, AlainP wrote: > Ok. Are there any tutorials on this on the net? Either there are none > or I am searching using the wrong keywords because I havent found > any ;-S > > Any idea on when the next Sunspot version will be out? > > On Jul 26, 1:06 pm, "Matthew A. Brown" wrote: >> WebSolr's Sunspot hosting uses the solr-spatial-light plugin to >> support Sunspot's geo search. However, the next Sunspot release will >> remove the need for an extended Solr and instead use a geohash-based >> spatial search that works with an out-of-box Solr 1.4 instance. >> >> On Mon, Jul 26, 2010 at 09:00, AlainP wrote: >> > In Sunspot documentation, it says: >> >> > Ordering by field value, relevance, geographical distance, or random >> >> > is it possible to make it work with Heroku? From what I understand, >> > geo search is only available on Solr with a plugin to Solr. >> >> > Am I missing something? >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Heroku" group. >> > To post to this group, send email to her...@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 her...@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. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Re: Sunspot and geo search
Ok. Are there any tutorials on this on the net? Either there are none or I am searching using the wrong keywords because I havent found any ;-S Any idea on when the next Sunspot version will be out? On Jul 26, 1:06 pm, "Matthew A. Brown" wrote: > WebSolr's Sunspot hosting uses the solr-spatial-light plugin to > support Sunspot's geo search. However, the next Sunspot release will > remove the need for an extended Solr and instead use a geohash-based > spatial search that works with an out-of-box Solr 1.4 instance. > > On Mon, Jul 26, 2010 at 09:00, AlainP wrote: > > In Sunspot documentation, it says: > > > Ordering by field value, relevance, geographical distance, or random > > > is it possible to make it work with Heroku? From what I understand, > > geo search is only available on Solr with a plugin to Solr. > > > Am I missing something? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@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 her...@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.
can't deploy Rails 3 release candidate apps
Heroku, please update Bundler to 1.0.0.rc.1 so we can use our Rails 3 apps. The Rails 3 release candidate is out and now we can't deploy Rails 3 apps to Heroku. I get -> Gemfile detected, running Bundler Unresolved dependencies detected; Installing... Fetching source index from http://rubygems.org/ No compatible versions could be found for required dependencies: Conflict on: "bundler": * bundler (0.9.26) activated by bundler (= 0.9.26, runtime) * bundler (>= 1.0.0.rc.1, runtime) required by rails (= 3.0.0.rc, runtime) All possible versions of origin requirements conflict. Thanks, Daniel -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Re: Sunspot and geo search
WebSolr's Sunspot hosting uses the solr-spatial-light plugin to support Sunspot's geo search. However, the next Sunspot release will remove the need for an extended Solr and instead use a geohash-based spatial search that works with an out-of-box Solr 1.4 instance. On Mon, Jul 26, 2010 at 09:00, AlainP wrote: > In Sunspot documentation, it says: > > Ordering by field value, relevance, geographical distance, or random > > is it possible to make it work with Heroku? From what I understand, > geo search is only available on Solr with a plugin to Solr. > > Am I missing something? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@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. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
new Bundler version?
Howdy, I was messing with a Rails 3 app on REE & Heroku. Things started out well but as I added dependencies to my Gemfile, I started getting seg faults: https://rails.lighthouseapp.com/projects/8994/tickets/5193-segmentation-fault-on-rake-dbcreate-multiple-rubies-multiple-dbs The fix in development was to use bundler --pre. But now, when I try to deploy to Heroku, I get: Your Gemfile.lock was generated by Bundler 0.10. You must delete it if you wish to use Bundler 0.9. FAILED: Have you updated to use a 0.9 Gemfile? http://docs.heroku.com/gems#gem-bundler It looks like Yehuda is releasing a Bundler 1.0.0 release candidate tomorrow: http://twitter.com/wycats/status/19558387994 Will Heroku be upgrading to that version of Bundler? I'm not sure how to test our Rails 3 on Heroku otherwise. Thanks! Dan -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Re: config paperclip for s3
I think this is an "aws-s3 gem doesn't support European buckets by default" thing. Try setting this constant in your config/environment.rb: AWS::S3::DEFAULT_HOST = "s3-eu-west-1.amazonaws.com" Discussion here: http://github.com/marcel/aws-s3/issues#issue/4 On Jul 25, 3:23 pm, Mateus wrote: > I configured my app as it's show here:http://docs.heroku.com/s3 > and upload the files, but, it doesn't work. > > I still got the message > """We're sorry, but something went wrong. > We've been notified about this issue and we'll take a look at it > shortly.""" > > When I try to upload a picture (a very small one actually) > > the bucket name is correct, also my id key and secret key, but the > problem still. > > anyone knows anything else I could try? > > -- > > before I finally post this I took a look on the logs and I found this > message: "The bucket you are attempting to access must be addressed > using the specified endpoint" > > I know this is because the bucked is EU based, so, to by-pass the > problem, I created another one US based and it works OK. > > I just want know now is if there is specific configuration for Europe > based buckets. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Error from the get go when heroku keys:add
Anyone know what would be causing this error? I installed the gem and it went successfully. /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.9.12/lib/heroku/client.rb: 5:in `require': no such file to load -- json/pure (LoadError) from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.9.12/lib/heroku/ client.rb:5:in `' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.9.12/lib/heroku.rb: 3:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.9.12/lib/heroku.rb: 3:in `' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.9.12/bin/heroku: 6:in `require' from /usr/local/lib/ruby/gems/1.9.1/gems/heroku-1.9.12/bin/heroku: 6:in `' from /usr/local/bin/heroku:19:in `load' from /usr/local/bin/heroku:19:in `' -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Problem with awesome_nested_set and Rails 3, and a fix
Using awesome_nested_set 1.4.3 with Rails 3 on Heroku was not straight forward. I wanted to document this here in case someone else had the same problem. First, make sure you have installed it as a plugin, not as a gem. Remove it from Gemfile if you have it there and install it on your local with: rails plugins install http://github.com/collectiveidea/awesome_nested_set.git If you try to run it now, you will get a NoMethodError for proxy_options. This is documented on github as issue #34. Until a permanent fix is made available, you can open vendor/plugins/ awesome_nested_set/lib/awesome_nested_set.rb and on line #567 remove: ", nested_set_scope.proxy_options[:conditions]" Then you will get two depreciation warnings on lines #89 and #90 of the same file. This is documented on github as issue #42. Change "named_scope" to "scope" on those lines. If you're like me, you have the vendor folder listed in .gitignore. If so remove it. Then add, commit and push to heroku. My tests still pass with these changes. YMMV. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Sunspot and geo search
In Sunspot documentation, it says: Ordering by field value, relevance, geographical distance, or random is it possible to make it work with Heroku? From what I understand, geo search is only available on Solr with a plugin to Solr. Am I missing something? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Re: rails 2.3 change the From field with Gmail SMTP?
It has been my experience that Gmail does not allow you to set the "From" address. It will only use the authenticated user's email. This is one of the reasons we switched to the Sendgrid plugin. Kelly Heikkila :coderow On Jul 26, 2010, at 12:57 AM, Matthew Todd wrote: On Jul 23, 2010, at 2:11 AM, Seriously.Arrested.Development wrote: I'd like to specify "Real Name " but the email is not deliverred in this case. Would anyone know of anyway of getting around that using the Gmail SMTP? Which specific versions of Ruby & Rails are you using? When you include the "Real Name" in the From address, ActionMailers 2.3.3 -- 2.3.5 improperly set the Return-Path header on Rubies 1.8.7 -- 1.9.x, causing mail delivery to fail. [Ticket #2340][1] If this is what's causing your problem, upgrading to Rails 2.3.8 (while playing The Final Countdown) should fix it. Cheers, -- Matthew [1]: https://rails.lighthouseapp.com/projects/8994/tickets/2340-action-mailer-cant-deliver-mail-via-smtp-on-ruby-191 -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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 . -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
Re: Occasional Memcached::ServerIsMarkedDead Error
Alright, maybe the memcached-northscale gem isn't working as expected.
Got some strange errors over the weekend:
"NoMemoryError: failed to allocate memory"
.bundle/gems/gems/memcached-northscale-0.19.5.3/lib/memcached/
memcached.rb:309:in `dump'
.bundle/gems/gems/memcached-northscale-0.19.5.3/lib/memcached/
memcached.rb:309:in `set'
.bundle/gems/gems/memcached-northscale-0.19.5.3/lib/memcached/rails.rb:
72:in `set'
.bundle/gems/gems/activesupport-2.3.8/lib/active_support/cache/
mem_cache_store.rb:82:in `write'
.bundle/gems/gems/activesupport-2.3.8/lib/active_support/cache/
strategy/local_cache.rb:51:in `write'
.bundle/gems/gems/activesupport-2.3.8/lib/active_support/cache.rb:
165:in `fetch'
What we're caching shouldn't come anywhere close the max key size in
memcached.
Also got some of these:
Memcached::ServerIsMarkedDead: Key {"Product:
754:1"=>"mc2.ec2.northscale.net:11211:8", "Product:
756:1"=>"mc2.ec2.northscale.net:11211:8", "Product:
979:1"=>"mc2.ec2.northscale.net:11211:8", "Product:
978:1"=>"mc2.ec2.northscale.net:11211:8", "Product:
980:1"=>"mc2.ec2.northscale.net:11211:8"}
.bundle/gems/gems/memcached-northscale-0.19.5.3/lib/memcached/
memcached.rb:604:in `check_return_code'
.bundle/gems/gems/memcached-northscale-0.19.5.3/lib/memcached/
memcached.rb:502:in `get'
.bundle/gems/gems/memcached-northscale-0.19.5.3/lib/memcached/rails.rb:
67:in `get_multi'
.bundle/gems/gems/activesupport-2.3.8/lib/active_support/cache/
mem_cache_store.rb:58:in `read_multi'
Any help/suggestions?
Thanks,
Chris
On Jun 29, 12:24 pm, Sean Lynch wrote:
> I've sent a pull request to Fauna so hopefully the changes I have
> inmemcached-northscale will be in the "real" gem soon. Unfortunately, I can't
> really help with making Rails find the right gem, though; I'm a C++, Python,
> and Erlang guy mostly ;-)
>
> On Jun 29, 2010, at 7:47 AM, shenry wrote:
>
> > I've got the same occasional error, and tried to usememcached-
> > northscale but Rails couldn't find the gem on my machine. In
> > environment.rd I tried
>
> > config.gem 'memcached-northscale' # replaces config.gem 'memcached'
>
> > But no luck. I have thememcached-northscale gem version 0.19.5.2
> > installed locally, what am I missing? TIA
>
> > On Jun 17, 1:18 pm, chris wrote:
> >> This nortchscale-memcachedgem has been working great for me in
> >> production over the last few days.
>
> >> Thanks! Heroku docs should be updated to point to this gem...
>
> >> On Jun 16, 1:42 pm, Perry Krug wrote:
>
> >>> Hi Chris,
> >>> We believe that these issues are caused by bugs in the default
> >>> memcachedlibrary in the Gem. Can you change over to the 'memcached-
> >>> northscale' library? You should just be able to replace 'memcached'
> >>> with 'northscale-memcached' in the Gemfile. Leave the "Memcached" for
> >>> the required field.
>
> >>> Let me know if that helps or if there's anything else that I can do to
> >>> help.
>
> >>> Perry Krug
> >>> NorthScale, Inc.
>
> >>> On Jun 15, 3:36 pm, opsb wrote:
>
> Hey
>
> I've been seeing the same problem. Where I can get hold of your
> memcached-northscale gem?
>
> Cheers,
> Olly
>
> On Jun 8, 9:31 pm, Sean Lynch wrote:
>
> > On Jun 8, 2010, at 10:11 AM, chris wrote:
>
> >> Hey y'all,
>
> >> I'm getting an occasionalMemcached::ServerIsMarkedDeaderror when
> >> folks hit the app. It seems to work fine if I wait a while or just
> >> restart the app.
>
> >> What do you guys do to catch this error? begin rescue retry? fail
> >> gracefully (somehow?)?
>
> > Hi, Chris.
>
> > I've made some modifications to Fauna's memcache-client compatibility
> > layer, because memcache-client never throws exceptions whereas the
> > compatibility layer is (which is why you're seeing these). I've
> > uploaded a test gem as memcached-northscale, and once I hear back from
> > people that it actually works and solves their issues, I'll submit the
> > modifications upstream.
>
> > -Sean
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Heroku" group.
> > To post to this group, send email to her...@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 her...@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.
