<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps on wriotsec</title><link>https://www.wriotsecurity.com/categories/devops/</link><description>Recent content in DevOps on wriotsec</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 31 Dec 2021 22:48:24 -0600</lastBuildDate><atom:link href="https://www.wriotsecurity.com/categories/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting up WSL, Ansible, and Packer for DevOps</title><link>https://www.wriotsecurity.com/posts/setting-up-wsl-ansible-and-packer-for-devops/</link><pubDate>Fri, 31 Dec 2021 22:48:24 -0600</pubDate><guid>https://www.wriotsecurity.com/posts/setting-up-wsl-ansible-and-packer-for-devops/</guid><description>
&lt;p&gt;WSL stands for Windows Subsystem for Linux. It allows Windows to run a lightweight Linux environment for running Linux binaries on Windows. I have not set it up from scratch by myself but have used it in the past with lab VM's like the one associated with &lt;a href="https://www.antisyphontraining.com/pay-what-you-can/"&gt;Black Hills Information Security's Pay What You Can&lt;/a&gt; courses. However, over the holidays I got myself an upgraded laptop and so I thought I would give it a try!&lt;/p&gt;</description></item></channel></rss>