mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #297] [Feature]: Restructure File Manager for Network sharing #182
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#182
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @atl285 on GitHub (Feb 8, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/297
Problem or Use Case
I'm testing BamBuddy since a few days now. The project feature could be very interesting. But for me it has a major problem: You have to download and upload files if you change something on the project. If I look at the directory structure on the file system, it doesn't correspondent to the View in BamBuddy:

This makes sense because you're managing this using a database.
Proposed Solution
My preferred solution would be, that folders and files from the File Manager view are presented in the same way on the real file system and changes (like adding and removing files) should be tracked by a file watcher. This makes the implementation a lot complexer, but this enables a much more comfortable option to work with the project files: sharing via network (especially SMB). There's simple docker container (

dperson/samba), which is easy to install and can share folders over network:This way I have all my project file in one location and can work directly with it. And thanks BamBuddy I have the project workflow, prints and all the stuff in one location. 😄
Alternatives Considered
Not realy.
Feature Category
File Manager
Priority
Would improve my workflow
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Feb 8, 2026):
What's about #124
@atl285 commented on GitHub (Feb 8, 2026):
Oh, maybe it describes the same. It seems I have used the wrong search terms. 😳 I think for both a rewrite of the internal file handling is needed. Right?
@maziggy commented on GitHub (Feb 8, 2026):
Would make sense. Will be covered in #124