Future of this project?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 178
- Avg merge
- 15d 9h
- Merged PRs (30d)
- 2
Description
I quite like this rest-server project for its append-only feature and low complexity for a backup storage backend, but development seems to have stalled and while looking for alternatives, I found the rclone serve restic option that seems to work quite similar.
Is there still a reason to use rest-server over rclone serve restic or has rclone made this implementation obsolete?
Does the rclone command above actually work the same as rest-server?
Are there any plans to continue development of rest-server as an independent backend?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or implementation entry point is named; begin by reviewing the project status and the issue's comparison with rclone serve restic. Done would require a maintainer-backed decision about whether rest-server remains needed and what future development, if any, is planned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100