Update bare metal and docker deployment config#1098
Open
geniusjoe wants to merge 1 commit intoapache:mainfrom
Open
Update bare metal and docker deployment config#1098geniusjoe wants to merge 1 commit intoapache:mainfrom
geniusjoe wants to merge 1 commit intoapache:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The current bare-metal and Docker deployment documentation lacks configuration guidance. Users need practical examples to understand how to properly configure BookKeeper and Broker components.
Modifications
Added configuration sections with practical examples for both bare-metal and Docker deployment docs, covering:
BOOKIE_MEM,BOOKIE_EXTRA_OPTS)PULSAR_MEM,PULSAR_EXTRA_OPTS)apply-config-from-env.pyworks, configuration methods (-eenv vars,--env-file, volume mounts)Versioned docs
Updated
docs/(next),version-4.0.x/, andversion-4.1.x/.version-3.0.x/is not updated because theapply_changes_to_versioned_docsscript failed due to content differences in 3.0.x. Since 3.0 LTS is approaching end-of-life per the Release Policy, only 4.0.x and 4.1.x versioned docs are updated.✅ Contribution Checklist
Preview
docker



bare-metal



