docs: document logging configuration and fix dev-server white screen - #313
Merged
Conversation
The configuration page only listed the logging flags as a table without any explanation. Add usage details covering: - default behavior (console prints core info only, file logging off) - setting the console level via --console-log-level / ET_CONSOLE_LOG_LEVEL and the RUST_LOG per-target filter syntax - enabling file logging with --file-log-level (non-off), the optional --file-log-dir / --file-log-size / --file-log-count knobs and daily rotation - adjusting the file log level at runtime with easytier-cli logger set/get - why logging options are process-level and cannot be put in the -c config file Applies to both the Chinese and English versions.
In dev mode vite serves node_modules sources as-is unless they are
prebundled. mermaid 11 imports { sanitizeUrl } from the pure-CJS
@braintree/sanitize-url package, which fails to load natively in the
browser and crashes the whole page (white screen). Build output is
unaffected because rollup converts the CJS dependency during bundling.
Add vite.optimizeDeps.include for mermaid so the dev server prebundles
it and its CJS dependencies with esbuild.
…groups The page had a single h2 (Basic Settings) wrapping every parameter group as h3, so the on-page outline only listed that one entry. Promote each parameter group (configuration server, network, RPC, listener, other, logging) to its own h2 and enable outline: deep so the logging sub-topics also appear. Applies to both the Chinese and English pages.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Adds previously-missing documentation for logging configuration (fixes #2498) and a couple of related fixes to the doc site.
--console-log-level/ET_CONSOLE_LOG_LEVEL,RUST_LOGper-target filters, enabling file logging with a non-off--file-log-levelplus the optional--file-log-dir/--file-log-size/--file-log-countknobs, runtime adjustment viaeasytier-cli logger, and why logging is a process-level option that cannot go in the-cconfig file. Both zh and en.node_modulessources as-is unless prebundled; mermaid's named import from the pure-CJS@braintree/sanitize-urlthen fails in the browser and blanks the whole page. AddoptimizeDeps.include: ['mermaid']so the dev server prebundles it (rollup build was already fine).outline: deepso the logging sub-topics also appear. Both zh and en.