clarify remote access #45 #46
Closed
Conversation
This file contains 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
|
Hey! Thanks for the suggestion, this does look helpful. Personally I bit more inclined to use Option 1 (mentioned in #45), could you rework the PR more in that direction? (adding the additional instructions, vs changing the original line) |
Repository owner
closed this by deleting the head repository
Jul 30, 2023
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.
Users not proficient with Jekyll may find it difficult to configure remote access to their Chowdown sites using the current readme. As described in issue #45 , the current instructions only describe how to serve the site to the localhost. Jekyll doesn't appear to be as extensively documented as other web servers.