docs: Update quick-start#13927
Conversation
Signed-off-by: Ryan Northey <ryan@synca.io>
| - critical | ||
| - off | ||
|
|
||
| You can also set the log level for specific components using the :option:`--component-log-level` option. |
There was a problem hiding this comment.
it would be great if there were a way to dump the component list without having to read the header file.
perhaps we could add something along the lines of
envoy --mode dump --dump components
potentially it could also do a config_dump type thing where it tells you what would be configured
just an idea, not sure if i should raise a ticket
There was a problem hiding this comment.
Yeah I agree this would be nice. Can you open a ticket to track this?
Signed-off-by: Ryan Northey <ryan@synca.io>
Signed-off-by: Ryan Northey <ryan@synca.io>
|
|
||
| If you are running Envoy on a Windows system Envoy will output to ``CON`` by default. | ||
|
|
||
| This can also be used as a logging path when configuring logging. |
There was a problem hiding this comment.
@envoyproxy/windows-dev can you confirm the above note about logging with windows is correct ?
There was a problem hiding this comment.
While stdout will generally refer to CON, that depends on how the envoy process is launched... I'd point out that on windows, logs will default to stdout, and that the Linux /dev/stdout and /dev/stderr filename aliases to FD 1&2 don't exist. The NUL filename on windows can be used in place of /dev/null
There was a problem hiding this comment.
@wrowe can i land this and then someone with better knowledge could PR with some windows-specific updates ?
there are quite a few places where the docs are posix-focused - im just aware that this config wont work (and not sure what would)
There was a problem hiding this comment.
We can give you further feedback later this morning. In the posix world, the file - name universally represents FD 1 (or FD 0 in the context of an input name). /dev/stdout is actually a newer convention. We need to decide as porters if we will implement the aliases /dev/null, /dev/stdout etc, or whether envoy should have unambiguous, non-os specific implementations of these things.
|
@mattklein123 this one is ready for final review i think, and contains some important errata not sure about windows compat issues (#13927 (comment)) but my inclination if the note there is incorrect is to remove it for now and iterate |
|
latest render is here https://storage.googleapis.com/envoy-pr/13927/docs/index.html |
| - critical | ||
| - off | ||
|
|
||
| You can also set the log level for specific components using the :option:`--component-log-level` option. |
There was a problem hiding this comment.
Yeah I agree this would be nice. Can you open a ticket to track this?
|
I think we can do Windows specific follow ups later. |
Signed-off-by: Ryan Northey ryan@synca.io
Commit Message: docs: Update quick-start running envoy page
Additional Description:
add info to running envoy page about:
minor updates to securing envoy page (#13880 (comment))
add section re web ui to admin page
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]