Added config files that should not be placed into repos by default as th... #488
Conversation
… they contain database information and URL's that will vary between local and other servers and can cause conflicts.
|
Thanks for submitting this! Sorry it's taken so long to take a look. It does look like lots of ExpressionEngine projects ignore these files, so |
aroben
added a commit
that referenced
this pull request
Nov 11, 2013
Added config files that should not be placed into repos by default as th...
drothmaler
pushed a commit
to drothmaler/gitignore
that referenced
this pull request
May 27, 2014
Added config files that should not be placed into repos by default as th...
u9E9F
pushed a commit
to u9E9F/gitignore
that referenced
this pull request
Jul 8, 2017
Added config files that should not be placed into repos by default as th...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I added two main config files to the gitignore for Expression Engine. I added them for 2 reasons, the constants in config.php change from repo to repo (as they set the URL) and the database.php for obvious security reasons.