Skip to content

fix: describe PROCESS_MAX_BUFFER as 7 reads it in the .env #35

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.

Sign up for GitHub

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
blaipr merged 1 commit into from
Oct 12, 2026
Merged

fix: describe PROCESS_MAX_BUFFER as 7 reads it in the .env #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions .env
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -144,9 +144,10 @@ ADMIN_PASSWORD=AnsibleForms!123
# Default: password|secret|token
# MASK_EXTRAVARS_REGEX=password|secret|token

# Maximum buffer size for process execution (increase for large output)
# Default: 1048576 (1024 * 1024)
# PROCESS_MAX_BUFFER=1048576
# Playbook output the RTE stores per stream (stdout, stderr), in bytes. Past it the output is no
# longer stored (the job says so) and the playbook goes on. Read by the RTE, not the app.
# Default: 52428800 (50 * 1024 * 1024)
# PROCESS_MAX_BUFFER=52428800

# Limit the launching user's details sent as ansibleforms_user in the extravars
# Default: empty (everything)
Expand Down
Loading