Skip to content

Commit a6759a4

Browse files
committed
remove redundant sentence
1 parent c46c3a0 commit a6759a4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/internals/configuration.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ See the [reference](/docs/reference) page for a complete list of available optio
3535

3636
Pomerium's default mode is all-in-one mode. It runs all the individual [components](/docs/internals/architecture#component-level) in a single container or under a single system service. This is our suggested way to run Pomerium. Alternatively, each of those component services can be configured and run separately in split mode.
3737

38-
All-in-one mode has the easiest configuration and is successfully used in large production environments. All the configuration goes in a single `config.yaml` file or single set of environment variables. When running Pomerium as a single system service or container, all the options on this page can be set in a single `config.yaml` file, or passed to the single instance as environment variables. Internal communication is configured automatically requiring no additional setup.
38+
All-in-one mode has the easiest configuration and is successfully used in large production environments. All the configuration goes in a single `config.yaml` file or single set of environment variables. Internal communication is configured automatically requiring no additional setup.
3939

4040
Alternatively, each component can be run separately in split-mode using the [service mode](/docs/reference/service-mode) key to specify which component to run. Each of these needs to be configured separately, and communication between components must be explicitly configured including managing TLS certificates.
4141

0 commit comments

Comments
 (0)