Move documentation to redis/redis.io #18
No reviewers
Labels
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
redict/redict-doc!18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch ":main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is the companion PR to redict/redict.io#18
It adjusts the links in the commands.
Delete all the documentation that I moved to
redict/redict.io. Removed things that are Redis specific (like "Redis Insight") or only in old versions (like Gopher protocol support).This leaves only a few bits of documentation that did not fit the "Usage" category in my opinion:
Most of these are either specs or for implementors. Not sure what we should do with these.
This does not yet extract the patterns to their own pages as outlined in #15. I will do that as a follow up, but not today 😄
What to do with these? Suggestions inline
Summary:
usage/clientsfor client authors sounds like a good idea 👍Ran a linkchecker yesterday #17, the remaining ones were:
/topics/protocol⇒ We will link to the RESP3 spec on GitHub instead, right?/topics/cluster-spec⇒ Link the wiki/topics/key-specs⇒ Link usage/clients/key-specs/topics/sentinel-clients⇒ Link usage/clients/sentinel-clients/topics/notifications⇒ Link usage/clients/keyspace-notificationsFor now, yes.