Tools and Equipment Overview
Loving Tools
- I love my tools because they help me a lot and make the whole process of developing and publishing code much easier through easier testing and writing
VSCode, GitHub Pages Setup
Important Shell Commands
wsl
: Opens the Ubuntu WSL System from Powershellcd
: Changes directory in Ubuntugit pull
: Pulls latest version of a repository from githubapt
: Used to manage packages on Ubuntupwd
: Prints working directory in Ubuntucode
: Opens folder or file to edit in VSCodels
: Lists contents of a directory in Ubuntu
Development Process
- On the local machine, my GitHub files are placed in my WSL Ubuntu System, under the directory
/home/eshaan/vscode/
- On the GitHub cloud, my files are placed under my username (
eshaank1
) and under the specific repository (ex:student
) - I would update my template by running
git pull
in WSL under the specific directory of the repository I want to update
GitHub Pages (localhost vs deployed server)
- Viewing GitHub Pages on localhost is kind of like testing as you can edit and change, but once you commit and push to GitHub then your real deployed server GitHub Page updates to the latest version of your page
- My localhost URL is
localhost:4200/student/
and nobody else can see it - My GitHub Pages URL is https://eshaank1.github.io/student/ and it is publicly viewable on the intenet
DNS
- I did not change the domain name to my student repository
Issues
Issue 1:
- When installing packages, my gem install was not working. Looking thru my version checks, all my installed packages were in older versions. I realized that I was running an old version of Ubuntu (Ubuntu 20) and an old version of WSL.
- To fix this, I uninstalled my WSL and started from scratch. After restarting my host Windows system, I installed a fresh WSL and Ubuntu 22.04. Following this, I was able to install all needed packages and install gem, and from the version checks everything was up-to-date.
Issue 2:
- I had a comment section under all my blog posts which I didnt want
- To fix this, I did some research and realized it was the
comments: false
section of my Jupyter Notebook blog files, which I promptly deleted, fixing my issue