Fair point about documentation - but config/sphinx.yml is definitely the best way to change these settings. And here's a bit better than Twitter - not limited to 140 characters ;)
It's worth double-checking the file name - is it definitely sphinx.yml? I know it's obvious, but doesn't hurt to make sure. Because I can't spot any mistakes in what you're doing otherwise. Cheers -- Pat On 04/01/2011, at 1:29 AM, sergiu wrote: > Hi Patt, > > sorry to spam you both on twitter an here :). I found you first on > twitter than in this group. I'll stick to replying here from now on. > > Yup, my config/sphinx.yml file is using two spaces for everything > that's under "development", "test" and "production". It's pretty much > formated the same as in database.yml. I'll try parsing it with YAML > and see what I get. Here's the content: > > development: > morphology: stem_en > address: 10.10.0.0 > port: 9312 > test: > morphology: stem_en > port: 9313 > production: > morphology: stem_en > port: 9312 > > My main reason for posting the question was to make sure you still use > sphinx.yml and not some other format for the config file. One can > never know when the documentation becomes outdated. > > On Jan 3, 4:06 pm, Pat Allan <[email protected]> wrote: >> Hi Sergiu >> >> Just to confirm - are you using two spaces when indenting each environment's >> settings? I think that's what the YAML parser expects. >> >> -- >> Pat >> >> On 04/01/2011, at 12:58 AM, sergiu wrote: >> >> >> >>> Hi there, >> >>> first of all, I really like Sphinx and Thinking Sphinx :). I working >>> on an app using Lucene and Solr and I've already replaced the Solr >>> piece with Sphinx and it's working great on my dev machine. Indexing >>> is fast, searching is about the same as before, and I really like all >>> the options that Sphinx gives and Thinking Sphinx supports. >>> I have only one problem before deploying this on production: I've >>> created a sphinx.yml file inside config, to be able to tweak the >>> settings for the sandbox and production environments. The thing is >>> that when running rake thinking_sphinx:configure or rake >>> thinking_sphinx:index, the development.sphinx.conf file is generated >>> without using any of my settings from the sphinx.yml file. What can be >>> the cause of this? I'm using Thinking Sphinx 1.3.6, Sphinx 0.9.9 and >>> Rails 1.2.6 >>> I've tried the sphinx.yml file with spaces, without spaces, nothing >>> changes. Here are the contents of this file: >> >>> development: >>> morphology: stem_en >>> address: 192.168.1.1 >>> port: 9312 >>> mem_limit: 128M >>> test: >>> morphology: stem_en >>> port: 9313 >>> production: >>> morphology: stem_en >>> # address: prod-sphinx-1 >>> port: 9312 >> >>> Thanks for any suggestions ;) >> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Thinking Sphinx" 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 >>> athttp://groups.google.com/group/thinking-sphinx?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" 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/thinking-sphinx?hl=en. > -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" 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/thinking-sphinx?hl=en.
