NB: These are partially based on the setup instructions found here: https://github.com/luke-hill/setup_info/blob/main/mac_setup.md
# Install brew from http://brew.sh/
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
$ brew doctor
$ softwareupdate --all --install --force
$ sudo xcode-select --install
$ brew update
$ brew upgrade
$ brew install git
$ git --version # This should output a number
# If running on Big Sur - Uncomment the next lines and run them
# $ export warnflags=-Wno-error=implicit-function-declaration
# $ softwareupdate --install-rosetta
$ curl -L https://get.rvm.io | bash -s stable --auto-dotfiles --autolibs=enable --rails
$ rvm update
$ rvm reload
# Quit the terminal once this has installed, and restart your machine
$ type rvm | head -1
$ rvm -v # This should output a number
$ rvm install 2.7.8
$ rvm install 3.1.6
$ rvm install 3.3.6
$ rvm install 3.4.1NB: These are partially based on the setup instructions found here: https://github.com/luke-hill/setup_info/blob/main/ubuntu_2404_setup.md
$ sudo apt-get install git
$ sudo apt-get install gnome-tweak-tool libappindicator1 software-properties-common curl perl gcc --fix-missing -y
$ sudo apt-get install libcurl3-gnutls libcurl4-openssl-dev libcurl4 libgmp3-dev libpq-dev libmagic-dev libssl1.0-dev --fix-missing -y
$ sudo apt-add-repository -y ppa:rael-gc/rvm
$ sudo apt-get update
$ sudo apt-get install rvm
$ source /etc/profile.d/rvm.sh
$ rvm fix-permissions system
$ rvm group add rvm $USER
$ rvm autolibs disable
$ rvm update
$ rvm reload
# In terminal, click Edit > Profile Preferences, click on Title and Command tab and check Run command as login shell.
# Restart your terminal completely, and restart your machine
$ rvm -v # This should output a number
$ rvm install 2.7.8
$ rvm install 3.1.6
$ rvm install 3.3.6
$ rvm install 3.4.1Fork this repository to your own workspace, and then clone it
# Fork it
$ git clone [email protected]:<your-gh-username>/ruby-training.gitChange directories so that you're in the project:
$ cd ruby-trainingThe classes are split into a variety of technical challenges. Each folder consists of various exercises, which are split according to week and complexity. A rough indicative "split" of the Strands (or 'areas'), of work is as follows ...
- Strand 1: Repo Introduction, Machine Setup,
the-language(Easy)- By the end of this strand you should be able to know how to "do" the Koan work
- You should be comfortable using the ruby interpreter, knowing how to enter / exit
irb - You are able to explain the difference between a ruby package manager, a version of ruby and
bundler
- Strand 2:
the-language(Medium),the-language(Hard)- You will be comfortable solving all types of Koans (Including potentially undescribed ones)
- Stack Traces, error messages and rspec outputs are now common parlance
- Most simple and complex ruby structures have now been introduced to you
- Strand 3:
shapes,bottles- You have begun to write some simple code
- You understand how basic TDD works
- You can switch between writing tests (From your Koan work), and writing code (From your Project work)
- Strand 4:
dice_games(Both),validators- You are beginning to understand basic programming paradigms
- Working in the correct ways with things like
git, including commits and PR's is now getting easier - You are able to start understanding how you need to solve simple software problems
- Strand 5:
lcd(Start, Single Digits & Composition)- You are introduced to the first complex task that needs whiteboarding
- Strand 6:
lcd(Completion / Stretch goals)- Introduction to the concept of refactoring
- You are starting to understand that Modularity in code and being able to extend is important
- Strand 7:
fake_rspec,decorators- Revisiting of good software principles (DRY / SOLID e.t.c.)
- Generic Programming concept where you can massively DRY up code by "Decorating" the inner item
- Strand 8:
metaprogramming,proxy- Introduction to DSL style method invocation, procedural programming
- Message Controlling (Sending messages from one location to another)
- Strand 9:
site_prism- The framework you can use to do web based automation - leans heavily on DSL / metaprogramming concepts
Each exercise will be in a subfolder of this directory, and should contain a README with more information.
It will be the aim that a mixture of theory and discussion will take place for each exercise, and then self-study / exercise completion.
It is advised that each pupil will start with a clean copy of this repo on their machine, and by the end will have as close as possible; to a full completed copy.
When you want to save your work, stage and commit changes:
$ git add . # the dot is important
$ git commit -m "Explain your change - try be descriptive"(Ensure you are working on a branch to start with and not main).
When we start working on a new exercise - or are moving forwards with a specific problem, save your work as described above, and then make a Pull Request to your own fork.
Doing this will give you a backup of all of your work, and also allow you to track your changes over time to see how you are progressing.
# On your current branch
$ git push -u origin <name_of_branch>
$ git checkout main
# Make the requisite PR on github and merge
$ git pull -p # the -p is optional but just helps tidy up the branch
# Then create a new branch straight away to continue working, with the latest changes you made
$ git checkout -b <new_branch_name>If you have gone down a blind alley, and you just want to start over, git makes it easy to clean up and start again.
First of all make sure git knows about all of your files
$ git add .Then throw away all of the changes
$ git reset --hard HEADYou will find you are back at a clean directory, from when you last committed.
Make a branch to keep all your changes:
git branch my-working-branchMake sure you've got the latest version from GitHub
git fetch originThen tell git to create a new copy of main, throwing away the old one
$ git reset --hard origin/main