Every fileProductEnv imports

• Dashboard: open an environment, choose Import, then drop the file, browse to it, or paste its text. You see every key before anything is saved, and you can untick the ones that aren't secrets.
• CLI: productenv push --file appsettings.json uploads a file and productenv diff --file … compares it. The format comes from the file name, or from --format. See the CLI guide.
• Names are never changed: ConnectionStrings:Default and spring.datasource.url are stored exactly like that, and every line is imported, empty values included.
• Where only environment variable names work (a .env download, productenv run, GitHub, deploy providers), ProductEnv sends ConnectionStrings__Default. Pushing that .env back updates the same keys.
• A name a key can't hold (a space, $) is listed as not imported, with the reason.

# Comments and blank lines are skipped
DATABASE_URL=postgres://app:change-me@db:5432/shop
export STRIPE_KEY=sk_test_example
GREETING="Hello, world"

• A KEY= line is imported with an empty value.
• Templates such as .env.example or appsettings.sample.json hold placeholders, so the dashboard does not import them.

{
  "API_URL": "https://api.example.com",
  "STRIPE_KEY": "sk_test_example",
  "Features": { "Beta": true }
}

• null and empty values are imported as empty values.

{
  // Comments and trailing commas are fine
  "ConnectionStrings": {
    "Default": "Server=db;Database=shop;Password=change-me"
  },
  "Stripe": { "ApiKey": "sk_test_example" },
  "AllowedHosts": "*",
}

• Untick the settings that are not secrets (Logging, AllowedHosts…) before you import.
• List items use their index: Hosts:0, Hosts:1.
• Where only environment variable names work (a .env download, GitHub, Vercel…), it is sent as ConnectionStrings__Default, the name .NET reads from them.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <add key="StripeApiKey" value="sk_test_example" />
  </appSettings>
  <connectionStrings>
    <add name="Default" connectionString="Server=db;Database=shop;Password=change-me" />
  </connectionStrings>
</configuration>

• Downloads never rewrite your web.config: you get secrets.config and connectionStrings.config to point it to.

# Spring
spring.datasource.url=jdbc:postgresql://db:5432/shop
spring.datasource.password=change-me
MAPS_API_KEY=AIzaExample

• A KEY= line is imported with an empty value.

spring:
  datasource:
    url: jdbc:postgresql://db:5432/shop
    password: change-me
stripe:
  apiKey: sk_test_example

• A setting without a value (key: or ~) is imported with an empty value.

import 'package:shop/config/app_config.dart';

class AppConfigStaging extends AppConfig {
  @override
  Env get environment => Env.staging;

  @override
  String get shopApi => 'https://staging-api.example.com';
  @override
  String get basicAuthToken =>
      'dXNlcjpjaGFuZ2UtbWU=';
  @override
  bool get enableExperimentalFeatures => true;
  @override
  String get appId => switch (Platform.operatingSystem) {
    'android' => 'com.example.shop',
    _ => '1234567890',
  };

  static const mapsKey = 'AIzaExample';
}

• A value worked out in code (a switch, a Platform check, an enum such as Env.staging, null) is imported exactly as written, and the import lists it so you can check it.
• String.fromEnvironment('API_URL', defaultValue: '…') imports as API_URL with its default.
• One class per environment: when a file has several classes setting the same keys, the first is read. Import each from a file of its own.
• A downloaded env.dart holds key names only, so it has nothing to import.
• Anything built into a mobile app can be read back out of it. Keep server secrets on your backend and pass the rest at build time with flutter run --dart-define-from-file.

Formats we don't read yet include .xcconfig (Xcode), .tfvars (Terraform), TOML and INI. Until then, paste the values into a .env file and import that.