I have been working these past months building my companies extensions for the varies disciplines’ we have. I have built a solid set of tools. Some I built and others I have grabbed from various other projects.
I have started “integrating” this into the pyrevit ecosystem. Mainly allowing users to control what extensions they see via the pyrevit extension manager. Before I was using the custom add folder location for the extensions. To expand on this. When updating my tools I have built a .bat file that deletes the extensions locally on the c drives and then copies the repository from our server. This works well and ensures users get the most up to date tools.
Now we are about to roll this out company wide and we have hit a snag. My IT department wants to package this a single install file.
So I have spent some time reading about the CLI and distributing to a team. I am just lost at where to start. I watched the youtube video about the CLI and and I could along a little.
In my journey so far I have learned I work best when I have something to reverse engineer. So I have some general questions to maybe help me understand the process a bit.
We have a couple of items here. We have pyrevit, my extensions, the need to disable some pyrevit tools(something about great power comes great something…).
From my readings I understand the CLI can handle all of this. My question is how?
Does the CLI generate a install file? Does that install file have pyrevit and my extensions baked in? does it pull from a repository that I can update? Every time I make changes to my extensions do I need to build a new CLI file or does it pull from my repository?
I have limited coding experience and no understanding of how install files are built.
Any help is appreciated.