[GH-ISSUE #358] Add support for Environments #230

New issue

Open

opened 2026-03-03 11:14:12 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 11:14:12 +03:00

Owner

Originally created by @pavanbhaskardev on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/358

Originally assigned to: @pavanbhaskardev on GitHub.

Feature Request: Support for Environments

Requirements:

Allow users to create multiple environments for the same project.
When a new environment is created, it should include data from the database of another environment (supporting database cloning/copying).
The new environment should be creatable within the same server or on a different server.

Benefits:

Enables better staging, development, and testing workflows.
Simplifies environment management for complex projects.

Additional Notes:

Consider access control and isolation between environments.
Ensure that database copy procedures do not interrupt production workloads.

Originally created by @pavanbhaskardev on GitHub (Jul 22, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/358 Originally assigned to: @pavanbhaskardev on GitHub. ### Feature Request: Support for Environments #### Requirements: 1. Allow users to create multiple environments for the same project. 2. When a new environment is created, it should include data from the database of another environment (supporting database cloning/copying). 3. The new environment should be creatable within the same server or on a different server. #### Benefits: - Enables better staging, development, and testing workflows. - Simplifies environment management for complex projects. #### Additional Notes: - Consider access control and isolation between environments. - Ensure that database copy procedures do not interrupt production workloads.

kerem added the

frontend

feature

backend

labels

2026-03-03 11:14:12 +03:00

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@akhil-naidu commented on GitHub (Jul 22, 2025):

@pavanbhaskardev, database cloning can be in another PR. To begin with look these like preview deployments.

@akhil-naidu commented on GitHub (Jul 22, 2025): @pavanbhaskardev, database cloning can be in another PR. To begin with look these like preview deployments.

kerem commented

2026-03-03 11:14:12 +03:00

Author

Owner

@pavanbhaskardev commented on GitHub (Jul 22, 2025):

There is a difference between preview-deployments and environments right?

When we've raise a PR to main from feature-branch we need to create deployment
Whereas environment is like same services with some different source configuration

Understood initial implementation should be like another environment should be created with same configuration

@pavanbhaskardev commented on GitHub (Jul 22, 2025): There is a difference between preview-deployments and environments right? - When we've raise a PR to main from feature-branch we need to create deployment - Whereas environment is like same services with some different source configuration Understood initial implementation should be like another environment should be created with same configuration