Networking
Networking is how applications can communicate with other applications or databases. There are two main ways this can be achieved:
- Public networking: Connections that are accessible from the Internet or external networks. This makes an Internet round-trip, so it can be slower than private networking. With Sevalla’s Application Hosting, you can connect to your application publicly using a specific port or TCP proxy.
- Private networking: Connections that stay within our network and are not directly accessible from the Internet. We strongly recommend this method if you’re connecting applications hosted on Sevalla or linking an application with a database also hosted on Sevalla. To use Sevalla’s private network, all applications and databases must use the same data center.
Internal connections are only available between applications and databases hosted with Application Hosting and Database Hosting services.
You can configure your application's public or private port, disable HTTP(S) traffic, or add an internal connection within Applications > app name > Networking.
Public networking
The domain, hostname, and port of the application.
Edit application port
By default, the port for your application’s web process is 8080. When an application is deployed, it is reachable on the internet on ports 80 and 443, and we route those ports to the container on the port defined by your application. This port is available during application runtime on the $PORT environment variable. You can define a different port; however, it must be within the range 1-65535 except for the following ports used by our core system: 15000, 15001, 15004, 15006, 15008, 15009, 15020, 15021, 15053, and 15090.
To configure a specific port for your application, click Edit port, enter the new port, and click Update.
Edit the port for the application web process.
Disable HTTP(S) traffic
To disable all HTTP(S) traffic for your web process, click Disable > Disable.
Disable HTTP(S) traffic on your web process.
Private networking
This shows the hostname for all of the application processes. You can use the hostname to connect to the processes on Sevalla’s private network.
Hostnames for the application processes.
Ports
You can expose a port internally to improve communication between applications. This is especially useful in microservice architectures or when running services like RabbitMQ or databases that require internal network accessibility.
To expose a port internally, click Expose port, choose the Process you want to expose the port for, enter the Port, and click Expose port.
Expose a port internally.
Kinsta automatically deploys your application when you expose a port.
Connected services
This shows any applications or databases that are connected to the current application over Sevalla’s private network.
Currently, internal connections are only supported between applications in the same region. If you’re deploying an application and a database, you must choose the same region for both.
Services connected to your application on Sevalla’s private network.
Add a private connection
You can add a private connection from an application’s Networking page or a database’s Overview page. Wherever you start the process, the result will be the same.
To add a connection from an application to another application or database, go to Applications > app name > Networking > in the Connected services section, click Add connection, and select the application or database you’d like to create the internal connection to.
Add an internal connection from an application or database to an application in Sevalla.
Environment variables
We can automatically populate an application’s environment variables from the connection details. Do not copy and paste the internal connection details into environment variables. Click Add connection or Add application and select the Add environment variables… checkbox. This will automatically populate the environment variables from the application or database you’re connecting to.
Some applications may expect environment variables (keys) with different names. You can edit the names in the list before adding the connection or edit them later on the application’s Environment variables page.
Automatically fill environment variables from the database connection details.
Private connections and the build process
Private connections are only available during runtime; they are not available during the build process.
If your application tries to connect to a database using an internal connection during the build process, this causes an error that says the database is not running, which makes the build fail. This is expected because the internal connection is not live during the build; it can only be used during runtime.
There are a couple of ways to work around this.
Option 1: Move the logic that connects to the database from the application’s build command to the start command. For example: if you have a command like prisma migrate in the build process and move that command to the start command, your application will only access the database during runtime, and the build will be successful.
Option 2: Add separate environment variables as needed for the database connection, one available for the build process, and the other only for runtime. The keys can be the same (e.g. DB_CONNECTION_URL) as long as one is only available during the build process and the other is only available during runtime. Use the database’s External connection details (Databases > dbname > Overview > External connections) for the values of any variables to be used in the build process.
Remove a private connection
If you need to remove a connection, go to the Application’s Networking page, and under Connected services, click the delete (trash can) icon.
Internal connections between databases and applications.
In the Delete connection modal/pop-up, click Delete connection to confirm and remove the connection to the application.
Removing an internal connection.