Skip to content

fix: do not force to build on production #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 8, 2019

Conversation

dianjuar
Copy link
Member

@dianjuar dianjuar commented Sep 8, 2019

The seeder used force to have the configuration production when building the app. We do not need to do it on libraries.

close #2

@dianjuar dianjuar self-assigned this Sep 8, 2019
@dianjuar
Copy link
Member Author

dianjuar commented Sep 8, 2019

FYI @xmlking

@dianjuar dianjuar merged commit d2172c1 into master Sep 8, 2019
@dianjuar dianjuar deleted the fix-deploy-production branch September 8, 2019 07:58
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.

--prod is no longer needed for library modules
1 participant