Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation warning during deploy from Capistrano and Rails 7.2 #1271

Open
walterdavis opened this issue Feb 27, 2025 · 0 comments
Open

Deprecation warning during deploy from Capistrano and Rails 7.2 #1271

walterdavis opened this issue Feb 27, 2025 · 0 comments

Comments

@walterdavis
Copy link

walterdavis commented Feb 27, 2025

I have been getting this warning while deploying to a server:

WARNING: key 'workers' is deprecated in /var/www/new_production/releases/20250227150142/config/production.sphinx.conf line 12; use 'default value' instead.

This file is auto-generated, and editing it manually doesn't seem to be a good idea.

Has anyone else seen this? Any suggestions to work around it?

TS: 5.6.0
Manticore: 6.3.8
Fairly ancient Ubuntu Linux server.

The Capistrano angle happens here, at the very end of my deploy script:

  after "deploy:published", "thinking_sphinx:configure"
  after "deploy:published", "thinking_sphinx:rebuild"
  after "deploy:published", "thinking_sphinx:restart"

The production.sphinx.conf file does not exist up until that point, it is not part of the deploy slug.

The config for TS is just this:

default: &default
  morphology: stem_en
  html_strip: true
  batch_size: 300
  charset_table: "0..9, A..Z->a..z, _, a..z, U+410..U+42F->U+430..U+44F, U+430..U+44F, U+23"

development:
  <<: *default

test:
  <<: *default

production:
  <<: *default
  batch_size: 100

staging:
  <<: *default
  mysql41: 9320

One of the three indices:

ThinkingSphinx::Index.define :document, :with => :real_time do
  scope { Document.where(id: Document.publicly.map{ |d| [d.id].concat(d.descendants.published.map(&:id)) }.flatten) }
  
  indexes title
  indexes teaser
  indexes body_html
  indexes author_display
  indexes tags_for_indexing

  has created_at, type: :timestamp
  has updated_at, type: :timestamp
end

None of these seem to have any settings which might influence that particular bit of inside-baseball configuration.

Please let me know if you need any other details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant