extern/PowerShell
1
0
Fork 0
mirror of https://github.com/fleschutz/PowerShell.git synced 2025-04-28 20:58:46 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update FAQ.md

Browse Source
This commit is contained in:
Markus Fleschutz 2023-05-10 14:26:07 +02:00 committed by GitHub
parent 84ae222263
commit c6b3c7a00f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Docs/FAQ.md
View File

@ -35,7 +35,7 @@ NOTE: the group policy object (GPO) settings of your organization might disallow
``` ```
</details> </details>
<details><summary>How to get the PowerShell Scripts?</summary> <details><summary>How to get the PowerShell scripts?</summary>
* When using **Git**, execute in a terminal window: `> git clone https://github.com/fleschutz/PowerShell` * When using **Git**, execute in a terminal window: `> git clone https://github.com/fleschutz/PowerShell`
* When using **Chocolatey**, execute in *Windows PowerShell (Administrator)*: `> choco install powershell-scripts --version=0.4` * When using **Chocolatey**, execute in *Windows PowerShell (Administrator)*: `> choco install powershell-scripts --version=0.4`
@ -60,11 +60,11 @@ NOTE: the group policy object (GPO) settings of your organization might disallow
</details> </details>
<details><summary>How to execute PowerShell Scripts in Jenkins?</summary> <details><summary>How to execute PowerShell scripts in Jenkins?</summary>
Install the 'PowerShell plugin', it allows Jenkins to invoke PowerShell as build scripts. It uses PowerShell.exe on Windows and pwsh on Linux. Install the 'PowerShell plugin', it allows Jenkins to invoke PowerShell as build scripts. It uses PowerShell.exe on Windows and pwsh on Linux.
</details> </details>
<details><summary>What about Security?</summary> <details><summary>What about security?</summary>
* Execute scripts only that you trust (and/or where you have checked the code before)! * Execute scripts only that you trust (and/or where you have checked the code before)!
* Prefer SSH Remoting instead of PowerShell Remoting * Prefer SSH Remoting instead of PowerShell Remoting