This is the tutorial site for the Zero to Cognitive Series. Each chapter in the Tutorial is a completely self contained folder.
We are currently at release 1.3, which includes updates to Chapter 8 (Watson Discover News), Chapter 9 (Visual Recognition) and Chapter 11 (Watson Discovery). Release notes are here: https://github.com/rddill-IBM/ZeroToCognitive/releases/tag/1.3
Please note that the videos for Chapters 8, 9 and 11 are currently incorrect. Please use the ReadME files in those chapters for explanations of the new code.
##The chapter structure is:
1). The Story, Architecture for this app
3). Building your first Watson App
7). SSL, https: sessions and users (set up security, use cloudant for sessionStore, manage user profiles)
10). Watson Conversations
12). How do I get started on my client app? Design Thinking, Stories, Architecture, Keeping it simple
If you are using IBM Public Bluemix for this tutorial series, IBM is introducing a significant change on January 2nd, moving from DEA (Droplet Execution Environment) to Diego. The tutorial will run without change in this new environment. There are two things you need to understand with this change:
A). VCAP_APP_HOST and VCAP_APP_PORT are no longer available (the apps in the tutorial don't use them, but you might)
B). The upload process changes. You must update your CLI (command line interface) to support Diego. The changes to your CLI are documented here: https://github.com/cloudfoundry-incubator/Diego-Enabler , which tells you to execute the following two commands from your command (terminal) prompt:
cf add-plugin-repo CF-Community https://plugins.cloudfoundry.org/ cf install-plugin Diego-Enabler -r CF-Community
Once you have done that, you will find that there is a new exec in each of the folders:
cf-diego. This exec reads your manifest.yml file for the name of your application and then issues the appropriate cloud foundry (cf) commands and also enables Diego. I've written this exec because now, instead of issuing a single cf push command, you have to issue three commands. This exec issues all three for your automatically.
If you want to resynchronize your fork with this master repository to get all of the latest updates. (First) push (
git push) your latest work to your personal repository, (then) execute the following commands:
git checkout master git pull email@example.com:ZeroToCognitive.git git push origin master
git checkout master command ensures that your local copy of your personal repository is pointing to the master branch of your local repository. This is the default branch.
git pull firstname.lastname@example.org:ZeroToCognitive.git command goes to this repository and brings down all changed files and adds them to your local repository.
git push origin master command updates your personal repository on enterprise github with the latest updates you've pulled down from the master repository.