Skip to content

dotenv-safe instead of manual checking a hardcodet whitelist #111

Open
Open
dotenv-safe instead of manual checking a hardcodet whitelist#111
Assignees
vpanjganj
Labels
suggestion
Milestone
Maintenance

Description

@Sharaal
Sharaal
opened on Jan 25, 2018

Instead of:
https://github.com/wearehive/project-guidelines/blob/4baf60bab3fc3d4616712b04f3dab48a3774d20c/config.sample.js#L1-L9

Maybe its an idea to use dotenv-safe, with that you can define the needed env variables in the .env.example (the optional ones can be prefixed with # ).

Activity

  1. vpanjganj
    added
    suggestion
    on Nov 22, 2018
  2. vpanjganj
    self-assigned this
    on Nov 22, 2018

  3. bhgsbatista commented on Aug 27, 2019

    @bhgsbatista
    bhgsbatista
    on Aug 27, 2019

    I second this, less code, less things to think about. The .gitignore example file would also need to be fixed, since it currently ignores .env* files.

  4. vpanjganj
    added this to the Maintenance milestone on Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

suggestion

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions