github
I'm open to talking about anything we've done so far.
Seems like several folks are having trouble with github,
so let's try looking at that.
I'll walk through the steps on windows.
The tools I've installed :
anaconda 1.8.0 (python and ipython)
notepad++
Git-1.8.5.2 from git-scm.com (includes "Git Bash" shell)
I'm following the recipes at
This gives you "Git Bash", a command line, which has a bunch of the unixy command line I've been using, including a command line "git".
pwd print working directory
ls list files in current directory
cd change directory
mv move (or rename) file
scp copy file (or cp, but jim likes scp)
rm -i remove
man read the man pages
mkdir make a new directory
ssh connect to a remote host
less show a file on the terminal
python (if installed by e.g. anaconda)
ssh-keygen make public/private keys
git manage local and remote code repositories
vim a popular terminal editor
nano an easy terminal editor
~ home directory
.. parent directory
Then the configuration steps are essentially
- create a git account
- use the "git config" command in the "Git Bash" shell to set up your identity.
- use the "ssh-keygen ..." command in "Git Bash" to create keys in ~/.ssh/
- copy your public key to your github account
Using git takes place in that same Git Bash shell.
- clone a github repo (create one there first if you want a new project)
- edit or create new files
- see what git things is going on : $ git status
- add those files : $ git add file
- commit changes : $ git commit -m "your message here"
- push your changes to github : $ git push
On windows, I'd suggest Notepad++ as the place to do the editing.
Questions?
Do a demo of using ssh from within Git Bash
to connect to csmarlboro.org
# Launch "Git Bash" on Windows, or Terminal on a Mac.
# Then type this :
$ ssh username@csmarlboro.org
passwd: <type yours in>
... and you're there
# OR copy a local file to the other computer
$ scp local_file user@csmarlboro.org:
Editing a file remotely:
$ nano filename
$ vim filename # another choice (google for tutorials)
$ emacs -nw filename # (google for tutorials)
So let's discuss the tron stuff some more and play around with it.
I've added all of you to the tron-engine repository in MarlboroCollegeComputerScience;
you can clone it, fork it, or push to it ... but be aware that it's public,
so if you put robots there, other folks in the class can see (and mess with) 'em.
For next Tuesday, make a bot, and get it to me either by
- uploading it to csmarlboro and telling me where it is
- putting it in the github repo, or
- submitting it on the assignments page
The advantage to having it on csmarlboro is that I'm going
to run it there, so you'll can test it with the system
I'll use for the tourney.