Installations to be made on windows while onboarding...

o Install WSL2
• You must be running Windows 10 version 2004 and higher (Build 19041 and
higher) or Windows 11 - To check your Windows version, hit Windows Key +
x and click on system. There you’ll see your Windows version.
• To run WSL2, you’ll need to enable to additional Windows features: Hyper-V
and Windows Subsystem For Linux . To get both up and running, look for “Turn
Windows features on or off” in the start menu.
• If you have those selected, click OK and go through with the reboot of your
system.
• In PowerShell administrator: wsl --install
• Setup WSL: open the distribution (Ubuntu by default) using the Start menu.
You will be asked to create a User Name and Password for your Linux
distribution.
• Now, we’ll go ahead and switch this installation from WSL1 to WSL2. To do
this, open a windows powershell (Run as admin), and execute the following
commands:
wsl -l -v
wsl --set-version Ubuntu-18.04 2
• This will convert our WSL1 to a WSL2. We can verify the conversion was
successful, with the following command:
wsl -l -v
• With that done, we have our WSL2 setup. Next up, setting up the Windows
Terminal.
o Install Windows Terminal
• Search for "Windows Terminal" in Microsoft Store
o Setup work environment in terminal
• Set Ubuntu as default tab in terminal
• Install MesloLGS NF font family from
here https://github.com/romkatv/powerlevel10k#meslo-nerd-font-patched-for-
powerlevel10k
• Set MesloLGS NF as default font in settings.json in Terminal
• Open settings.json
• Add "fontFace": "MesloLGS NF" in defaults JSON object somewhere
in profiles
• Update & Install zsh
sudo apt update
sudo apt-get install zsh curl git
• Install oh-my-zsh
sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-
zsh/master/tools/install.sh)"
• Install powerlevel10k theme
• git clone --
depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTO
M:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k
• Set ZSH_THEME="powerlevel10k/powerlevel10k" in ~/.zshrc.
• Restart terminal, follow prompts to set terminal as per your need.
o Setup python via pyenv: https://realpython.com/intro-to-pyenv/
• sudo apt-get install -y make build-essential libssl-dev zlib1g-dev \libbz2-
dev libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev \libncursesw5-
dev xz-utils tk-dev libffi-dev liblzma-dev python-openssl
 • curl https://pyenv.run | bash
• Restart the terminal again and perform below steps
• pyenv install 3.9.6
• pyenv global 3.9.6
• pip install pipenv
• add below 4 commands in ~/.zshrc file using editor
vi ~/.zshrc
export PATH="$HOME/.pyenv/bin:$PATH"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
eval "$(pyenv init --path)"

• Restart the terminal to check python’s version to point as 3.9.6

“python --version”
o Setup stskeygen: https://support.cimpress.cloud/hc/en-us/articles/360049195674-
stskeygen-Installation-and-Overview
1. Install homebrew by performing below steps -
• git clone https://github.com/Homebrew/brew homebrew
• eval "$(homebrew/bin/brew shellenv)"
• brew update --force --quiet
• chmod -R go-w "$(brew --prefix)/share/zsh"
2. brew tap cimpress-mcp/stskeygen-installers https://github.com/Cimpress-
MCP/stskeygen-installers.git
3. brew install stskeygen
o Setup Git:
• Install the git on desktop. - https://git-scm.com/download/win
• VS code - https://code.visualstudio.com/download
• Extension needed - ‘’JIRA and Bitbucket Official’
• To setup SSH keys - https://support.atlassian.com/bitbucket-cloud/docs/set-
up-an-ssh-key/
• We must set up Bitbucket from GIT bash with following commands:
git config --global user.name "First Name" (user.name will be Bitbucket username)
git config --global user.email “youremail@pens.com"
Git Workflow -
• create a feature branch using JIRA ticket
• clone the repository on which you will be working (if already done - skip the
step)
• checkout your feature branch
• to make necessary changes needed for your ticket
• save the changes locally using CTRL+S
• test the changes locally
• stage the changes for tracking purpose
• commit the changes with a message
• push the changes to your remote feature branch
• raise a PR against master branch from bitbucket console
• to get it reviewed by reviewers and update the changes if asked
• post approval -> merge the PR to get the changes reflected in master