This repository was archived by the owner on Jan 29, 2022. It is now read-only.
[#187] Don't allow "npm run seed" in production #144
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vitorbaptista
force-pushed
the
feature/187-disable-seeds-in-production
branch
from
98a0a08 to
a5ec565
Compare
We only allow `npm run seed` if `NODE_ENV == "production"`. This avoids us cleaning our production database by mistake. Fixes opentrials/opentrials#187
We need a separate environment as we need to be able to run `npm run seed` on staging.
vitorbaptista
force-pushed
the
feature/187-disable-seeds-in-production
branch
from
11c882d to
fe64668
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We only allow
npm run seedifNODE_ENV == "production". This avoids uscleaning our production database by mistake.
Fixes opentrials/opentrials#187