Hi David In this situation, I would do the following instead:
indices_location: /var/www/tb/shared/sphinx Thus, no symlinks, and the location for the Sphinx files wouldn’t change. You’d want to do the same thing for log and pid files as well :) Cheers — Pat On 29 Oct 2014, at 7:58 am, David Krmpotic <[email protected]> wrote: > Pat, > > Thank you for fast response... I have /tmp already linked to a shared > directory on each release (I'm using https://github.com/mina-deploy/mina)... > also production.sphinx.conf is symlinked > > so: > /var/www/tb/current/tmp -> /var/www/tb/shared/tmp > /var/www/tb/current/production.sphinx.conf -> > /var/www/tb/shared/config/production.sphinx.conf > > Is this what you ment or is there even more optimal way? Because here I'm > using shared directories and it works nicely. > > In thinking_sphinx.yml I now use: > > indices_location: "<%= Rails.root %>/tmp/sphinx" > > regards, > david > > On Tue, Oct 28, 2014 at 9:47 PM, Pat Allan <[email protected]> wrote: > Hi David > > Sorry, the docs there should be more clear - RAILS_ROOT is just a placeholder > for people to put their own app directory in. It’s not a magic variable that > gets replaced within the TS code. You *can* use ERB within > thinking_sphinx.yml, but in this case that wouldn’t quite work, because you > really shouldn’t have these files within the app’s current Rails.root - they > need to be in a shared directory. > > I would avoid the need for symlinks, and just use shared folders instead. > > Cheers > > — > Pat > > On 29 Oct 2014, at 6:22 am, David Krmpotic <[email protected]> wrote: > >> david@eclipse:~/Projects/tb (master)$ bundle exec rake ts:configure >> >> Generating configuration to >> /Users/david/Projects/tb/config/development.sphinx.conf >> >> david@eclipse:~/Projects/tb (master)$ cat config/development.sphinx.conf | >> grep RAILS >> >> path = RAILS_ROOT/tmp/sphinx/post_core >> >> path = RAILS_ROOT/tmp/sphinx/post_delta >> >> >> On Tuesday, October 28, 2014 8:20:54 PM UTC+1, David Krmpotic wrote: >> Pat, thank you for the fast response... >> >> Actually in this case I'm at fault because of my new deployment strategy the >> sphinx folder with indices got stranded on each deploy... now I want to >> symlink it but I'm having some trouble with this: >> >> http://pat.github.io/thinking-sphinx/advanced_config.html >> >> it says I can use: >> >> indices_location: "RAILS_ROOT/tmp/sphinx" >> >> in thinking_sphinx.yml but this doesn't get expanded in generated sphinx >> configuration files.... >> >> So how can I use RAILS_ROOT there and is the manual outdated? >> >> thank you >> >> On Sunday, October 26, 2014 5:01:52 AM UTC+1, Pat Allan wrote: >> Hi David >> >> In recent versions of Thinking Sphinx (v3.1.1 definitely, and I think 3.1.0 >> too) guard files are put in place while indexing occurs, to avoid an index >> being processed multiple times at once. Unfortunately, these guard files >> aren't cleared out when an exception is raised during indexing... have a >> look in the folder of your index files, should be easy enough to spot. >> >> In the upcoming v3.1.2 release, there'll be better logging to note if these >> guard files are blocking indexing requests, and they'll also be cleared out >> if an exception is raised. >> >> — >> Pat >> >> On 25 Oct 2014, at 5:49 pm, David Krmpotic <[email protected]> wrote: >> >>> Hi, I use TS 3.1.1 and Sphinx 2.2.5 on the server and this is my index >>> definition: >>> >>> ThinkingSphinx::Index.define :post, with: :active_record, delta: true do >>> indexes :text >>> indexes :tags >>> >>> has :user_id >>> has :created_at >>> end >>> >>> After upgrading both TS and Sphinx every few days of webapp usage, I notice >>> that new records are no longer indexed. >>> >>> I checked and they are really not in the sphinx post_core or post_delta >>> indices. >>> >>> After reindexing and restarting sphinx, it's ok for a few days then the >>> same happens. >>> >>> How to troubleshoot this further? >>> >>> thank you >>> david >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Thinking Sphinx" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/thinking-sphinx. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Thinking Sphinx" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/thinking-sphinx. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Thinking Sphinx" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/thinking-sphinx/hLW-kZupy6g/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/thinking-sphinx. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/thinking-sphinx. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/thinking-sphinx. For more options, visit https://groups.google.com/d/optout.
