C
C
ctyjiuh2021-10-10 19:54:47
linux
ctyjiuh, 2021-10-10 19:54:47

How to store and manage a large number of scripts for different tasks?

A number of scripts for different tasks have accumulated.
I want to make a directory with the possibility of deployment.
Perhaps ansible is suitable for this, but suddenly there are some other solutions. Preferably open source

Answer the question

In order to leave comments, you need to log in

5 answer(s)
A
Alexander Karabanov, 2021-10-10
@karabanov

Will do.

A
Alexey Dmitriev, 2021-10-10
@SignFinder

version control system like github, gitlab
deploy with one command.

R
rPman, 2021-10-10
@rPman

What does it mean to manage?
Once upon a time, I wrote the most simple .net application, where scripts were named, tags were more precisely placed (the most important process), they were stored in the file name, and there was a simple search engine filter for them with the ability to select scripts and save selections to your bat file (better in a separate entity so that you can immediately load selections and edit).
In practice, I didn’t use this utility, since having beautifully named scripts on hand, you can manually throw them in a text editor (I use far, it’s convenient to search and select files by substring, copy the selected names to the clipboard, and paste directly in a line-by-line list in the form text).
Sorry, the application has not been preserved, but it is really simple, lazily written in the evening

C
CityCat4, 2021-10-11
@CityCat4

Okay, google.
What is VCS, why is it and what are they?

M
MaxKozlov, 2021-10-11
@MaxKozlov

It's not very clear what your goals are.
If you just want to keep and have a history - git, etc.
If you lay it out on different machines, then you need to understand in what composition and why.
Divide according to purpose into modules and completely update modules or individually deploy commands.
If you run it manually or from a scheduler, you can decompose it through GP. or stupidly Copy-Item, it will turn out no worse than ansible.
Again, the question is - who will launch? unless you - the easiest way is to have one repository somewhere on the network, and on the necessary computers just create the Documents\WindowsPowershell folder as a reparse point from this network repository.
The start of PS, of course, will be long, but wherever necessary there will always be the latest version itself.
The documentation, of course, is inside the files themselves. If everything is described correctly, Get-Help will give it out in the best possible way. Well, naming commands according to the standard Verb-PrefixNoun

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question