Add some GIfs, etc to local dev

Author: JDubbTX

Gemfile.lock

@@ -1,19 +1,20 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.0.4.3)
+    activesupport (7.0.8)
       concurrent-ruby (~> 1.0, >= 1.0.2)
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)
       tzinfo (~> 2.0)
-    addressable (2.8.4)
+    addressable (2.8.5)
       public_suffix (>= 2.0.2, < 6.0)
+    base64 (0.1.1)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
     coffee-script-source (1.11.1)
     colorator (1.1.0)
-    commonmarker (0.23.9)
+    commonmarker (0.23.10)
     concurrent-ruby (1.2.2)
     dnsruby (1.70.0)
       simpleidn (~> 0.2.1)
@@ -23,8 +24,9 @@ GEM
     ethon (0.16.0)
       ffi (>= 1.15.0)
     eventmachine (1.2.7)
-    execjs (2.8.1)
-    faraday (2.7.4)
+    execjs (2.9.1)
+    faraday (2.7.11)
+      base64
       faraday-net_http (>= 2.0, < 3.1)
       ruby2_keywords (>= 0.0.4)
     faraday-net_http (3.0.2)
@@ -86,7 +88,7 @@ GEM
       activesupport (>= 2)
       nokogiri (>= 1.4)
     http_parser.rb (0.8.0)
-    i18n (1.13.0)
+    i18n (1.14.1)
       concurrent-ruby (~> 1.0)
     jekyll (3.9.3)
       addressable (~> 2.4)
@@ -209,20 +211,20 @@ GEM
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.18.0)
-    nokogiri (1.15.0-x86_64-linux)
+    minitest (5.20.0)
+    nokogiri (1.15.4-x86_64-linux)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
       sawyer (~> 0.9)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
     public_suffix (4.0.7)
-    racc (1.6.2)
+    racc (1.7.1)
     rb-fsevent (0.11.2)
     rb-inotify (0.10.1)
       ffi (~> 1.0)
-    rexml (3.2.5)
+    rexml (3.2.6)
     rouge (3.26.0)
     ruby2_keywords (0.0.5)
     rubyzip (2.3.2)

_posts/2023-05-11-RPG-CICD-Setting-up-local-development.markdown

@@ -4,33 +4,69 @@ title:  "RPG CiCd - Part 2 - Local Development Setup"
 date:   2023-05-14 20:18:07 -0500
 categories: VSCode IBM i Setup SSH
 ---
-There are a few hurdles to overcome to achieve local rpgle / clle development.  This blog post will help you though those hurdles.
+
+## LOCAL IBM i development setup
+
+There are a few hurdles to overcome to achieve local rpgle / clle development.  This blog post will help you though those hurdles.  The outcome is that changes you make on your local PC pushed to an IFS directory and compiled, while also being synchronized with online source/version control, such as Github, Bitbucket, Gitlab, etc.  
+
+> To start, we will work on the IBM i development partition where source will be built. 
 
 ### You need a home directory
+
 You need to have a home directory on your development IBM i partition.  It doesn't matter how you add it, there are several ways.  If we assume you can't SSH, you can always do it with a CRTDIR command in the greenscreen.
 
 ![Please, not more greenscreen!](/assets/images/CRTDIR.png)
 
 ### Set default shell to Bash
+
 If you haven't done it yet, follow instructions in [this link](https://ibmi-oss-docs.readthedocs.io/en/latest/troubleshooting/SETTING_BASH.html) to set Bash as your default shell.  For historical reasons, IBM i has ksh (kornshell) as the default shell.  Most folks prefer Bash. Most open source examples you find on the web use Bash.  The absolute easiest way to do it is to run the following command in ACS Run SQL Scripts tool:
 
 ```SQL
 CALL QSYS2.SET_PASE_SHELL_INFO('*CURRENT', '/QOpenSys/pkgs/bin/bash')
 ```
 
-### VSCODE setup
-1. Install VSCODE
-   Go to the [Visual Studio Code download page] and install it on your machine.  Once installed, it will notify you when there are updates and prompt you to update it, quite seamlessly.   It usually only takes a few seconds.
-2. Install extensions to VSCODE
-   There are a multitude of extensions available for VSCODE.  They are available to install in the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/VSCode), or you can access the same marketplace from within the VSCODE in the extensions sidebar view:
+> The next few steps will be done on your local PC.  Windows steps are pictured, but the process isn't any different on a Mac.
+
+### VSCODE and Git setup
+
+#### Install VSCODE
+
+Go to the [Visual Studio Code download page] and install it on your machine.  Once installed, it will notify you when there are updates and prompt you to update it, quite seamlessly.   It usually only takes a few seconds.
+
+#### Install GIT (local)
+
+VSCODE automatically prompts you to download and install it the first time you click on the the **source control** view in the activity bar.  After GIT install and reload of VSCODE, you should see the **Open Folder** and **Clone Repository** buttons in the **source control** view.
+
+![Downloading GIT](/assets/images/VSCODE_Install_GIT.gif) 
+
+![Install GIT](/assets/images/VSCODE_Install_GIT_2.gif)
+
+#### Install VSCODE extensions
+
+There are a multitude of extensions available for VSCODE.  They are available to install in the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/VSCode), or you can access the same marketplace from within the VSCODE in the extensions sidebar view:
    ![Install IBM i Development Pack](/assets/images/InstallIBMiDevelopmentPack.jpg)
 
-   Here are the most essential ones.
-   *  [IBM i Development Pack](https://marketplace.visualstudio.com/items?itemName=HalcyonTechLtd.ibm-i-development-pack) This will install 13 extesions, all helpfull for developming on IBM i, including the Code for IBM i extension.
-   *  [GitLense](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) This gives you full visibility to your git repository, both locally and remote.
-3. Log in to your IBM i with the Code for IBM i extension.
-4. [Configure your Settings](/_posts/2023-05-18-VSCODE-Settings-for-IBM-i-development.markdown)
-5. Set your deploy IFS target directory
+Here are the essential ones for IBM i development.
+
+*  [IBM i Development Pack](https://marketplace.visualstudio.com/items?itemName=HalcyonTechLtd.ibm-i-development-pack) This will install 13 extesions, all helpfull for developming on IBM i, including the Code for IBM i extension.
+
+*  [GitLense](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) This gives you full visibility to your git repository, both locally and remote.
+
+4. Log in to your IBM i with the Code for IBM i extension.
+
+5. [Configure your Settings](/_posts/2023-05-18-VSCODE-Settings-for-IBM-i-development.markdown)
+
+### Create a project
+
+There are two approaches to getting a project to sync to online source control.  The easiest approach is to create a blank project online, then clone it locally.  In this tutorial, we will use gitlab, but the same concept applies if you are using Github, Bitbucket, and the like.
+
+1. Log into your Gitlab account and create a new project.  Think of a good name for your project.  This will end up being the directory name where the source is stored.  For this tutorial we will call it "My First IBM i Project".
+
+![CiCd pipeline](/assets/images/Gitlab_Create_New_Project.gif)
+
+2. Copy the project SSH clone URL and clone it
+
+5. Set your deploy IFS target directory - do this in the IFS 
 6. Set up your 
 
 ### Setting up your IBM i profile