Profiles, sync directory and docker

[Pete-the-Geek]

Once again, great piece of software!
I have a question about the new profiles and how this works with Sync Directory in Docker.

I have it set up to use docker and have a sync directory to my flights using the docker environment variable sync_logs_path. I then have a profile for each of my children who have their flights in other directories. These directories are not setup for auto sync. When it does an auto sync, does it sync in the current profile or the default profile?

Ideally, it would be good to have one sync directory each profile but using env vars in docker, this isn't possible from what I can see. My concern is that if I'm in one of the other profiles, I wouldn't want the auto sync to pull my flights into that profile, only mine, the default one. Is that how it works?

Incidentally, this profiles improvement fixed my tagging issue completely. Each update is filled with really good improvements! Keep up the great work

[arpanghosh8453]

Hello @Pete-the-Geek I indeed put some thoughts into this. The docker and desktop behave differently in this regard. The desktop version, when a new profile is created, the sync path is set to empty, but for the docker, the set ENV path works as the parent folder for all the profile sync path. So for example, if you have a new profile named Bob and you have the default profile as usual, the parent sync folder directory is used for the default folder, but the Bob profile automatically sets a sync path to be a subfolder of the main parent sync folder named Bob (whatever the profile name is), so if you create a subfolder in the parent sync folder directory with the exact name of the new profile, then it will automatically sync from there. You can also set the upload file path and the sync path to be the same mount path (making them a union), that way whatever you upload, from corresponding profile, goes to the subfolder (auto-created) or parent sync folder (if profile is set as default when uploading) based on the current profile. If you do that union, don't forget to remove the ro tag from the docker volume mount. I hope these make sense, let me know if you have more questions.

[Pete-the-Geek]

That is amazing! Perfect for what I'm after. And yes, you have put a lot of thought into it!

[arpanghosh8453]

@Pete-the-Geek please give it a try and let me know if it is working as expected and I can mark this as answered in this thread ✨

[Pete-the-Geek]

That works exactly as described and does exactly as needed! Many thanks

[arpanghosh8453]

@Pete-the-Geek would be surprised if it did not, but it's always good to have some external verification! Thank you for the question and confirmation!