Repository navigation
Include location in nginx config for logs specific directives - #3654
Merged
bfops merged 3 commits intoApr 27, 2026
Merged
Conversation
cloutiertyler
approved these changes
Apr 14, 2026
Contributor
|
@aceysmith Thank you for creating this PR! Could you resolve the merge conflicts? I've approved this. |
clockwork-labs-bot
enabled auto-merge
April 14, 2026 21:07
auto-merge was automatically disabled
April 14, 2026 23:12
Head branch was pushed to by a user without write access
aceysmith
force-pushed
the
nginx-config-for-follow-logs
branch
from
April 14, 2026 23:12
bf17689 to
0a5f3c4
Compare
Contributor
Author
Done! |
clockwork-labs-bot
enabled auto-merge
April 15, 2026 13:04
clockwork-labs-bot
disabled auto-merge
April 24, 2026 14:53
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.
Resolves #3652
Description of Changes
Update docs nginx configuration to better support
spacetime logs --followwhen self hosting configured to use ssl.API and ABI breaking changes
None
Expected complexity level and risk
1
Testing
I have added this location to my own nginx configuration and confirmed I am able to
spacetime logs -s some-https-server <my-module> --followand see logs immediately and continue following even if no log is produced after 1 minute.