From 5a9956e42e832824964dabf71423fe53f0dfed9b Mon Sep 17 00:00:00 2001 From: Ruben Arts Date: Mon, 20 Jan 2025 15:41:01 +0100 Subject: [PATCH] Update docs/tutorials/multi_environment.md Co-authored-by: Hofer-Julian <30049909+Hofer-Julian@users.noreply.github.com> --- docs/tutorials/multi_environment.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/tutorials/multi_environment.md b/docs/tutorials/multi_environment.md index b560504f0..5bd6e6c38 100644 --- a/docs/tutorials/multi_environment.md +++ b/docs/tutorials/multi_environment.md @@ -23,10 +23,8 @@ Environments can actually be installed and activated to run tasks in. You can define multiple environments in one project. Defining environments is done by adding them to the `[environments]` table in the manifest file. #### **Default** -To keep pixi simple you will define a default environment if not specified otherwise. -This is the environment build by the non `[feature.` prefixed tables in the manifest file. -All these tables are merged to create the `default` environment. -Thus, in theory you can read the `[dependencies]` table as `[feature.default.dependencies]`. +Instead of specifying `[feature..dependencies]`, one can populate `[dependencies]` directly. +These top level table, are added to the "default" feature, which is added to every environment, unless you specifically opt-out. ## Let's get started