Skip to content

Do we still need separate environment specification files for "normal" and "headless server" installations? #11355

@hoechenberger

Description

@hoechenberger

For a long time, we've been providing an environment.yml for "common" use, and a separate server_environment.yml for running on a headless server.

As far as I can tell, the main difference between the two appears to be that the latter uses VTK development versions and a few pip packages -- including MNE!

It's a little confusing, and this pattern also resurfaces in the mne-docker repository, which is actually why it caught my attention as I was working on refreshing the Docker images.

So my question is: Can we consolidate the two environments?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions