Enhanced "Installation" to document WEBSVN_PATH_CONF. #4
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
|
Looking into it. |
michael-o
requested changes
Jun 20, 2019
docs/install.html
Outdated
| etc. would be set in <code>include/config.php</code>. That allows structuring SVN-repos in | ||
| subdirs like supported by <code>svnserve</code>, which is otherwise not supported by WebSVN, | ||
| as it checks if each directory is an SVN-repo already or simply ignores it. The following is | ||
| a more complete example: |
There was a problem hiding this comment.
There is comparative of complete, it is either complete or incomplete
There was a problem hiding this comment.
Is "comprehensive" a better term? The example doesn't contain everything, only more htan the former one. Or better use "verbose"?
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The section "'Installation" has been enhanced to document the new environment variable
WEBSVN_PATH_CONFintroduced by websvnphp/websvn#87 and the newly implemented simple layering of configs.One problem I recognized is that we only have one web site with one installation instructions for the latest released version of the software. So in theory one can only merge this directly before releasing a new version, which sounds pretty error prone to me. Not sure how to handle this, in the easiest case we simply merge and don't think about such things too much. :-)