this will make us to share dynamo easily
The easiest way is probably to just get IT to make a logon script that copies the contents from a shared folder into the appdata folder of a user
1 Like
I agree with @Garbage_Collector. You can create a Dynamo script to copy network packages to a local folder if an official startup script isn’t an option. But it’s best to have a team or individual in charge of maintaining package installs and versioning.
2 Likes
The best way to scale Dynamo is to teach users how to use Dynamo. Expecting them to get value without knowing it doesn’t work well. So your best best is to let workspace references do it’s job and teach users how to install the references. Education is actually easiest.
Beyond that, your next best option is to manage your content (graphs) and environments (packages) well, and have IT or a paid service deploy things.
Trying to script your way around the issue is a long and painful ride which ends in frustration.
2 Likes
sure❤
sure❤ i am teaching around me how its work, i am just curious that is there an shortcut that’s it!!
1 Like
Hi.
You can write a script that downloads the file as zip, and unzip it using python.
Next write a script that edits the dynamo config file to add a Custom Package folder path to unzipped folder.
The problem is that if you do this using dynamo than it reverses it to original after closing dynamo.
To bypass it you need to change the file flag to readonly at the end.
Next time you need to run the script again to turn the read only flag off.
Just place the packages in the appdata folder in the default location. Wouldnt want to be meddling with the config files
All described actions are risky if performed without caution.
Theese config files are not criticall to the system. If deleted, Revit will regenerate default verison.
For packages. I think that placing them in default folder, automatically using Dynamo, wont work.
If you place them manually or using admin rights, thats different story.