feature:env

Introduction

feature:env shows or creates the .env in a feature’s docker/ folder. It works on the copy the product runs, editable or pinned, through the product’s symlink.

splent feature:env splent-io/splent_feature_notes --dev

📍 Feature: splent-io/splent_feature_notes@v1.2.0
🔗 Symlink: /workspace/my_first_app/features/splent_io/splent_feature_notes@v1.2.0 → /workspace/.splent_cache/features/splent_io/splent_feature_notes@v1.2.0
🧾 Env file: (not created)

Write the feature as the product’s pyproject.toml writes it, namespace included. The match is on the start of each entry.

---

Creating the .env

splent feature:env splent-io/splent_feature_notes --generate --dev

📄 Created splent-io/splent_feature_notes@v1.2.0/docker/.env from .env.dev.example

It copies docker/.env.<env>.example, or docker/.env.example when there is none for that environment. An existing .env is never overwritten.

---

Reference

Option	Description
--generate	Create docker/.env. Without it, only print the paths
--dev	Use the development features lists and template
--prod	Use the production features lists and template

Without --dev or --prod the command uses SPLENT_ENV, and stops when that is unset too. It exits 1 when the feature is not declared, has no symlink (run product:resolve) or has no docker/ folder.

---

Requirements

• A selected product (SPLENT_APP) that declares and links the feature.

See also

• product:env builds the product’s .env from its features.