KASM Workspace Prep

Any time you start work on a new KASM workspace perform these steps

  1. Open a Linux-supported Terminal

  2. Setup personal GitHub variables: Change youremail@gmail.com and yourGHID to match your credentials. This is required prior to syncing code to GitHub.

     git config --global user.email jmort1021@gmail.com
 git config --global user.name jm1021

  3. Move to your home directory:

     cd

  4. Setup a directory and clone your projects:

     mkdir nighthawk 
 cd nighthawk 
 git clone https://github.com/nighthawkcoders/portfolio_2025.git
  5. Tool preparation for GitHub Pages 
     cd ~/nighthawk/portfolio_2025/scripts
 ./activate.sh
  6. VSCode preparation Launch VSCode from the desktop and install or adjust install on the following extensions. Here is a visual of extension
    • Python. Required for Python. Be sure to upgrade to pre-release after install.
    • Jupyter Required for Jupyter Notebooks. Be sure to upgrade to pre-relase after install.
    • GitLens Required for easy GitHub operations.
  7. Required Close everything.
    • Close any terminals open The environment of terminal will not activate until a new terminal is opened.
    • Close VSCode It is always best to close a tool when you activate new features.

Project Preparation

Any time you start work on a new project perform these steps. Change https://github.com/nighthawkcoders/john_2025.git to match your repo.

  1. Clone your projects:

     cd nighthawk 
 git clone https://github.com/jm1021/john_2025.git
  2. Tool preparation for GitHub Pages 
     cd ~/nighthawk/john_2025
 ./scripts/venv.sh
  3. Start your project specific virtual environment with bundle requirements 
     source venv/bin/activate
 bundle install
  4. Load VSCode 
     code .
  5. Verify the following After installation it is alway best to do some testing and checks. It is likely you will need to create a keyring and authenticate with GitHub during this process.
    • Open Terminal in VSCode, verify venv is present. If not, make sure you have pre-release of Python Extension.
    • Perform make in terminal and verify and run server. If it delays or fails, make sure you have venv in terminal and run have run bundle install
    • Open an Jupyter Notebook, set a kernel, verify by running a code cell. If you can’t set a kernel be sure you have pre-release verion of Jupyter Extension.
    • Make a commit to GitHub. If you have failures it could be related to GitHub autentication, git config environment variables, or kingring password.