Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
celery-haystack-ng
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
AlekSIS®
Libraries
celery-haystack-ng
Commits
50d73598
Unverified
Commit
50d73598
authored
7 years ago
by
Justin Caratzas
Browse files
Options
Downloads
Patches
Plain Diff
fix comment typo
parent
2f9c8ca2
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
celery_haystack/conf.py
+1
-1
1 addition, 1 deletion
celery_haystack/conf.py
with
1 addition
and
1 deletion
celery_haystack/conf.py
+
1
−
1
View file @
50d73598
...
@@ -25,7 +25,7 @@ class CeleryHaystack(AppConf):
...
@@ -25,7 +25,7 @@ class CeleryHaystack(AppConf):
COMMAND_BATCH_SIZE
=
None
COMMAND_BATCH_SIZE
=
None
#: The max age of items used by the CeleryHaystackUpdateIndex task
#: The max age of items used by the CeleryHaystackUpdateIndex task
COMMAND_AGE
=
None
COMMAND_AGE
=
None
#: W
e
hther to remove items from the index that aren't in the DB anymore
#: Wh
e
ther to remove items from the index that aren't in the DB anymore
COMMAND_REMOVE
=
False
COMMAND_REMOVE
=
False
#: The number of multiprocessing workers used by the CeleryHaystackUpdateIndex task
#: The number of multiprocessing workers used by the CeleryHaystackUpdateIndex task
COMMAND_WORKERS
=
0
COMMAND_WORKERS
=
0
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment