Skip to content

Commit ba12123

Browse files
committed
docs(SRV): update
1 parent 13dafed commit ba12123

File tree

2 files changed

+26
-11
lines changed

2 files changed

+26
-11
lines changed

pages/serverless-containers/concepts.mdx

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -150,13 +150,6 @@ The container can then process the message and perform any required actions, suc
150150

151151
The port of a containerized application refers to the network port that the application inside the container listens on for incoming requests.
152152

153-
When you deploy a container, you must map this internal port to a port on the host machine by specifying its value at [container creation](/serverless-containers/how-to/deploy-container/) via the **Port** parameter. The value defined in this parameter will then be passed to your container during the deployment inside the `PORT` environment variable.
154-
155-
<Message type="note">
156-
- Only one port can be exposed per Serverless Container.
157-
- 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.
158-
</Message>
159-
160153
Refer to the [dedicated documentation](/serverless-containers/reference-content/port-variable/) for more information and examples on the **Port** parameter of Serverless Containers.
161154

162155
## Privacy policy
Lines changed: 26 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
3-
title: Understanding the PORT variable
4-
description: Learn about the PORT environment variable in Scaleway Serverless Containers.
3+
title: Understanding the Port parameter
4+
description: Learn about the Port parameter and the PORT environment variable in Scaleway Serverless Containers.
55
content:
6-
h1: Understanding the PORT variable
7-
paragraph: Learn about the PORT environment variable in Scaleway Serverless Containers and how to use it effectively.
6+
h1: Understanding the Port parameter
7+
paragraph: Learn about the Port parameter and the PORT environment variable in Scaleway Serverless Containers.
88
tags: port variable environment containers serverless
99
dates:
1010
validation: 2025-04-02
@@ -14,3 +14,25 @@ categories:
1414
- containers
1515
- environment-variables
1616
---
17+
18+
## Port parameter
19+
20+
The port of a containerized application refers to the network port that the application inside the container listens on for incoming requests.
21+
22+
When you deploy a container, you must map this internal port to a port on the host machine by specifying its value at [container creation](/serverless-containers/how-to/deploy-container/) via the **Port** parameter. The value defined in this parameter will then be passed to your container during the deployment inside the `PORT` environment variable.
23+
24+
<Message type="note">
25+
- Only one port can be exposed per Serverless Container.
26+
- 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.
27+
</Message>
28+
29+
## PORT environment variable
30+
31+
To allow you application to be reachable, the port declared as a parameter when [creating your Container](/serverless-containers/how-to/deploy-container/) must be the same as the port exposed by your containerized application.
32+
33+
We therefore recommend you use the `$PORT` variable in your application, as it will contain the port parameter value, as shown in the examples below:
34+
35+
36+
37+
38+
##

0 commit comments

Comments
 (0)