Mount remotes if they need to be accessed

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
infrastructure

Research direction

Start by reviewing the issue description and the linked pull request #590 for the intended remote-mount behavior. Identify the project's path-access entry points and existing hook mechanisms before defining whether mounting occurs on access or through before/after hooks. Done should include a decided scope and tested mount and dismount lifecycle.

Written by the indexing model from the issue text.

Description

Feature

If any/a path is accessed and it does not exist or is somehow marked as a mountable point it should try to mount that point first. Or the system should support a package that mounts things in a before hook and dismounts in a after hook.

See for more information: https://github.com/meskyanichi/backup/pull/590

Dominant language
No language data
Stars
6
Forks
0
No merged PRs in 30d

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.

More from backup/backup-features

All issues in backup/backup-features

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.