Skip to content

docs(serverless): clarify ports usage int-fix-serverless #4577

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 11, 2025
Merged

docs(serverless): clarify ports usage int-fix-serverless #4577

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
28bb479
fix(serverless): a port is not related to the HTTP protocol
ahamez Mar 10, 2025
c2f3be4
fix(serverless): add EOL
ahamez Mar 10, 2025
745c205
fix(serverless): remove confusing sentence about different port
ahamez Mar 10, 2025
35bccb9
feat(serverless): explain that containers are accessible on ports 80 …
ahamez Mar 10, 2025
e46c50b
fix(serverless): apply sugession
ahamez Mar 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions pages/serverless-containers/concepts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,12 +148,13 @@ The container can then process the message and perform any required actions, suc

## Port

The port parameter specifies the network port that your container listens on for incoming requests. If your application or container is set up to listen on a different port, you must specify it using the port parameter when deploying your container to Serverless Containers. It must reflect the port configuration within your container for your service to function correctly.
The port parameter specifies the network port that your container listens on for incoming requests. It must reflect the port configuration within your container for your service to function correctly.

The value defined in the port parameter will then be passed to your container during the deployment inside the `PORT` environment variable.

<Message type="note">
Only one HTTP port can be exposed per Serverless Container.
- Only one port can be exposed per Serverless Container.
- Your container is accessible from the internet via ports 80 and 443, regardless of the specified port. The value you set determines how the Scaleway infrastructure accesses your container.
</Message>

## Privacy policy
Expand Down Expand Up @@ -262,4 +263,4 @@ Unit used to measure the resource consumption of a container. It reflects the am

## Protocol

Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended.
Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended.