lawndoc / lawndoc/stack-back

feature: add functionality to restore from backup

Open
#6 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement seeking feedback
Dominant language
Python
Stars
180
Forks
12
PR merge metrics
No merged PRs in 30d

Description

I'm not seeing anything in the docs around how to restore from the backups this application is making, I'm guessing it's just expected to use the restic CLI separately? Potentially interested in contributing this functionality but I wanted to make sure there wasn't already a really clean way of doing it I was missing.

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

The issue names no files, tests, or entry points. First clarify whether restore should be implemented in the application or documented as a separate restic CLI workflow, then inspect how the existing Docker Compose backups are created. Done requires an agreed restore scope and a documented or implemented, verifiable restore path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, python
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.