Graham Hudgins
Graham Hudgins
# Acceptance criteria Add a -c option to `flox activate` **When** I `flox activate -c 'python -c "import requests"'` **Then** I see requests is successfully imported **When** I `flox activate...
# Problem **When** I have a remotely managed environment **I need** to edit its manifest with an IDE **So I can** enjoy the seamlessness of my IDE's terminal and text...
### Acceptance Criteria _New environment pushes_ **Given** I have just `flox init -n newly-pushed && flox install yarn` **When** I `flox push -m "hello world"`
## Original Issue Conda projects define their Python requirements in a file called `environment.yml`. Our current `flox init` steps are not looking in this file to determine the correct version...
### Acceptance Criteria _Entrypoint option_ Add design here _cmd option_ Add design here
**When** I don't want Flox to update (eventual enterprise reasons? I like it how it is?) **I need** to disable Flox's version check **So I can** turn off the message...
I took a note to make this enhancement awhile ago. It just says, "ask @nicklewis" (so please feel free to edit any part of this!)
STR: * create an environment and `flox install almonds` to it (a python app). * `flox activate` the environment * do `flox activate -r rossturk/flaim` * do the `gen` command...
## Motivation _Find old versions_ * **When** I need to find older versions of packages * **I need** a catalog of nixpkgs revisions over time * **So I can** search...
### Motivation **When** I have several processes that need to be running before I can start my developer environment **I need** a service manager in Flox environments **So I can**...