Easier way to delete remote projects (and files) locally

Open
#7,967 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop

Research direction

Start with the remote dialog and project browser described in the issue, and inspect how locally cached projects and files are represented under the Binary Ninja remote directory. Define the scope for removing local copies without server deletion, then verify that the relevant UI actions leave remote projects intact and reclaim local storage.

Written by the indexing model from the issue text.

Description

Component: Collaboration Edition: Ultimate Effort: Low Impact: Low UI: Projects

I have quite a few remote projects and these projects locally take up over 100gb of storage, I need to clear them out locally without deleting them from the remote.

To do this now I need to open each project I no longer want and get the guid of it, then go to '/Users/emesare/Library/Application Support/Binary Ninja/remote' and delete the associated bnpr.

If I want to delete specific files in a remote i need to open the project, locate the file and then open the file location and delete. Seeing as i have open and close 200 remote projects this is quite tedious if i am looking to only delete files which take up a considerable amount of space. This particular issue of trying to delete remote project files locally I am less interested in, I would accept just the option to delete remote projects from the remote dialog.

I would prefer if the remote dialog offered a way to delete the project locally (that requires no deletion permissions on the server) and a way to delete project files locally (that requires no deletion permissions on the server) from the project browser.

Related https://github.com/Vector35/binaryninja-api/issues/7955

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

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 Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.