feat: make RQ results_ttl configurable

[fclabs]

Issue resolved by this Pull Request:
Resolves #458

Description

This PR makes the RQ results_ttl (Time To Live) configurable via the DOCLING_SERVE_ENG_RQ_RESULTS_TTL environment variable, addressing the feature request in issue #458.

Changes

1. Added eng_rq_results_ttl setting to DoclingServeSettings with default value of 4 hours (matching current behavior)
2. Updated orchestrator_factory.py to pass results_ttl when creating RQOrchestratorConfig
3. Updated __main__.py to pass results_ttl when creating RQOrchestratorConfig in the rq_worker command
4. Updated documentation in docs/configuration.md to document the new setting

Benefits

• Flexibility: Users can configure TTL based on their specific needs (long-running workflows, memory optimization, compliance requirements)
• Backward Compatible: Default value (4 hours) matches current behavior
• Consistency: Follows the existing pattern for RQ engine configuration
• No Breaking Changes: Existing deployments will continue to work with the default value

Usage

Users can now configure the TTL via environment variable:

export DOCLING_SERVE_ENG_RQ_RESULTS_TTL=7200  # 2 hours

Or in .env file:

DOCLING_SERVE_ENG_RQ_RESULTS_TTL=86400  # 24 hours

Testing

• ✅ Default value (4 hours) is used when not set
• ✅ Custom value is respected when set via environment variable
• ✅ Value is correctly passed to RQOrchestratorConfig in both orchestrator factory and rq_worker command

[github-actions]

❌ DCO Check Failed

Hi @fclabs, your pull request has failed the Developer Certificate of Origin (DCO) check.

This repository supports remediation commits, so you can fix this without rewriting history — but you must follow the required message format.

---

🛠 Quick Fix: Add a remediation commit

Run this command:

git commit --allow-empty -s -m "DCO Remediation Commit for Federico Castañeda <[email protected]>

I, Federico Castañeda <[email protected]>, hereby add my Signed-off-by to this commit: 9421bb13ec66983f76f4bc1bdaba52d1d27fef39"
git push

---

🔧 Advanced: Sign off each commit directly

For the latest commit:

git commit --amend --signoff
git push --force-with-lease

For multiple commits:

git rebase --signoff origin/main
git push --force-with-lease

More info: DCO check report

[dosubot]

Related Documentation

Checked 10 published document(s) in 0 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

[dolfim-ibm]

lgtm

[fclabs]

lgtm

Hi, @dolfim-ibm What else it is required to merge this one? Thank you in advance.