Initial commit

.gitignore

@@ -127,3 +127,6 @@ dmypy.json
 
 # Pyre type checker
 .pyre/
+
+# Jupyter Book
+_build/

book/_config.yml

@@ -0,0 +1,10 @@
+title: Intro to Git, VS Code and Jupyter Books
+author: Caspar Jungbacker
+logo: images/MUDE_Logo-small.png
+
+execute:
+  execute_notebooks: auto
+
+sphinx:
+  extra_extensions:
+  - sphinx_inline_tabs

book/_toc.yml

@@ -0,0 +1,7 @@
+format: jb-book
+root: intro
+
+parts:
+  - caption: Installation and Setup
+    chapters:
+    - file: git-setup

book/git-setup.md

@@ -0,0 +1,54 @@
+# Git
+
+
+
+## Installation
+
+First, we need to install Git itself. 
+
+````{tab} Windows
+1. Go to [this webpage](https://git-scm.com/download/win) and download the correct version of Git for your system.
+2. Execute the installer and go through it. You can leave all options to the default values, **but make sure the option "Git from the command line and also from 3rd-party software" is selected**. Without this option, we won't be able to use Git from VS Code.
+3. Once the installation is finished, check if everything works. Open a command prompt, and execute the command `git`. If Git is installed correctly, you should see some sort of help page. If it outputs an error, then something may went wrong with the installation (you may have selected a wrong option).
+````
+````{tab} MacOS
+Open up a terminal window. Then, type the command `git`. If Git has been installed already, it will output some help. If Git has not been installed, you will get a pop-up that looks something like this:
+
+```{figure} images/install-Xcode-CLT.png
+```
+
+Click on `install`. The installation may take a couple of minutes. Once it's finished, check if everything has been installed correctly by exectuting `git` again.
+````
+
+## Setting up SSH-keys
+
+When we want to visit the MUDE repositories on GitLab, we need to log in. The same holds if we want to interact with these repositories with Git from VS Code. This means that everytime we make a commit, pull, et cetera, we need to provide our password which becomes very tedious. Alternatively, we can provide GitLab with an SSH-key of our sytem, so that GitLab knows it is indeed us that are making the changes to the repository, removing the need to provide a password. 
+
+1. Open up a terminal window (Git Bash on Windows). Next, type (or copy and paste) the following command:
+
+        ssh-keygen -t ed25519 -C "GitLab"
+
+2. You will get output that looks something like this:
+    
+        Generating public/private ed25519 key pair.
+        Enter file in which to save the key (/Users/<user>/.ssh/id_ed25519):
+
+    Press enter to use the default path. Keep note of this path, as we will need to visit it later on.
+
+3. You will now be asked to enter a passphrase, which is recommended but not required. After the command is done executing, it will generate two files: `id_ed25519` and `id_ed25519.pub`. The `.pub` file is the public part of the SSH-Key which we need.
+
+4. Go to [GitLab](https://gitlab.tudelft.nl) and log in. Click on your profile icon on the top-right of the page, then go to Preferences. In the menu on the left, go to SSH-Keys. You are now greeted with a screen that looks like this:
+
+```{figure} images/gitlab-ssh-screen.png
+```
+
+5. Open the `id_ed25519.pub` file that we generated in step 2. Copy its contents and paste it in the 'Key' field of SSH-Keys menu. Give the key a Title and click 'Add key'. 
+
+6. Now test the connection. Go to the terminal (Git Bash on windows) and type:
+
+        ssh -vT git@gitlab.tudelft.nl
+
+    You should get a huge output, but somewhere in that output it should say something like:
+
+        Welcome to GitLab, <netid>!
+

book/intro.md

@@ -0,0 +1,3 @@
+# Home
+
+This is an introduction to Git, VS Code and Jupyter Books for teachers of MUDE. Topics that are covered include: installing Git and VS Code, setting up SSH-keys for GitLab, the basic structure of Jupyter Books and basic Git workflows. 

requirements.txt

@@ -0,0 +1,2 @@
+jupyter-book
+sphinx-inline-tabs