The new concept of Packages is superb... but, for organisations who want to have a little more control over what is downloaded from the web, especially in this time of a need to comply with things like Cyber Essentials, allowing everyone to be able to download and locally install a package doesn't fly for lots of larger companies. Can packages be downloaded once and stored at the end of a 'shared' path, like the concept with custom transformers and database connections please. Then central IT can be given the option to control the packages in use and importantly the version deployed to end users. Thanks!
Open
Option for shared Package paths
I agree, I believe it is important to get a balance between allowing users to download different packages, but also important for companies to maintain standardisation across users and departments.
I agree, packages are great and the ability to have a control over the deployment of them would be beneficial to maintain consistency between users and departments. Balancing the freedom of downloading packages and ensuring standardisation across teams is key.
+17- Contributor
Another aspect is if a machine is shared installing per user doesn't provision the machine for all users. The manual install option with 'fme.exe install package' has a --baseDir parameter that presumably exists for the purpose of managing install locations, so lets see it.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.