restic / restic/rest-server

quota

Open
#305 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.5k
Forks
178
Avg merge
15d 9h
Merged PRs (30d)
2

Description

Output of rest-server --version

rest-server version rest-server 0.13.0 compiled with go1.22.5 on linux/386

What should rest-server do differently?

Add quota support

What are you trying to do? What is your use case?

I run a rest-server for our university which has several hundreds institutes and departments.
I have no access on their servers, they just use our central backup server.
I want to limit the storage space for them:
Institute A may use X TB backup storage
Institute B may use Y TB backup storage
...

Did rest-server help you today? Did it make you happy in any way?

Much easier und more fun than IBM Storage Protect :-)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by reviewing rest-server's REST backend and storage handling, then clarify how institutes would be identified and how per-institute limits should be enforced; done means the quota behavior is specified for the stated multi-institute use case.

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
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.