Skip to content

refactor: add example env file for easier environment variable management#685

Open
Kat-Alo wants to merge 5 commits intothemarshallproject:developfrom
washingtonpost:napps-1234-new-contribution-branch
Open

refactor: add example env file for easier environment variable management#685
Kat-Alo wants to merge 5 commits intothemarshallproject:developfrom
washingtonpost:napps-1234-new-contribution-branch

Conversation

@Kat-Alo
Copy link

@Kat-Alo Kat-Alo commented Sep 5, 2023

This is purely meant as a developer experience enhancement. Rather than referencing different environment variables in different files, it can sometimes be a bit easier to copy the contents of an example env file into an actual env file and go from there.

Worth noting: this is part of my team's effort to sort out our guidelines for contributing back to open source projects we stand up for The Post's newsroom. This is just a small test case for our first go at it with Klaxon.


# Use "forwardPorts" in **devcontainer.json** to forward an app port locally.
# (Adding the "ports" property to this file will not forward from a Codespace.)
env_file:
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't honestly say I know how I mangled the git history here, but the diff should only be the switch from using environment variables to an env file like shown in this duplicate (and now closed) PR.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahhh, I see now. Y'all purged docker files on develop. I can definitely just nix this file, but thinking more about how this impacts the PRs we have in the queue... 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant