Source: DALL-E 3
An awesome little Project to keep your Desktop tidy!
Explore the docs »
View Demo
·
Report Bug
·
Request Feature
Table of Contents 📋
So, if you're anything like me, you'll realize that it's not always straightforward to manage your data. Whether it's vacation photos, memes, documents, bills, videos, or anything else you need to store, the challenge is real. The task becomes even more daunting when you add the necessity of managing additional backups. And let's face it, your desktop isn't a version control system like git, making it tough to handle all this without considering future changes you might make. This time, I set out to develop an application that corrects past mistakes. It identifies and, if needed, eliminates duplicates.
Here's why:
- Your time should be spent on creating something remarkable, not hunting down duplicates and unnecessary documents.
- Repeating the same tasks over and over isn't efficient.
- Keeping your desktop organized and your storage as minimal as possible is essential. 😄
Admittedly, this project might not be flawless or meet all your needs. So, I plan to make more improvements soon. You're also welcome to suggest changes by forking this repository, creating a pull request, or opening an issue. A big thank you to everyone who takes the time to explore this Repository!
classDiagram
class Your-Program-To-Implement {
DependencyResolver
}
class DependencyResolver{
-CreateHostBuilder(string[] args) IHostBuilder
-ScanUtil
-DeleteUtil
-DuplicateUtil
-FilterUtil
-HashUtil
}
class ScanUtil {
+ScanUtil(IOptions options, ILogger logger)
+GetFiles()
}
class FilterUtil {
+Filter()
}
class DuplicateUtil {
+FindDuplicates()
}
class DeleteUtil {
+DeleteDuplicates()
}
class HashUtil {
+CompareFilehashes()
}
DependencyResolver o-- HashUtil : DI Service
DependencyResolver o-- ScanUtil : DI Service
DependencyResolver o-- FilterUtil : DI Service
DependencyResolver o-- DuplicateUtil : DI Service
DependencyResolver o-- DeleteUtil : DI Service
Your-Program-To-Implement <|-- DependencyResolver : Hosting Extension
As you can see, ByteBrusher provides a bunch of Util Classes to implement in your Codebase. If you have a HostBuilder to build and run your App you can headlessly integrate the Codebase into your DI Container to let the Dependency Injection manage your instances. If you don't use an HostBuilder you're free to directly use the Implementation. Both works like a Charm.
This section should list any major frameworks/libraries used to bootstrap your project. Leave any add-ons/plugins for the acknowledgements section. Here are a few examples.
| Technology | Logo |
|---|---|
| .NET 6 |  |
| C# | |
| Serilog |  |
| NUnit |  |
| Moq |  |
This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.
This is an example of how to list things you need to use the software and how to install them.
- dotnet
dotnet build --release
Below is an example of how you can instruct your audience on installing and setting up your app. This template doesn't rely on any external dependencies or services.
- Request a Pull Request
- Clone the repo
git clone https://github.com/NicoFilips/ByteBrusher.git](https://github.com/NicoFilips/ByteBrusher/
- Restore Nuget packages
nuget restore
- Start the Application
dotnet build --release
I've coded some extension methods to configure your IHost. It also registers Dependency Injection so you can integrate it into your Apps:
private static void Main(string[] args)
{
IHost host = DependencyResolver.DependencyResolver.CreateHostBuilder(args).Build();
CliOptions = host.Services.GetRequiredService<ICliOptions>();
_byteBrusherClient = host.Services.GetRequiredService<IByteBrusherClient>();
_logger = host.Services.GetRequiredService<ILogger<Program>>();
_byteBrusherClient.ExecuteAsync(CliOptions.DeleteFlag, CliOptions.Path);
_logger.LogInformation("---- < ByteBrusher.CLI finished > ----");
}
- Build Architecture
- Add Dependency Injection and HostBuilder Extensionmethod
- Add and Handle CLI Arguments
- Filehash Comparison
- Add Serilog
- Unittest for every Util
- Add Codecoverage > 80%
- Use ML.Net to find redundant Documents
- Memetemplates
- Duplicates
- Find more Contributors!
- Earn the Startruck Badge!
See the open issues for a full list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Distributed under the MIT License. See LICENSE for more information.
Nico Filips - git@nicofilips.de
- CommandLineParser
- NLog
- Img Shields
- Font Awesome
- React Icons
- GitHub Emoji Cheat Sheet