For our students on Windows, we have a separate setup for you using AWS's Cloud9. Instead of enabling virtualization, messing with Bios, and going through Docker, our IDE will be fully browser based with AWS's Cloud9. We estimate that your usage of AWS for Code Platoon will amount to around $20/month- you are responsible for the cost. Let's get started.
-
Sign in or sign up for an AWS Account.
-
After successfully creating your account or signing in you want to Sign in to the AWS Console. This is your dashboard to access any of the AWS Services.
- From here you can either use the search bar in the navigation or you can use the All Services listing to look for:
Cloud9
. In the search bar you can simply type:Cloud9
or you can use the All Listings dropdown looking for a Development Tools category whichCloud9
will be nested within.
Method 1: Use the Search by to find the Service in question.
Method 2: Use the All Services listing
- You'll see a page with a button that says Create environment. Click the Create environment button.
- Fill out the two fields with the following:
-
For the Name field:
codeplatoon-<cohort-name>
where<cohort-name>
is the name of your cohort -
For the Description field:
Development environment for the Code Platoon curriculum
- For Environment settings, leave them as is - they should look like the settings in the image below.
- Click the Next Step at the bottom, leaving all the defaults in place. Ensure Cost-saving Settings is set to the (default) of 30 minutes. Amazon is trying to help you protect your Cloud environment and put it to a sleeping state in case you forget to close or stop it from running. You wont be charged any money while your environment is not in use.
- Review this page, ensure your settings look correct and match besides the Name and Description that should match with what you entered. If everything looks correct, click the Create Environment button at the bottom.
- Our environment is now being setup and configured. This may take a few minutes to complete.
- Once ready, our Cloud Environment and IDE will look like this.
We've created a base cloud IDE environment to work from and need to install the necessary software for our class. In this section, we're going to execute a shell script. Inside your running Cloud9 IDE Window:
- Create a file named
installfest.sh
using the sidebar or console.- Sidebar: You can "right click" -> Create New File
- Alternatively, a console command:
touch installfest.sh
- Make this file executable using this command:
chmod +x installfest.sh
- In your sidebar click and open
installfest.sh
, you should see an empty file open in the editor view. - Go to Code Platoon's Cloud9-Setup Installfest Script. Find and Click the Raw button.
- Highlight and COPY ALL the contents on this page.
- Open your Cloud9 IDE window where we should still have our
installfest.sh
file open in Editor view. PASTE ALL the contents you copied into thisinstallfest.sh
file and ensure you SAVE before continuing. - Run the command:
./installfest.sh
(this will take a few minutes) - When the script finishes you should see
Installfest script finished running!
output to the screen as the very last line. If you do not see this message, reach out to a TA or Instructor. - Finally lets run:
source ~/.bash_profile
which should make our current console aware of all these new updates without having to close the console. You should see the console colors subtly change. You shouldn't need to run this again unless you later decide to edit your own~/.bash_profile
.
Let's configure Git so that we can clone/push (download/upload) the code for Code Platoon.
- Create a Create A Personal Access Token within your GitHub account.
- When you get to Scopes (permissions for this token), just enable the permissions listed within: repo. Scoping your token's permission to only what it needs is a GOOD security practice.
- SAVE THIS TOKEN on your machine or preferrably, a password manager. Your access token acts as your password when you get prompted in the console by the
git
client in a few steps
- In your Cloud9 IDE Console, run...
git config --global credential.helper cache
-- this will enable caching of your credentials within thegit
client so that you don't have to keep entering your username/password repeatedly.git config --global user.name "Your Name"
git config --global user.email "<username>@users.noreply.github.com"
-- Replace<username>
with your GitHub username.