PowerShell 7 is Microsoft’s cross-platform automation framework that runs natively on Linux, macOS, and Windows. Built on .NET, it brings a full-featured shell and scripting language to Linux systems, making it a solid choice for administrators managing hybrid environments across Azure, AWS, and on-premises infrastructure. This guide walks through installing PowerShell 7 on Ubuntu 24.04\/22.04 and Debian 13\/12 from the official Microsoft APT repository, then covers practical usage for Linux system administration.<\/p>\n\n\n\n
If you manage infrastructure across multiple platforms, PowerShell 7 gives you a consistent scripting environment everywhere. Here is what makes it worth installing on your Linux boxes:<\/p>\n\n\n\n
Before starting the installation, make sure you have the following in place:<\/p>\n\n\n\n
apt-transport-https<\/code>, curl<\/code>, and gpg<\/code> packages installed<\/li>\n<\/ul>\n\n\n\nUpdate your system packages before proceeding:<\/p>\n\n\n\n
sudo apt update && sudo apt upgrade -y<\/code><\/pre>\n\n\n\nInstall the required dependencies:<\/p>\n\n\n\n
sudo apt install -y curl gpg apt-transport-https software-properties-common<\/code><\/pre>\n\n\n\nStep 1 – Add the Microsoft APT Repository<\/h2>\n\n\n\n
Microsoft maintains an official APT repository for PowerShell and other .NET packages. Start by downloading and installing the Microsoft GPG key:<\/p>\n\n\n\n
curl -fsSL https:\/\/packages.microsoft.com\/keys\/microsoft.asc | sudo gpg --dearmor -o \/usr\/share\/keyrings\/microsoft-archive-keyring.gpg<\/code><\/pre>\n\n\n\nNow add the Microsoft APT repository. Choose the command that matches your distribution.<\/p>\n\n\n\n
For Ubuntu 24.04 (Noble):<\/strong><\/p>\n\n\n\necho \"deb [arch=amd64 signed-by=\/usr\/share\/keyrings\/microsoft-archive-keyring.gpg] https:\/\/packages.microsoft.com\/ubuntu\/24.04\/prod noble main\" | sudo tee \/etc\/apt\/sources.list.d\/microsoft.list<\/code><\/pre>\n\n\n\nFor Ubuntu 22.04 (Jammy):<\/strong><\/p>\n\n\n\necho \"deb [arch=amd64 signed-by=\/usr\/share\/keyrings\/microsoft-archive-keyring.gpg] https:\/\/packages.microsoft.com\/ubuntu\/22.04\/prod jammy main\" | sudo tee \/etc\/apt\/sources.list.d\/microsoft.list<\/code><\/pre>\n\n\n\nFor Debian 13 (Trixie):<\/strong><\/p>\n\n\n\necho \"deb [arch=amd64 signed-by=\/usr\/share\/keyrings\/microsoft-archive-keyring.gpg] https:\/\/packages.microsoft.com\/debian\/13\/prod trixie main\" | sudo tee \/etc\/apt\/sources.list.d\/microsoft.list<\/code><\/pre>\n\n\n\nFor Debian 12 (Bookworm):<\/strong><\/p>\n\n\n\necho \"deb [arch=amd64 signed-by=\/usr\/share\/keyrings\/microsoft-archive-keyring.gpg] https:\/\/packages.microsoft.com\/debian\/12\/prod bookworm main\" | sudo tee \/etc\/apt\/sources.list.d\/microsoft.list<\/code><\/pre>\n\n\n\nVerify the repository file was created:<\/p>\n\n\n\n
cat \/etc\/apt\/sources.list.d\/microsoft.list<\/code><\/pre>\n\n\n\nYou should see the repository line you just added. If the file is empty or missing, repeat the steps above.<\/p>\n\n\n\n
Step 2 – Install PowerShell 7<\/h2>\n\n\n\n
Update the package index to pull metadata from the newly added repository, then install PowerShell:<\/p>\n\n\n\n
sudo apt update\nsudo apt install -y powershell<\/code><\/pre>\n\n\n\nThe installation pulls in the .NET runtime and all required dependencies automatically. Depending on your connection speed, this may take a minute or two.<\/p>\n\n\n\n
Step 3 – Verify the Installation<\/h2>\n\n\n\n
Confirm PowerShell 7 is installed and working by checking the version:<\/p>\n\n\n\n
pwsh --version<\/code><\/pre>\n\n\n\nExpected output:<\/p>\n\n\n\n
PowerShell 7.4.x<\/code><\/pre>\n\n\n\nCheck the binary location to confirm it installed to the expected path:<\/p>\n\n\n\n
which pwsh<\/code><\/pre>\n\n\n\nThis should return \/usr\/bin\/pwsh<\/code>. You can now launch an interactive PowerShell session:<\/p>\n\n\n\npwsh<\/code><\/pre>\n\n\n\nYour prompt changes to PS \/home\/username><\/code>, indicating you are inside a PowerShell session. To exit back to your regular shell, type exit<\/code>.<\/p>\n\n\n\nStep 4 – Basic PowerShell Usage on Linux<\/h2>\n\n\n\n
If you are coming from Bash, PowerShell works differently in some fundamental ways. Here are the essentials to get productive quickly.<\/p>\n\n\n\n
Process Management<\/h3>\n\n\n\n
List running processes with Get-Process<\/code>, which is the PowerShell equivalent of ps aux<\/code>:<\/p>\n\n\n\nGet-Process<\/code><\/pre>\n\n\n\nFilter for a specific process:<\/p>\n\n\n\n
Get-Process -Name \"nginx\"<\/code><\/pre>\n\n\n\nSort processes by CPU usage and show the top 10:<\/p>\n\n\n\n
Get-Process | Sort-Object CPU -Descending | Select-Object -First 10<\/code><\/pre>\n\n\n\nService Management<\/h3>\n\n\n\n
On Linux, PowerShell interacts with systemd through its service cmdlets. Note that Get-Service<\/code> is not natively available on Linux, but you can query systemd directly:<\/p>\n\n\n\n# List all active services via systemctl\n& systemctl list-units --type=service --state=running\n\n# Check status of a specific service\n& systemctl status nginx\n\n# Restart a service\n& sudo systemctl restart nginx<\/code><\/pre>\n\n\n\nThe Object Pipeline<\/h3>\n\n\n\n
The biggest difference from Bash is that PowerShell pipes structured objects, not plain text. This means you can access properties directly without parsing text with awk or grep:<\/p>\n\n\n\n
# Get all processes using more than 100MB of memory\nGet-Process | Where-Object { $_.WorkingSet64 -gt 100MB } | Select-Object Name, @{Name='MemoryMB';Expression={[math]::Round($_.WorkingSet64\/1MB,2)}}\n\n# Get files larger than 50MB in a directory\nGet-ChildItem \/var\/log -Recurse | Where-Object { $_.Length -gt 50MB } | Select-Object FullName, @{Name='SizeMB';Expression={[math]::Round($_.Length\/1MB,2)}}<\/code><\/pre>\n\n\n\nWorking with Files and Directories<\/h3>\n\n\n\n
PowerShell provides cmdlets that map to familiar Linux commands, plus additional functionality:<\/p>\n\n\n\n
# List files (equivalent to ls -la)\nGet-ChildItem -Force\n\n# Read file contents (equivalent to cat)\nGet-Content \/etc\/hostname\n\n# Search for text in files (equivalent to grep)\nSelect-String -Path \"\/var\/log\/syslog\" -Pattern \"error\" -CaseSensitive:$false\n\n# Create a directory\nNew-Item -ItemType Directory -Path \"\/tmp\/powershell-test\"\n\n# Copy files\nCopy-Item -Path \"\/etc\/hosts\" -Destination \"\/tmp\/hosts.backup\"<\/code><\/pre>\n\n\n\nInstalling PowerShell Modules<\/h3>\n\n\n\n
PowerShell modules extend functionality significantly. Install them from the PowerShell Gallery:<\/p>\n\n\n\n
# Search for a module\nFind-Module -Name \"PSScriptAnalyzer\"\n\n# Install a module for the current user\nInstall-Module -Name PSScriptAnalyzer -Scope CurrentUser -Force\n\n# List installed modules\nGet-InstalledModule<\/code><\/pre>\n\n\n\nStep 5 – Install the Az Module for Azure Management<\/h2>\n\n\n\n
If you manage Azure resources, the Az PowerShell module lets you handle everything from VMs to storage accounts directly from your Linux terminal. Launch a PowerShell session and install the module:<\/p>\n\n\n\n
pwsh -Command \"Install-Module -Name Az -Repository PSGallery -Scope CurrentUser -Force\"<\/code><\/pre>\n\n\n\nThe Az module is large, so the installation takes a few minutes. Once installed, verify it:<\/p>\n\n\n\n
pwsh -Command \"Get-InstalledModule -Name Az | Select-Object Name, Version\"<\/code><\/pre>\n\n\n\nConnect to your Azure account and start managing resources:<\/p>\n\n\n\n
# Start PowerShell\npwsh\n\n# Connect to Azure (opens browser for authentication)\nConnect-AzAccount\n\n# List resource groups\nGet-AzResourceGroup | Format-Table ResourceGroupName, Location\n\n# List virtual machines\nGet-AzVM | Format-Table Name, ResourceGroupName, Location\n\n# Get the status of all VMs\nGet-AzVM -Status | Select-Object Name, ResourceGroupName, PowerState<\/code><\/pre>\n\n\n\nStep 6 – Install AWS.Tools for AWS Management<\/h2>\n\n\n\n
For AWS environments, the modular AWS.Tools packages let you install only the service modules you need, keeping things lightweight:<\/p>\n\n\n\n
pwsh -Command \"Install-Module -Name AWS.Tools.Installer -Scope CurrentUser -Force\"<\/code><\/pre>\n\n\n\nThen install the specific service modules you work with:<\/p>\n\n\n\n
pwsh -Command \"Install-AWSToolsModule AWS.Tools.EC2, AWS.Tools.S3, AWS.Tools.IAM -Scope CurrentUser -Force\"<\/code><\/pre>\n\n\n\nVerify the installation and configure your credentials:<\/p>\n\n\n\n
# Start PowerShell\npwsh\n\n# Verify installed AWS modules\nGet-InstalledModule -Name \"AWS.Tools.*\" | Select-Object Name, Version\n\n# Set your AWS credentials\nSet-AWSCredential -AccessKey \"YOUR_ACCESS_KEY\" -SecretKey \"YOUR_SECRET_KEY\" -StoreAs default\n\n# List EC2 instances\nGet-EC2Instance -Region us-east-1 | ForEach-Object { $_.Instances } | Select-Object InstanceId, InstanceType, State\n\n# List S3 buckets\nGet-S3Bucket | Format-Table BucketName, CreationDate<\/code><\/pre>\n\n\n\nStep 7 – PowerShell SSH Remoting<\/h2>\n\n\n\n
PowerShell 7 supports SSH-based remoting, which is the preferred method on Linux. This lets you run PowerShell commands on remote machines over SSH without WinRM.<\/p>\n\n\n\n
Configure SSH for PowerShell Remoting<\/h3>\n\n\n\n
On the remote machine, add a PowerShell subsystem to the SSH configuration:<\/p>\n\n\n\n
sudo tee -a \/etc\/ssh\/sshd_config <<'EOF'\n\n# PowerShell SSH Remoting Subsystem\nSubsystem powershell \/usr\/bin\/pwsh -sshs -NoLogo -NoProfile\nEOF<\/code><\/pre>\n\n\n\nRestart the SSH service to apply the change:<\/p>\n\n\n\n
sudo systemctl restart sshd<\/code><\/pre>\n\n\n\nVerify sshd restarted without errors:<\/p>\n\n\n\n
sudo systemctl status sshd<\/code><\/pre>\n\n\n\nConnect to a Remote Machine<\/h3>\n\n\n\n
From your local PowerShell session, create a remote session over SSH:<\/p>\n\n\n\n
# Start an interactive remote session\nEnter-PSSession -HostName 192.168.1.100 -UserName admin -SSHTransport\n\n# Or run a single command on the remote machine\nInvoke-Command -HostName 192.168.1.100 -UserName admin -SSHTransport -ScriptBlock {\n Get-Process | Sort-Object CPU -Descending | Select-Object -First 5\n}\n\n# Run commands on multiple remote machines\nInvoke-Command -HostName \"server1\",\"server2\",\"server3\" -UserName admin -SSHTransport -ScriptBlock {\n hostname\n Get-Process | Measure-Object | Select-Object -ExpandProperty Count\n}<\/code><\/pre>\n\n\n\nStep 8 – Create and Run PowerShell Scripts on Linux<\/h2>\n\n\n\n
PowerShell scripts use the .ps1<\/code> extension and work the same way on Linux as they do on Windows.<\/p>\n\n\n\nCreate a Simple Script<\/h3>\n\n\n\n
Create a script that gathers basic system information:<\/p>\n\n\n\n
cat > ~\/scripts\/system-report.ps1 <<'SCRIPT'\n#!\/usr\/bin\/env pwsh\n\n# System Report Script\n$report = [PSCustomObject]@{\n Hostname = (hostname)\n DateTime = Get-Date -Format \"yyyy-MM-dd HH:mm:ss\"\n Uptime = (& uptime -p)\n KernelVer = (& uname -r)\n CPUCount = (& nproc)\n TotalMemGB = [math]::Round((Get-Content \/proc\/meminfo | Select-String \"MemTotal\" | ForEach-Object { ($_ -split '\\s+')[1] }) \/ 1MB, 2)\n DiskUsage = (& df -h \/ | Select-Object -Last 1)\n}\n\n$report | Format-List\n\n# Top 5 memory-consuming processes\nWrite-Output \"`n--- Top 5 Processes by Memory ---\"\nGet-Process | Sort-Object WorkingSet64 -Descending | Select-Object -First 5 Name, @{N='MemMB';E={[math]::Round($_.WorkingSet64\/1MB,2)}} | Format-Table -AutoSize\nSCRIPT<\/code><\/pre>\n\n\n\nMake it executable and run it:<\/p>\n\n\n\n
mkdir -p ~\/scripts\nchmod +x ~\/scripts\/system-report.ps1\npwsh ~\/scripts\/system-report.ps1<\/code><\/pre>\n\n\n\nSchedule Scripts with Cron<\/h3>\n\n\n\n
Run PowerShell scripts on a schedule using standard cron:<\/p>\n\n\n\n
# Run the system report every day at 8 AM\n(crontab -l 2>\/dev\/null; echo \"0 8 * * * \/usr\/bin\/pwsh \/home\/$USER\/scripts\/system-report.ps1 >> \/var\/log\/system-report.log 2>&1\") | crontab -<\/code><\/pre>\n\n\n\nVerify the cron entry was added:<\/p>\n\n\n\n
crontab -l<\/code><\/pre>\n\n\n\nStep 9 – Configure PSReadLine for a Better Terminal Experience<\/h2>\n\n\n\n
PSReadLine is bundled with PowerShell 7 and provides command-line editing features similar to what you get with Bash readline. Customize it by creating a PowerShell profile:<\/p>\n\n\n\n
pwsh -Command \"New-Item -Path \\$PROFILE -ItemType File -Force\"<\/code><\/pre>\n\n\n\nAdd your PSReadLine configuration to the profile:<\/p>\n\n\n\n
cat > ~\/.config\/powershell\/Microsoft.PowerShell_profile.ps1 <<'PROFILE'\n# PSReadLine Configuration\nSet-PSReadLineOption -PredictionSource History\nSet-PSReadLineOption -PredictionViewStyle ListView\nSet-PSReadLineOption -EditMode Emacs\nSet-PSReadLineOption -HistorySearchCursorMovesToEnd\nSet-PSReadLineKeyHandler -Key UpArrow -Function HistorySearchBackward\nSet-PSReadLineKeyHandler -Key DownArrow -Function HistorySearchForward\nSet-PSReadLineKeyHandler -Key Tab -Function MenuComplete\n\n# Useful aliases\nSet-Alias -Name ll -Value Get-ChildItem\nSet-Alias -Name grep -Value Select-String\n\n# Custom prompt\nfunction prompt {\n $currentDir = (Get-Location).Path.Replace($HOME, \"~\")\n \"PS $currentDir> \"\n}\nPROFILE<\/code><\/pre>\n\n\n\nVerify the profile loads correctly:<\/p>\n\n\n\n
pwsh -NoExit -Command \"Write-Output 'Profile loaded successfully'\"<\/code><\/pre>\n\n\n\nKey features you now have:<\/p>\n\n\n\n
\n- Predictive IntelliSense<\/strong> – Shows suggestions based on your command history as you type<\/li>\n
- ListView predictions<\/strong> – Displays suggestions in a dropdown list<\/li>\n
- Emacs keybindings<\/strong> – Ctrl+A, Ctrl+E, Ctrl+K, and other familiar shortcuts work as expected<\/li>\n
- History search<\/strong> – Up\/Down arrows search through history matching what you have already typed<\/li>\n
- Tab completion<\/strong> – Menu-style tab completion for commands, parameters, and file paths<\/li>\n<\/ul>\n\n\n\n
Step 10 – VS Code Integration<\/h2>\n\n\n\n
Visual Studio Code with the PowerShell extension provides the best editing and debugging experience for PowerShell scripts on Linux.<\/p>\n\n\n\n
Install VS Code if you have not already:<\/p>\n\n\n\n
sudo apt install -y code<\/code><\/pre>\n\n\n\nIf VS Code is not available from your default repositories, install it from the Microsoft repository (which you already added in Step 1):<\/p>\n\n\n\n
sudo apt update && sudo apt install -y code<\/code><\/pre>\n\n\n\nInstall the PowerShell extension from the command line:<\/p>\n\n\n\n
code --install-extension ms-vscode.powershell<\/code><\/pre>\n\n\n\nVerify the extension is installed:<\/p>\n\n\n\n
code --list-extensions | grep -i powershell<\/code><\/pre>\n\n\n\nThe PowerShell extension provides:<\/p>\n\n\n\n
\n- Syntax highlighting and IntelliSense for .ps1 files<\/li>\n
- Integrated PowerShell terminal<\/li>\n
- Script debugging with breakpoints<\/li>\n
- Code formatting with PSScriptAnalyzer rules<\/li>\n
- Function and variable navigation<\/li>\n<\/ul>\n\n\n\n
To configure VS Code to use PowerShell 7 as the default integrated terminal, add this to your settings.json<\/code>:<\/p>\n\n\n\n{\n \"terminal.integrated.defaultProfile.linux\": \"pwsh\",\n \"terminal.integrated.profiles.linux\": {\n \"pwsh\": {\n \"path\": \"\/usr\/bin\/pwsh\",\n \"icon\": \"terminal-powershell\"\n }\n },\n \"powershell.powerShellDefaultVersion\": \"PowerShell (pwsh)\"\n}<\/code><\/pre>\n\n\n\nTroubleshooting<\/h2>\n\n\n\nPackage not found after adding the repository<\/h3>\n\n\n\n
If apt install powershell<\/code> fails with “Unable to locate package,” the repository may not have been added correctly. Check the repository file:<\/p>\n\n\n\ncat \/etc\/apt\/sources.list.d\/microsoft.list<\/code><\/pre>\n\n\n\nMake sure the codename matches your distribution. Also verify the GPG key is present:<\/p>\n\n\n\n
ls -la \/usr\/share\/keyrings\/microsoft-archive-keyring.gpg<\/code><\/pre>\n\n\n\nIf the file is missing or has zero size, re-download it:<\/p>\n\n\n\n
curl -fsSL https:\/\/packages.microsoft.com\/keys\/microsoft.asc | sudo gpg --dearmor -o \/usr\/share\/keyrings\/microsoft-archive-keyring.gpg<\/code><\/pre>\n\n\n\npwsh crashes or fails to start<\/h3>\n\n\n\n
If PowerShell crashes on launch, it may be a .NET dependency issue. Check the installed dependencies:<\/p>\n\n\n\n
apt list --installed 2>\/dev\/null | grep -E \"libicu|libssl|dotnet\"<\/code><\/pre>\n\n\n\nInstall any missing ICU or SSL libraries:<\/p>\n\n\n\n
sudo apt install -y libicu-dev libssl-dev<\/code><\/pre>\n\n\n\nIf the issue persists, try running PowerShell with trace output to identify the problem:<\/p>\n\n\n\n
DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 pwsh<\/code><\/pre>\n\n\n\nModule installation fails with permission errors<\/h3>\n\n\n\n
Always install modules with -Scope CurrentUser<\/code> to avoid permission issues. If you previously installed a module system-wide and need to fix it:<\/p>\n\n\n\npwsh -Command \"Install-Module -Name ModuleName -Scope CurrentUser -Force -AllowClobber\"<\/code><\/pre>\n\n\n\nSSH remoting fails to connect<\/h3>\n\n\n\n
Verify that the PowerShell subsystem is configured on the remote host:<\/p>\n\n\n\n
grep -i \"subsystem powershell\" \/etc\/ssh\/sshd_config<\/code><\/pre>\n\n\n\nMake sure pwsh<\/code> is installed on the remote machine and the path in the subsystem line is correct:<\/p>\n\n\n\nwhich pwsh<\/code><\/pre>\n\n\n\nAfter making any changes to sshd_config<\/code>, restart the SSH service:<\/p>\n\n\n\nsudo systemctl restart sshd && sudo systemctl status sshd<\/code><\/pre>\n\n\n\nPowerShell profile not loading<\/h3>\n\n\n\n
Check the profile path and verify the file exists:<\/p>\n\n\n\n
pwsh -Command \"Write-Output \\$PROFILE; Test-Path \\$PROFILE\"<\/code><\/pre>\n\n\n\nThe profile directory should be ~\/.config\/powershell\/<\/code>. If the directory does not exist, create it:<\/p>\n\n\n\nmkdir -p ~\/.config\/powershell<\/code><\/pre>\n\n\n\nUpdating PowerShell<\/h3>\n\n\n\n
Since PowerShell is installed through APT, updates come through the standard package manager:<\/p>\n\n\n\n
sudo apt update && sudo apt upgrade powershell -y<\/code><\/pre>\n\n\n\nVerify the new version after upgrading:<\/p>\n\n\n\n
pwsh --version<\/code><\/pre>\n\n\n\nWrapping Up<\/h2>\n\n\n\n
PowerShell 7 on Ubuntu and Debian gives you a capable cross-platform automation tool that fits right into existing Linux workflows. With the Microsoft APT repository configured, you get regular updates through the standard package manager. Combined with the Az and AWS.Tools modules, SSH remoting, and VS Code integration, it provides a solid foundation for managing hybrid infrastructure from a single scripting environment. The object-oriented pipeline alone makes it worth learning if you spend time parsing text output from traditional Linux commands.<\/p>\n\n","protected":false},"excerpt":{"rendered":"
PowerShell 7 is Microsoft’s cross-platform automation framework that runs natively on Linux, macOS, and Windows. Built on .NET, it brings a full-featured shell and scripting language to Linux systems, making it a solid choice for administrators managing hybrid environments across Azure, AWS, and on-premises infrastructure. This guide walks through installing PowerShell 7 on Ubuntu 24.04\/22.04 … Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":5298,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[712,26,299,50,81],"tags":[787,193,145,786,527],"class_list":["post-5295","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-desktop","category-debian","category-how-to","category-linux-tutorials","category-ubuntu","tag-microsoft","tag-os","tag-powershell","tag-shell","tag-windows"],"_links":{"self":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/5295","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/comments?post=5295"}],"version-history":[{"count":2,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/5295\/revisions"}],"predecessor-version":[{"id":164147,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/posts\/5295\/revisions\/164147"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media\/5298"}],"wp:attachment":[{"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/media?parent=5295"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/categories?post=5295"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/computingforgeeks.com\/wp-json\/wp\/v2\/tags?post=5295"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}