Skip to content

Fixes #661 - Added resource limit scenario #662

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

Merged
merged 6 commits into from
Jun 26, 2025
Merged

Conversation

ralf401
Copy link
Contributor

@ralf401 ralf401 commented Jun 25, 2025

No description provided.

@ralf401 ralf401 self-assigned this Jun 25, 2025
@ralf401 ralf401 linked an issue Jun 25, 2025 that may be closed by this pull request
Copy link

github-actions bot commented Jun 25, 2025

Artifacts

Produced during runtime

📦 epub-5f911a3
📦 html-5f911a3
📦 htmlzip-5f911a3

@ralf401 ralf401 changed the title Draft: Fixes #661 - Added resource limit scenario Fixes #661 - Added resource limit scenario Jun 25, 2025
@ralf401
Copy link
Contributor Author

ralf401 commented Jun 25, 2025

@mgruner I added the scenario keeping it rather small. Can you have a look if that's ok? I created additional issues about the docker environment variables (for docs and new docs). However, I replaced the outdated docker environment variable (replaced by ZAMMAD_PROCESS_SESSION_JOBS_WORKERS) and mentioned to check resource settings when adjusting it.

@ralf401 ralf401 requested a review from mgruner June 25, 2025 09:14
Copy link
Contributor

@mgruner mgruner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks nice, some suggestions for improvement for your consideration.

@ralf401 ralf401 merged commit 02a0444 into pre-release Jun 26, 2025
1 check passed
@ralf401 ralf401 deleted the rsc/fixes/661 branch June 26, 2025 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add new docker scenario to limit resources
2 participants