Ditch the custom website, put redirect in place #1
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
The custom website hasn't been updated for almost five years and it isn't a good look. With nobody clamering to update it the far better solution seems to be to ditch it entirely. Instead we redirect to https://github.com/zookeepr/zookeepr which is active and has maintained documentation in various files. Website is hosted by github which does not support serverside redirects like 302. So client side redirects are used instead.
Member
|
I have no issues with this pull request. Any other opinions before I merge it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 custom website hasn't been updated for almost five years and it
isn't a good look.
With nobody clamoring to update it the far better solution seems to be
to ditch it entirely.
Instead we redirect to https://github.com/zookeepr/zookeepr which is
active and has maintained documentation in various files.
Website is hosted by github which does not support serverside redirects
like 302. So client side redirects are used instead.
Discussion regarding the change is at zookeepr/zookeepr#500