Add Gopher support #273
Merged
Add Gopher support #273
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
This adds gopher support to WriteFreely -- both single- and multi-user instances. It is off by default, but can be enabled with the new `gopher_port` config value in the `[server]` section. When enabled, multi-user instances will show all public blogs at gopher://[host]:[gopher_port]/ -- otherwise, blogs are accessible at gopher://[host]:[gopher_port]/[blog]/ This is just a proof of concept for now. We still need to handle some edge cases and different configurations, like private instances. Ref T559
😲 seriously? Something I wrote is getting serious use? :) WOW! |
|
@prologic Yep! Thanks for the great work 🙂 Merging this in now. |
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.
This adds Gopher support to WriteFreely, thanks to @prologic's excellent go-gopher library. (This feature is tracked here: T559.)
This works on both single- and multi-user instances. It is off by default, but can be enabled with the new
gopher_portconfig value in the[server]section -- set it to the port you want to run the gopher server on. Then you'll want to expose that port to the internet or proxy connections to it.When Gopher support is enabled, multi-user instances will show all public blogs at
gopher://[host]:[gopher_port]/-- otherwise, blogs are accessible atgopher://[host]:[gopher_port]/[blog]/On single-user instances, you can access the blog via
gopher://[host]:[gopher_port]/and posts viagopher://[host]:[gopher_port]/[slug]This is just a proof of concept for now. We still need to handle some edge cases and different configurations, likeThis is handled.private = true. But this should be a good start.What do you think? Any improvements you'd suggest?