Skip to content

Commit 424812a

Browse files
lannitowlson
authored andcommitted
Document spin up --listen
Signed-off-by: Lann Martin <[email protected]>
1 parent 8b09bf8 commit 424812a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/v3/http-trigger.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -496,11 +496,11 @@ When exposing HTTP triggers using HTTPS you must provide `spin up` with a TLS ce
496496

497497
### Trigger Options
498498

499-
The `spin up` command's `--tls-cert` and `--tls-key` trigger options provide a way for you to specify both a TLS certificate and a private key (whilst running the `spin up` command).
499+
The `spin up` command accepts some HTTP-trigger-specific options:
500500

501-
The `--tls-cert` option specifies the path to the TLS certificate to use for HTTPS, if this is not set, normal HTTP will be used. The certificate should be in PEM format.
501+
The `--listen` option sets the local IP and port that `spin up` should listen to for requests. By default, it listens to `localhost:3000`.
502502

503-
The `--tls-key` option specifies the path to the private key to use for HTTPS, if this is not set, normal HTTP will be used. The key should be in PKCS#8 format.
503+
The `--tls-cert` and `--tls-key` options provide a way for you to configure a TLS certificate. If they are not set, plaintext HTTP will be used. The `--tls-cert` option specifies the path to the TLS certificate to use for HTTPS. The certificate should be in PEM format. The `--tls-key` option specifies the path to the private key to use for HTTPS. The key should be in PKCS#8 format.
504504

505505
### Environment Variables
506506

0 commit comments

Comments
 (0)