-
Notifications
You must be signed in to change notification settings - Fork 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
Consider which deployment files should be ignored within git #6
Comments
|
I think this issue is almost resolved, but we still need to remove the |
node_modules is updated in git ignore |
Confirmed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Almost certainly files under
dist/
andnode_modules/
should be included in the a.gitignore
so that the git repository is only tracking local source code changes. The dependencies and the packaged application should only exist in deployed packages (releases), or left to the administrator to deploy when the application is installed.To capture the state of the the application when it has been tested with specific dependencies, you will want to include the
package-lock.json
file in the git repository. If specific dependency versions are non-critical, you may want to exclude thepackage-lock.json
file via the.gitignore
.For configuration files where the administrator who is deploying the application has choices to make (such as database names, passwords, backend hostnames, ports, etc.), the git repo should provide sample files or sample values, with instructions to the administrator for changes. For example, consider
src/environments/environment.prod.ts
.The text was updated successfully, but these errors were encountered: