Step 1: Basics
Use the first Portal step to create the Nodinite Environment and choose the target runtime model. In the current v7 wizard, this is where you decide whether the installation runs on Windows Server (IIS) or one of the supported container-based runtimes. The Windows Server option is the default and remains the standard production path.
Example of the current Portal Basics step in the environment wizard.
This step defines the core Environment metadata and the deployment pattern the rest of the wizard inherits.
Select a deployment pattern, for example Windows, then review Step 2: Auth, Step 3: Infrastructure, and Step 4: Servers so you understand how the selected runtime and the server-level values are refined later in the wizard.
Prerequisites
- Valid Nodinite 7 product key
- Portal access to the target Customer entry
- Planned Environment name and operational purpose
- Decision on whether to use the default Windows Server deployment or a container runtime
What This Step Controls
| Area | What it does |
|---|---|
| Environment metadata | Sets the name and description used for the target instance |
| Runtime selection | Chooses the Windows Server (IIS) path or one of the container-based runtime variants |
| Deployment starting point | Establishes the base configuration that later steps refine for authentication, infrastructure, and servers |
Choose the Runtime Model
Warning
The Environment name is permanent. Once the environment is created and the installation is built around it, the name must not be changed. Changing it later can break installation references, database naming, IIS site naming, and operational expectations across the environment.
The current Portal wizard supports the following runtime choices. Select the model that matches your deployment and then continue to the next configuration steps.
| Runtime | Use when | Guidance |
|---|---|---|
| Windows Server (IIS) | Standard production or on-premises deployment | Default choice for most installs and the main path described in Install Nodinite v7 |
| Docker Compose runtime | Local validation or container-based sandbox | See Docker runtime overview for the container deployment model |
| Kubernetes runtime | Cluster-based sandbox or evaluation | See Kubernetes runtime overview for the Helm-based workflow |
| OpenShift runtime | Kubernetes-based enterprise sandbox | See OpenShift runtime overview for the route-based deployment pattern |
| Azure Container Apps runtime | Managed Azure sandbox | See Azure Container Apps runtime overview for the Azure deployment guidance |
Register the Environment in the Portal
- Open the Nodinite Portal and navigate to your customer entry.
Example of the customer entry you open before registering a new Environment. - Verify that a Nodinite 7 product key exists. If it does not, create one before continuing.
Example of a Nodinite 7 product key entry in the Nodinite Portal. - Open the Environment tab and click Add Environment.
Example of the Add Environment action that starts the installation wizard. - In the wizard, select Install Fresh Nodinite 7.
Example of the Install Fresh Nodinite 7 option in the Portal wizard.
Note
The migration wizard uses the same portal steps (Basics → Auth → Infrastructure → Servers → Agents → Review and Download). For migration-specific guidance and differences — such as the Upgrade from Nodinite 6 mode, the Legacy Nodinite 6 environment path, and deferred agent configuration — see Updating from v6 to v7. 5. Enter the base Environment values and choose the runtime model for the deployment.
Example of the initial 'Add Environment' modal where the environment name and target runtime are selected.
- Name — the permanent name of the Environment used in the Portal and for the installation. This value cannot be changed later.
- Description — a free-text description of the Environment that can be updated later.
- Runtime — choose the target runtime model for the installation. The default is Windows Server (IIS), but you can select one of the container-based runtimes if that matches your deployment plan.
- After the wizard is created, the environment is opened and the next steps continue with the selected runtime model and configuration values.
The Edit Environment dialog is where you can update the name, description, and runtime choice before you continue the wizard.
Completion Checklist
- Product key verified
- Environment values entered
- Runtime model selected: Windows Server or container variant
- Next steps in Step 2: Auth and Step 3: Infrastructure reviewed