Use special configs when operating behind SMP - #249
Merged
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
1 participant
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.
We currently operate in what the Stalwart docs refer to as "standalone mode". That is, our installation operates directly, without a proxy in front of it. However, we need to be able to place our legacy installations behind a migration proxy, which requires several significant settings alterations. We also want to be able to roll back easily if something fails.
Therefore, I am introducing here a new option,
behind_proxy, which makes these settings changes in our bootstrapped/templated config files. We can swap this fromfalsetotruein our Pulumi configs, then roll out the changes when we're ready. If we need to roll back, we can swap it back tofalseand the changes will be rolled back when bootstrapping is run again.