Skip to content

Dynamic .env file #434

New issue
New issue
Closed
feature
Closed
Dynamic .env file#434
feature

Description

@g5becks
g5becks
opened on Jan 23, 2021

This may be possible already and I am unaware of it, but what I would like to be able to do is set the dotenv file based on an environment variable.
E.G.

version: "3"

env:
  NODE_ENV: echo $($NODE_ENV)

dotenv: ["./packages/server/.env.{{.NODE_ENV}}"]

This would enable more dynamic variables for my tasks as opposed to writing separate taskfiles and including them.

Thanks.

Activity

  1. g5becks
    added
    feature
    on Jan 23, 2021

  2. badele commented on Mar 17, 2021

    @badele
    badele
    on Mar 17, 2021

    In the meantime, you can use this workaround

    # I assume that NODE_ENV is in shell variable 
set -o allexport; source ./packages/server/.env.${NODE_ENV}; set +o allexport
task target

  3. badele commented on Mar 18, 2021

    @badele
    badele
    on Mar 18, 2021

    The best feature would be have a taskfile to be able to use variables on any yaml section (from vars, env or minima environment vars)

  4. nfo
    added a commit that references this issue on Mar 18, 2021

    Allow vars in dotenv paths, including environment variables go-task#434

    a602d06
  5. andreynering
    closed this as completedin 08265edon Jun 5, 2021

  6. andreynering commented on Jun 5, 2021

    @andreynering
    andreynering
    on Jun 5, 2021
    Member

    This was just implemented at 08265ed.

  7. pd93
    removed
    type: feature
    on Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    feature

    Fields

    No fields configured for feature.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions