+
+### Getting into the Insider Program
+
+If you're not yet in the insider program, you can visit the
+following link for very detailed instructions on how to
+enroll into Insider Program, and install WSL 2:
+
+> [Official Microsoft's WSL2 Installation Instructions](https://docs.microsoft.com/en-us/windows/wsl/wsl2-install)
+>
+> [How to install Windows Subsystem for Linux 2 on Windows 10](https://pureinfotech.com/install-windows-subsystem-linux-2-windows-10/)
+>
+> *Note: These guides includes WSL2 installation too*
+
+ If you want the short version, go to Settings > Update
+& Security > Windows Insider Program. There, make sure to get onto the
+**SLOW ring**. At the time this guide was first written, you don't need
+ get into the Fast ring, so let's avoid unnecessary problems.
+
+
+
+After getting into the Slow ring, restart your PC if
+required. Then, check windows for updates on Settings >
+Uptade & Security > Windows Update. **Once your Windows
+build is above build 18917, you can continue.**
+
+### Installing WSL2
+
+Now that you have the right OS build, you can enable WSL2
+on your computer **manually** or **via Poweshell**:
+
+#### Powershell instructions
+
+Open up Powershell as Admin by right clicking the Windows
+start button and selecting "Windows Powershell (Admin)".
+Then, paste and run the following commands and restart your computer
+after they are done running:
+
+```Powershell
+dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
+
+dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
+```
+
+#### Manual instructions
+
+Go to Windows' start menu, and type "Turn Windows features
+on or off". If you click in the right item, you'll see the
+window below. Make sure to check "Windows Subsystem for
+Linux"
+
+
+
+You'll probably be asked to restart your PC, please do so now.
+After enabling Windows Subsystem for Linux, then we have to
+install a Linux *distro* (short for distribution). Open up
+the Windows Store app, and search for "Linux". You should
+see something like the image below:
+
+
+
+Install "Ubuntu" from the linux subpage. It will take a few
+seconds. After it is installed, launch it. You will see a
+*terminal* window showing the following message:
+
+```bash
+Installing, this may take a few minutes...
+```
+
+You will be asked to create a default UNIX user account.
+Make sure it is a simple username (avoid mayus, symbols,
+etc). Then type a password (*no characters will show
+while you type, so make sure you get it right!*) and
+confirm it. If everything went according to plan, you
+should see the following message:
+
+```none
+Installation successful!
+
+To run a command as administrator (user "root"), use
+"sudo `
+
+If your distro's version is NOT 2, then you definitely have to run the
+command below. If it is 2, you should run it anyways just in case:
+
+```Powershell
+wsl --set-version +
+ *GoRails tutorial example* +
+ +As you follow the steps above, make sure to read the return messages from +the terminal. If there's anything funky or you get an error message, stop +and debug it! The order in which things are done makes a big difference. + +Just in case the guide above changes, I will show the instructions for Ruby +version 2.7.1 and Rails version 6.0.2.2 below, with some handy tips for +beginners. + +### Installing Ruby and Updating your Distro + +Ruby is the backend language that powers Rails apps. This means that it +controls the logic via scripts, just like Python or R. You can learn more +about this [here](https://www.ruby-lang.org/en/about/) and [here](https://ruby-lang.co/what-is-ruby/). + +First, let's get your distro upgraded! In Linux speech, "update" means +getting the latest version numbers, and "upgrade" means actually downloading +and installing them. Run the following code in Ubuntu: + +```bash +sudo apt update && sudo apt dist-upgrade && sudo apt-get autoremove && sudo +apt-get clean +``` + +If you are asked to proceed, type "Y" and hit enter + +
+
+Now that your distro's libraries are up-to-date, let's proceed to install
+ruby. Run the following 2 lines in your Ubuntu terminal:
+
+```bash
+sudo apt install curl
+curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
+curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
+echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
+
+sudo apt-get update
+
+sudo apt-get install git-core zlib1g-dev build-essential libssl-dev libreadline-dev libyaml-dev libsqlite3-dev sqlite3 libxml2-dev libxslt1-dev libcurl4-openssl-dev software-properties-common libffi-dev nodejs yarn
+```
+
+That's a long code! If you are promped for your password, please input it
+and press enter. This is because we invoked sudo (*pro tip: sudo won't ask
+you for a password for some time after inputting it successfully*).
+
+Now, let;s install Ruby using `rbenv`. Run the following lines in your
+bash terminal (same Ubuntu window):
+
+```bash
+cd
+git clone https://github.com/rbenv/rbenv.git ~/.rbenv
+echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
+echo 'eval "$(rbenv init -)"' >> ~/.bashrc
+exec $SHELL
+
+git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build
+echo 'export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH"' >> ~/.bashrc
+exec $SHELL
+
+rbenv install 2.7.1
+rbenv global 2.7.1
+ruby -v
+```
+
+Now let's install bundler, which is an impotant gem (ruby libary):
+
+```bash
+gem install bundler
+rbenv rehash
+```
+
+### Configuring Git
+
+If you don't already have a GitHub account, [create one now](https://github.com/join?source=header-home).
+This will come very handy in the future, and some things we do here (like
+creating SSH keys) will be useful outside of Git and Github, so no skipping.
+
+After creating your Github account (or if you already had one), paste the
+following commands in your terminal, replaceing the items in CAPS with your
+name (use your UNIX username for simplicity) and github email:
+
+```bash
+git config --global color.ui true
+git config --global user.name "YOUR NAME"
+git config --global user.email "YOUR@EMAIL.com"
+ssh-keygen -t rsa -b 4096 -C "YOUR@EMAIL.com"
+```
+
+When prompted for a location, just press enter. Same for password, no need
+to add a password to this for now. If successful, this is a sample output:
+
+```none
+Generating public/private rsa key pair.
+Enter file in which to save the key (/Users/USERNAME/.ssh/id_rsa):
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /Users/USERNAME/.ssh/id_rsa.
+Your public key has been saved in /Users/USERNAME/.ssh/id_rsa.pub.
+The key fingerprint is:
+80:5f:25:7c:f4:90:aa:e1:f4:a0:01:43:4e:e8:bc:f5 vivek@desktop01
+The key's randomart image is:
++--[ RSA 2048]----+
+| oo ...+. |
+|.oo . .ooo |
+|o .o. . .o . |
+| o ...+o. |
+| o .=.=S |
+| . .Eo . |
+| |
+| |
+| |
++-----------------+
+```
+
+We just generated fancy, industrial-grade security keys. This is much more
+convenient and secure than using passwords (even though you would never
+re-use a password, rigt?). So we'll paste the encrypted PUBLIC key into
+Github, which will accept our connections in the future without the need
+of a password. Get your public key by running the following command:
+
+```bash
+cat ~/.ssh/id_rsa.pub
+```
+
+This will output the contents of the "id_rsa.pub" file, which holds your
+SSH public key. Once you get that output, you can select it with your
+mouse and right-click it to copy it (remember, CTRL+C doesn't copy things
+in the Ubuntu bash terminal).
+
+> Note: the ~ variable is the same as typing \$HOME, which is a variable as
+> indicated by the preceding dollar sign (\$). This is just a shortcut to
+> indicate your user's home folder, very similar to your user folder in
+> Windows 10.
+
+The command's output should look something like this:
+
+```none
+ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSU
+GPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3
+Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA
+t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En
+mZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx
+NrRFi9wrf+M7Q== USER@HOSTNAME
+```
+
+Now, let's head to [Github](https://github.com/settings/keys) and paste that
+SSH key [in here](https://github.com/settings/ssh/new). Remember to give this
+key a name so you remember it's your WSL 2 connecting to Github. Let's
+double-check that everything worked out, run the following command:
+
+```bash
+ssh -T git@github.com`
+```
+
+You should see something like this:
+
+```none
+Hi USERNAME! You've successfully authenticated, but GitHub does not provide shell access.
+```
+
+Great! So now we have a) WSL 2 set up, b) an Ubuntu distro installed and
+updated, c) Ruby installed, and d) an SSH key pair created and successfully
+connected to Github. We're almost there.
+
+### Installing Rails
+
+Run the following commands in your bash terminal:
+
+```bash
+curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
+curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
+echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
+
+sudo apt update
+sudo apt-get install -y nodejs yarn
+```
+
+This may take a few minutes as you're installing NodeJS and Yarn, two very
+important packages.
+
+> *Note: you may have noticed that whenever we run the
+> `apt update` or `apt-get install` commands we get more packages, and
+> whenever we run `gem install` command we get more "gems" (ruby libraries)*
+
+And now we finally install Rails (this may take a few minutes too):
+
+```bash
+gem install rails -v 6.0.2.2
+rbenv rehash
+```
+
+Let's test it out by running `rails -v`, you should get:
+
+```bash
+rails -v
+Rails 6.0.2.2
+```
+
+If you get anything different, start debugging/Googling.
+
+### Installing and Configuring PostgreSQL
+
+You can install PostgreSQL in Windows or directly in the WSL. It is easier
+to install it in Windows, but I prefer separating my development environment
+from my personal user space, so I'll show how to install it in your WSL.
+
+As of April 3, 2020, installing PostgreSQL-11 isn't trivial. First, let's
+go to [Postgre's website](https://www.postgresql.org/download/linux/ubuntu/).
+Choose your Ubuntu apt repository (most likely Bionic 18.04) and run the
+following commands from your bash terminal:
+
+```bash
+sudo vim /etc/apt/sources.list.d/pgdg.list
+```
+
+Vim is the terminal's text editor. **Don't try typing things yet!** Vim
+doesn't start in "insert mode" which is the mode that lets you type stuff,
+instaed it starts in the mode that accepts commands. So first push the "i"
+key in your keyboard. This will take vim into "insert mode" like below:
+
+
+ *Vim in insert mode -> text editing enabled* + +Now that we can insert stuff, paste the following line into the +document (remember to right-click)L + +```vim +deb http://apt.postgresql.org/pub/repos/apt/ bionic-pgdg main +``` + +
+
+After pasting that line, we have to save and exit. To do this, first
+exit INSERT mode by pressing your ESC key. You'll notice that the
+-- INSERT -- message disappeared from the bottom left corter of
+vim's screen. Now, type `:w` and press enter. This will ask vim
+to **write** changes into the file. Then, type `:q` which will ask
+vim to exit (*Note: you can also do `:wq` to do both at the same time*).
+
+We just added the information required for bash to successfully get the
+latest version of PostgreSQL. So now we'll get it! Run the following
+command in bash:
+
+```bash
+wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -
+
+sudo apt-get update
+```
+
+We got the update info now, let's install:
+
+```bash
+sudo apt-get install postgresql-11
+
+sudo apt install libpq-dev
+```
+
+Now that PostgreSQL is installed, let's set up a user. Run the code below
+replacing `USERNAME` for your UNIX user for simplicity:
+
+```bash
+sudo -u postgres createuser USERNAME -s
+```
+
+And now we're done with PostgreSQL! All that's left is to test the server:
+
+### Testing Rails server
+
+To see whether things are working, lets boot up a server. Run the following
+lines of code in your terminal:
+
+```bash
+cd
+rails new helloworldapp
+cd helloworldapp
+rails server -b 0.0.0.0 -p 3000
+```
+
+
+ *Puma server booted successfully* + +Now, if you were able to boot up Puma successfully, you +should be able to open up Chrome or any other browser and +enter `http://localhost:3000` in the address bar. If you +did everything well, you should see the following page: + +
+
+Rejoice! The hard part is over. **Now, close your server by going back to the
+terminal and pressing CTRL+C**
+
+## Setting up VSCode for Local Development
+
+It's great that you have a server up and running, but you will most likely
+want to have real-time access to the code and assets in the server. The files
+that live in your Linux subsystem don't like comingling with your Windows
+files (they are completely separate Operating Systems after all). *This means
+that you can't really edit those files DIRECTLY from Windows*. If we left
+things as they are now, you would have to make some code, upload it to
+Github, and then download it using your Ubuntu terminal. This would be
+cumbersome to say the least.
+
+Fret not! Since your WSL lives inside Windows, you CAN edit the files using
+Windows, but *not directly*. This means that you will be able to code and
+instantly see the changes you made in the same computer.
+
+If this sounds a bit too technical, **just follow these steps so you can
+use VSCode inside your new Linux environment.**
+
+### Download and Install VSCode
+
+In case you don't already have VSCode, then [please download and install it
+now](https://code.visualstudio.com/download) (*download the Windows 64 bit
+version unless you know you have a different Operating System*). You may be
+thinking about downloading the Ubuntu version, but don't. WSL 2 is *kind of*
+Linux, but not full fledged, VSCode needs to run from a fully functional
+Operating System like the Windows 10 you're running now.
+
+> Make sure to leave the "Add to PATH" checkbox **TICKED**
+
+Some resources in case something goes wrong:
+
+[Official "Developing in WSL" guide](https://code.visualstudio.com/docs/remote/wsl)+[Remote development in WSL guided tutorial](https://code.visualstudio.com/remote-tutorials/wsl/getting-started)
+[Remote-WSL Extension site](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl)
+[Full guide from Microsoft](https://devblogs.microsoft.com/commandline/an-in-depth-tutorial-on-linux-development-on-windows-with-wsl-and-visual-studio-code/)
+ +### Install Remote Development Extensions + +After installing, open VSCode. It will most likely offer you to install a +"Remote-WSL" extension. Don't do it for now. Go to extensions on the left +(or hit CTRL+SHIFT+X) and paste this into the search bar: + +```none +Remote Development +``` + +You should see something like the picture below but with +the option to install available (I already have it installed +so it doesn't show up): + +
+
+Install this one. If you installed it successfully, you should see the little
+connection icon in the bottom-left corner of your VSCode:
+
+
+
+Click on that green icon. You'll notice a dropdown menu appeared near the
+top of your VSCode. Click on `Remote-WSL: New Window`. Now VSCode is asking
+for a folder to open. Browse to the *helloworld* app we created before to
+test whether Rails was creating a server successfully. It should be something
+like `/home/USERNAME/helloworld/`. Click OK. After a second, you should see
+a notification at the bottom-right corner of VSCode stating that "Code
+Server" is being installed in WSL:
+
+
+
+Once this is finished, VSCode will open up a new window and your status
+at the bottom-left corner will change to `WSL: 
+
+If you got all the way here, then congratulations! You can now successfully
+code from your Windows 10 machine using VSCode and see those changes
+reflected in real time in your server. Try it out by creating a hello-world
+view inside your helloworld app!
+
+### Test VSCode by Making Hello World View
+
+From your `helloworld` app folder, go to `config > routes.rb` and double
+click the file to open. Add the following line inside the `Rails.application.routes.draw do` block:
+
+```ruby
+ root 'application#hello'
+```
+
+
+
+Then go to `app > controllers > application_controller.rb` and open the file.
+Inside the `ApplicationController` class, add the following instance method:
+
+```ruby
+ def hello
+ render html: ("Hello worlddd 🔥!!!
").html_safe
+ end
+```
+
+
+
+
+
+Now let's boot up the server again, and let's do it well. At the menu on the
+top, click on `Terminal > New Terminal`, or better yet, press ``CTRL+SHIFT+` ``
+(*" \` " is the key next to "1" in your keyboard*).
+
+
+
+Once you open the terminal, **make sure that the commands are being run from the helloworld folder.** This can be double-checked by looking at the
+terminal line:
+
+
+
+If everything is going according to plan, then type the following in this
+new terminal:
+
+```bash
+rails server -b 0.0.0.0 -p 3000
+```
+
+If you have done everything well up to this point, visit 
+
+> **Don't forget to stop the server again, CTRL+C.**
+
+Congratulations, you are now up and running with VSCode + WSL2 + Ruby on Rails.
+Nothing is stopping you now.
+
+
+
+TODO
+
+* Windows terminal
+* Setting up VSCode via WSL 2 connection
+* Forwarding ports, making website discoverable in local
+network on startup (NIC bridge)
+* Allowing connection via hostname instead of IP
+* Advanced: Setting up VSCode via SSH, automating SSH Daemon
+on startup
+
+
+
+
+
\ No newline at end of file
diff --git a/img/fstupdate.png b/img/fstupdate.png
new file mode 100644
index 0000000..a5fa142
Binary files /dev/null and b/img/fstupdate.png differ
diff --git a/img/gorails1.png b/img/gorails1.png
new file mode 100644
index 0000000..4704fad
Binary files /dev/null and b/img/gorails1.png differ
diff --git a/img/helloworld-controller.png b/img/helloworld-controller.png
new file mode 100644
index 0000000..bcf7562
Binary files /dev/null and b/img/helloworld-controller.png differ
diff --git a/img/helloworld-routes.png b/img/helloworld-routes.png
new file mode 100644
index 0000000..5c29f4e
Binary files /dev/null and b/img/helloworld-routes.png differ
diff --git a/img/helloworld-success.png b/img/helloworld-success.png
new file mode 100644
index 0000000..d8d55b3
Binary files /dev/null and b/img/helloworld-success.png differ
diff --git a/img/insider1.png b/img/insider1.png
new file mode 100644
index 0000000..ae771c0
Binary files /dev/null and b/img/insider1.png differ
diff --git a/img/new-terminal.png b/img/new-terminal.png
new file mode 100644
index 0000000..2fc8b62
Binary files /dev/null and b/img/new-terminal.png differ
diff --git a/img/pumaboot.png b/img/pumaboot.png
new file mode 100644
index 0000000..d3ac884
Binary files /dev/null and b/img/pumaboot.png differ
diff --git a/img/remoteext.png b/img/remoteext.png
new file mode 100644
index 0000000..51ced19
Binary files /dev/null and b/img/remoteext.png differ
diff --git a/img/terminal-right.png b/img/terminal-right.png
new file mode 100644
index 0000000..0e7ac72
Binary files /dev/null and b/img/terminal-right.png differ
diff --git a/img/vimins.png b/img/vimins.png
new file mode 100644
index 0000000..a025f7c
Binary files /dev/null and b/img/vimins.png differ
diff --git a/img/vimpaste.png b/img/vimpaste.png
new file mode 100644
index 0000000..a7baf35
Binary files /dev/null and b/img/vimpaste.png differ
diff --git a/img/winfeatures.png b/img/winfeatures.png
new file mode 100644
index 0000000..4920f1b
Binary files /dev/null and b/img/winfeatures.png differ
diff --git a/img/winstore.png b/img/winstore.png
new file mode 100644
index 0000000..4037fa9
Binary files /dev/null and b/img/winstore.png differ
diff --git a/img/winver.png b/img/winver.png
new file mode 100644
index 0000000..dc15ee1
Binary files /dev/null and b/img/winver.png differ
diff --git a/img/wsl-available.png b/img/wsl-available.png
new file mode 100644
index 0000000..df10646
Binary files /dev/null and b/img/wsl-available.png differ
diff --git a/img/wsl-installing.png b/img/wsl-installing.png
new file mode 100644
index 0000000..4c98848
Binary files /dev/null and b/img/wsl-installing.png differ
diff --git a/img/wsl-successful.png b/img/wsl-successful.png
new file mode 100644
index 0000000..ed96922
Binary files /dev/null and b/img/wsl-successful.png differ
diff --git a/img/wsllist.png b/img/wsllist.png
new file mode 100644
index 0000000..2d6a91e
Binary files /dev/null and b/img/wsllist.png differ
diff --git a/img/yayrails.png b/img/yayrails.png
new file mode 100644
index 0000000..c337bce
Binary files /dev/null and b/img/yayrails.png differ
diff --git a/ports/config.ps1 b/ports/config.ps1
new file mode 100644
index 0000000..a74881a
--- /dev/null
+++ b/ports/config.ps1
@@ -0,0 +1,68 @@
+# Give process admin privileges:
+param([switch]$Elevated)
+
+function Test-Admin {
+ $currentUser = New-Object Security.Principal.WindowsPrincipal $([Security.Principal.WindowsIdentity]::GetCurrent())
+ $currentUser.IsInRole([Security.Principal.WindowsBuiltinRole]::Administrator)
+}
+
+if ((Test-Admin) -eq $false) {
+ if ($elevated)
+ {
+ # tried to elevate, did not work, aborting
+ }
+ else {
+ Start-Process powershell.exe -Verb RunAs -ArgumentList ('-noprofile -file "{0}" -elevated' -f ($myinvocation.MyCommand.Definition))
+ # If we want to keep the window open after running:
+ # Start-Process powershell.exe -Verb RunAs -ArgumentList ('-noprofile -noexit -file "{0}" -elevated' -f ($myinvocation.MyCommand.Definition))
+}
+
+exit
+}
+
+'Running with full privileges'
+
+# Get WSL virtual IP:
+$remoteport = bash.exe -c "ifconfig eth0 | grep 'inet '"
+$found = $remoteport -match '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}';
+
+if( $found ){
+ $remoteport = $matches[0];
+} else{
+ Write-Output "The Script Exited, the ip address of WSL 2 cannot be found";
+ exit;
+}
+
+#[Ports]
+
+#All the ports you want to forward separated by coma
+$ports=@(80,2223,3000);
+
+
+#[Static ip]
+#You can change the addr to your ip config to listen to a specific address
+$addr='0.0.0.0';
+$ports_a = $ports -join ",";
+
+#[Firewall]
+#More often than not, Windows firewall will block connections even from local network, so
+#we will open the ports above for PRIVATE connections only. It is STRONGLY advised against
+#opening ports in Public networks, specially for mobile devices that may automatically
+#connect to unsafe networks. If you're sure you want Public access to your server, then
+#change the rules below under the "-Profile" option (look up the right syntax online):
+
+#Remove existing Firewall Exception Rules, if any
+Invoke-Expression "Remove-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' ";
+
+#Adding Exception Rules for inbound and outbound Rules
+Invoke-Expression "New-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' -Profile Private -Direction Outbound -LocalPort $ports_a -Action Allow -Protocol TCP";
+Invoke-Expression "New-NetFireWallRule -DisplayName 'WSL 2 Firewall Unlock' -Profile Private -Direction Inbound -LocalPort $ports_a -Action Allow -Protocol TCP";
+
+#Bridge the connection such that your
+for( $i = 0; $i -lt $ports.length; $i++ ){
+ $port = $ports[$i];
+ Invoke-Expression "netsh interface portproxy delete v4tov4 listenport=$port listenaddress=$addr";
+ Invoke-Expression "netsh interface portproxy add v4tov4 listenport=$port listenaddress=$addr connectport=$port connectaddress=$remoteport";
+}
+
+exit
\ No newline at end of file