Configuration Reference

Netptune services are configured entirely through environment variables. The sections below document every option for each service. For Helm deployments, see the mapping table at the bottom of this page.

API server

Connection strings

Passed as environment variables using ASP.NET Core's double-underscore (__) separator for nested configuration keys.

Authentication

Token behaviour

Email

S3 storage

ASP.NET Core

CORS

CORS origins are configured via appsettings.json. When self-hosting, set CorsOrigins to include your public domain:

{
  "CorsOrigins": [
    "https://your-domain.com"
  ]
}

Job server

The Job Server requires the same connection string, authentication, email, and S3 variables as the API server. The table below lists each one for reference.

PostgreSQL

Redis / Valkey

Start the server with a --requirepass flag:

valkey-server --requirepass <your_password>

Include the password in the connection string passed to the API and Job Server:

<password>@<hostname>:<port>

NATS

NATS must run with JetStream enabled using the -js flag:

nats-server -js

Client (Nginx)

The client container is a pre-built Angular application served by Nginx. No additional configuration is required. The following behaviours are baked in:

• All requests to /api/* are proxied to the API server
• All other routes fall back to the Angular SPA's index.html
• Static assets are served with a 1-year Cache-Control header
• Security headers: X-Frame-Options, X-Content-Type-Options, Referrer-Policy
• Gzip compression enabled

Helm values mapping

When deploying via Helm, environment variables are managed through values.yaml and values.secret.yaml. The table below maps Helm value paths to their corresponding environment variables.