automation Automated actions on conditions for (quarantine'd files/folders/users/etc)

[Ornival]

I would love to simplify or automate uploads from (guest) users to a shared folder with customised conditions. Now I need to define specific groups and user and separate (home) folders, where an uploaded file goes to first for review, before releasing it and/or leaving the (RW/own) settings. Something like a menu where you can choose or make a selection of actions on files/folders/share/users/groups etc. Then all is needed just a condition to trigger the automation or a button click.

(Context: Me and my friends started making our own (steering motorised) kites/hang gliders. Design started in AutoCAD and we pretty much loved the AutoDesk ecosystem and now nearly all is done within Inventor and Nastran. Flight control (orientation, positioning and alignment) is realised by using several sensors and actuators.)

I share my git and AutoDesk Vault (like git but for parts, assemblies and other CAD files) with various people - some I don't even know personally - and streamlining the collaboration is sometimes a hassle because someone else managed to work on a file/project and creating an unintended fork, resulting in wasted effort. Both git and Vault have their own workflow, which would be fine if there were clear boundaries between me, my (own) groups and those exceeding my ring of trust.

A known user can create a new user, which automatically falls in this user's group, with similar permissions to read from/contribute to files from the master. In Vault you can withhold any changes going upstream until the new version is approved., but that makes the new version folder locked/inaccessible for anyone else than the approved supervisors/superusers if the shared folder and files live outside of AutoDeks Vault. Currently I mitigate this by copying everything over to a separate share...

ACLs would normally be the way to go (on a Synology), but I need to manually change permissions and group members every time, when I/we need to synch both the code in git and the assemblies in Vault to review  the impact of the changes.

I tried scripting these permission changes on both debian/TrueNAS, but while it makes no sense allowing a non-programmer to trigger the script, it is needed to allow key members to unlock/unfreeze the CAD project (or better: the projectiles that live within Vault) to work on some other features.

 

I would not ask for this very niche n=1 feature if I was an apt programmer in any other language than beer, cigarettes and assembly 😞

Not sure if I even make sense (I'm dutch and it's always baffling how people are unable to read my thoughts)

Edited December 1, 2024 by Ornival
correcting stupid errors