diff --git a/content/docs/deploy/core.mdx b/content/docs/deploy/core.mdx index db99c309f..2883eb398 100644 --- a/content/docs/deploy/core.mdx +++ b/content/docs/deploy/core.mdx @@ -33,7 +33,8 @@ We publish official binaries for Linux and macOS on our [GitHub Releases](https: ### Standalone Binary -1. **Download** Go to [GitHub Releases](https://github.com/pomerium/pomerium/releases) and look for the tarball corresponding to your operating system and architecture. For example: +1. **Download** + Go to [GitHub Releases](https://github.com/pomerium/pomerium/releases) and look for the tarball corresponding to your operating system and architecture. For example: ```bash ARCH=[amd64 or arm64] @@ -43,7 +44,8 @@ We publish official binaries for Linux and macOS on our [GitHub Releases](https: | tar -z -x ``` -2. **Run** Once extracted, you have a `pomerium` binary. Supply configuration via environment variables or a config file: +2. **Run** + Once extracted, you have a `pomerium` binary. Supply configuration via environment variables or a config file: ```bash ./pomerium -config config.yaml @@ -115,7 +117,8 @@ If you prefer building from source: git clone https://github.com/pomerium/pomerium.git $HOME/pomerium cd $HOME/pomerium ``` -2. **(Optional) Generate Local Certs** For local development, use [mkcert](https://mkcert.dev/): +2. **(Optional) Generate Local Certs** + For local development, use [mkcert](https://mkcert.dev/): ```bash go install filippo.io/mkcert@latest mkcert -install @@ -176,7 +179,8 @@ For local testing, specify the `certificate_file` and `certificate_key_file` if If you installed via `rpm` or `deb`, we ship a systemd service unit: -1. **Bind to Port 443** Allow the `pomerium` service to listen on a privileged port: +1. **Bind to Port 443** + Allow the `pomerium` service to listen on a privileged port: ```bash echo -e "[Service]\nAmbientCapabilities=CAP_NET_BIND_SERVICE" | sudo SYSTEMD_EDITOR=tee systemctl edit pomerium ```