##Create a Repository
First you will need to create an account on BitBucket.
Once you have the account, create a new repository by clicking the Create button:
Name your repository Prog270_LastName where LastName is your last name:
Fill in the other values as follows:
##CodeAnywhere and DevBoxes
Open up CodeAnywhere and sign in. (You may have to create an account first, if you have not done so already.) We now want to set up a DevBox. In the free tier you are allowed to have only one DevBox, but we can put multiple repositories in side it and we can put multiple folders in each repository.
To set up DevBox follow these steps:
##Add CodeAnyWhere SSH Key to BitBucket
SSH keys are a means of identifying you when you make secure connections across the internet. Typically, you have one private key that only you see. You then give the public key to locations across the web that you want to access. To use the key the following conditions must be met:
For this to work, the private key must remain private. Never give or show your private key to anyone. The public key can be shown, at least in theory, to anyone. But in general, we only give it to people we trust.
In this case we are using the CodeAnywhere private key. This key is maintained by CodeAnywhere and we never see it. We give the CodeAnywhere public key to BitBucket. Now CodeAnywhere can communicate with BitBucket and vice versa.
To make this work, you must first get the CodeAnywhere public key.
Here is how to select and copy the key:
NOTE: Though there is little danger in sharing a public key, still the key shown here is fake, and does not contain valid values.
Now we need to put the key in BitBucket
In BitBucket, go to your your picture, then choose Manage account | SSH Key
Now go to the SSH Key hyperlink in the manage page:
Select Add Key, then paste in your SSH key, not the fake one shown below:
##CodeAnywhere and BitBucket
First do this on CodeAnywhere in your DevBox in the workspace folder:
mkdir Prog270_LastName cd Prog270_LastName git init git remote add origin email@example.com:
You can find your bitbucket URL on BitBucket. It is on the upper right corner of the overview page, as shown near the bottom of this document.
Then do this, Full name is your full name:
echo "#Full name" >> README.md git add README.md git commit -m 'Initial commit' git push -u origin master
Please note that similar text is available on BitBucket, under the text that reads something lie "Starting for scratch." If you find that text, you will see exactly what to to type in the line begin "git remote add origin...".
Below you can see a screenshot that shows what you need to do to complete the core of this assignment. This is only an example, as you will need to make a few minor changes. The main difference between my example and your code will be name of the repository. Your's should have the name of your account and your repo, not a name like ccalvert or DeleteMeSoon. For instance, I entered:
git remote add origin firstname.lastname@example.org:ccalvert/deletemesoon.git
You code will might look more like this:
git remote add origin email@example.com:lastname/prog270_lastname.git
I can't say precisely how it will differ, but the exact line is printed on the BitBucket site, if you can find it!
In this screen shot the line for adding the remote repository origin is cut off at the end. You can, however, see the whole URL further down.
When you try to commit your code, you may see text that is a bit hard to understand, but please try to understand it:
You can suppress this message by setting them explicitly: git config --global user.name "Your Name" git config --global user.email firstname.lastname@example.org If the identity used for this commit is wrong, you can fix it with: git commit --amend --author='Your Name
This means you should type in the first two lines, as suggested:
git config --global user.name "Charlie Calvert on CodeAnywhere" git config --global user.email email@example.com
Git saves this information, and uses it when you commit posts, and at other times. No one will not end up spamming you or giving your email away. It's just saved to a text file and used when git talks to BitBucket. Please fill these values in as suggested in the prompts. There is a similar prompt that you might get when you try to push. I don't remember the details, but just choose the option that is called simple.
If you don't fill in the these values, two things may happen:
You don't see these prompts in my screen shot because I have already filled in this information.
When you are done, you should be able to go BitBucket, refresh the page, and view your repository. It contains one file, called README.md, and the contents of the file is your full name.
When you are done share it with ccalvert by following a few simple steps. Open up BitBucket and, if necessary, use the Repositories menu to switch to your repository.
As shown in the screenshot below, along the left are a series of icons. Select the one that looks like a graph.It is labeled Overview
On the right you can see a button called Send Invitation. Select it. Type in my first initial and last name: ccalvert.
##Turn it in
When you turn in your work, all I should need is the URL of your repository and screenshot of your repository in CodeAnywhere. Attach the screenshot, and then put the URL in the comment. The URL should look something like this, only with your data, not mine:
To learn more about Git go here. The Elvenware Git page is not an assignment, it is just a reference. It focuses more on GitHub than on BitBucket, but the two services are very similar.