This page outlines how the lessons are structured and intended to work overall.
Starting code
The source code for the training application is stored in two Git repositories as outlined in the Application setup and overview page, which is a prerequisite to any lesson and hopefully something you’ve already been through. (Hint: if you haven’t, perhaps now is a good time to do so :)).
Once checked out the source code in your registry-quick-start folder can pretty much be ignored. It can remain on the master branch and won’t need updating (unless you come back to the training after a long period you might want to pull down the latest – which may or may not coincide/require an update to your Stratus Server version).
The files within super-heroes folder are a different matter however. The Git branch these files point to should change for each lesson. Each lesson has a "Starting code" section at the top which states a Git tag – that is the super heroes configuration starting point for that lesson. In other words, it contains the configuration required for any previous lessons and ensures the running super heroes application is in a known state.
Now, as you no doubt know, tags in Git are immovable and you get a warning if you check them out to make changes. So the process per lesson is as follows:
- Check out the tag listed at the top of the lesson e.g. the tag “lesson/01” for Lesson 1
- Create a new branch off that tag using the convention [your username]/lesson/01 e.g. “smithw/lesson/01”
- Switch to this new branch
This will give you a personalised, editable branch based off the start tag for the lesson, allowing you to make changes as you go through the lesson. You don’t need to push your changes (unless you really want to) as you’ll repeat the process for each lesson using its start tag, discarding your changes for the official lesson configuration.
