This is the P2PU Archive. If you want the current site, go to www.p2pu.org!
Introduction to Ruby and Rails
My recent threads
You haven't posted any discussions yet.
Recently updated threads
- Introductions Thu, 2011-02-03 13:39
- Intro to Git Thu, 2011-01-20 06:34
- Fonts. Thu, 2011-01-20 06:33
- Regarding JRuby Wed, 2011-01-19 16:28
- Changes to Sign Up Task Wed, 2011-01-19 02:17
Changes to Sign Up Task
All--
Thank you so much for your interest in the "Introduction to Ruby and
Rails" course.
First, please forgive me: this is my first time facilitating a P2PU
course. The interest has been overwhelming, and I therefore feel the
need to make some tweaks to make sure those who apply are truly
motivated.
Important part: While I know this will create a bit of a mess, I am
going to require a "second sign up task" to try to make sure those who
are accepted will be able to handle the workload and stay motivated.
This "second sign up task" includes the first, but adds some
additional tasks to bring it closer to what a week of coursework will
look like after the course starts.
Simply revisit the sign up task page at http://alindeman.github.com/p2pu-rubyrails/signup-task.html
(do a shift+refresh to make sure you have the latest copy) and
complete the new tasks.
If you have already submitted a sign up task, skip to "Setting up Git"
I will accept submissions via email as described in the guide. Those
who are approved will be notified and readded to the Google Group on
19 January or after.
Andy - do you want to know that we installed GIT as well (I have and I just sent you an email without that information)?
I will know you installed git if you successfully fork and push back the coursework repo :)
Ping me if you run into any trouble.
I didn't pull the latest instructions. My fault. I'll do it tomorrow.
Andy,
Does this mean that if we have already been approved for the course, we need to do this to be re-approved or else we may be dropped? I'm fine with that (I'm guessing you have a lot of folks applying), but when will you need these new tasks completed by? I may not be able to get to it until the weekend.
Thanks,
Dan
The deadline is 19 January. Waiting until the weekend is fine :)
Everything seemed to be going well with the second part of the sign-up task, but when I got to the section of "Modifying the Signup Script", and attempted to clone the repository I keep receiving this error: fatal: could not create work tree dir 'coursework'.: Permission denied.
Does anybody have any insight? Thanks.
@Anthony Zazo i guess u need to change the file permissions of vagrant/shared folder. Provide write capabilities to your account. If you tell me the operating system i may try to help. thanks
It's Vista 32 bit, thanks.
@Anthony,
Did you add your ssh key into into your github account? If not, go here: http://help.github.com/msysgit-key-setup/
and follow the instructions. You should then be able to copy your forked repository.
Thanks for the link, Adam! Feel free to use SSH keys instead of HTTPS; I only showed HTTPS in the sign up task for a bit of simplification. In reality, SSH is probably the best option.
Thanks, I will give it a shot it tonight.
I was continuing to have problems with cloning, so I uninstalled vagrant, putty and the virtual box, reinstalled and everything worked.
Hi Everybody,
I cloned the reposity, changed the script and it works fine. Now i tried to push it back and i get this error:
The requested URL returned error: 401 while accessing https://whiteywhite@github.com/whiteywhite/coursework.git/info/refs
Does anybody know what that means and how i could solve this?
Cheers
401 usually means an authentication or authorization error. Were you prompted for your GitHub password? Are you sure you entered it correctly?
Ok pretty embarrassing, i used the wrong password. But for my defense, when i cloned the repository it asked me for a password and i used the wrong one aswell, but it worked. Is that a bug of git?
It may be that GitHub doesn't require successful authentication until you actually push something up. In the first week of the course, I'll link folks to some tutorials on how to use SSH with Git and GitHub. SSH is a more convenient and common method, but requires some initial setup I didn't want to clutter the setup task with.
Hi Hi,
Andy, I don't know if you are aware of this but the link "My git workflow" within the extended signup task page links to github reference on "Generating SSH keys" whereas I guess you meant it to point to a blog post?
--Jaime
You're absolutely correct, my apologies. I've updated the link (may need to hard refresh again to get it).
That's probably the source of the confusion regarding keys. I just followed Andy's instructions for completing the git fork etc task and didn't do anything with respect to SSH keys other than previously having set up Putty to use one.
Yah, at first I was writing up instructions for SSH keys, but it became too complicated. Even though it's a little less convenient to use a password, HTTPS is easier to get going quickly.
I'll make sure folks know about the ability to use SSH during the first week of the course.
I will do the new tasks tonight and send them to you. Thanks for the information!
To note, if you already have git set up on your default machine, it may be easier to git clone into the shared folder. You can test and run in virtualbox, and code and push in the non-virtual machine.
Great point! The sign up task is definitely only one possible way out of many.
Hi people,
I'm having some problems with the"git clone" part.
When I try to clone the repository, I get this error:
--------------------------------
git clone https://bernatf@github.com/bernatf/coursework.git
Initialized empty Git repository in /shared/coursework.git/
Password:
Error: Couldn't resolve host 'github.com' while accessing https://bernatf@github.com/bernatf/coursework.git/info/refs
fatal: HTTP request failed
--------------------
Does anybody know what can be the cause of this?
Thank you very much people!
Were you able to fix it? I see that you pushed a commit to your repo - what was the issue?
Also, I know it isn't a fix for the HTTPS problem, but you should consider setting up SSH with GitHub instead. http://help.github.com/linux-key-setup/
Thanks but still not working.
I've followed the ssh setup instructions and vagrant can't connect to download "xclip" either.
I've also tried to do an "apt-get update" and also it can't establish connection to the server...
Any clue on what can be the problem?
If you could provide a bit of info that may help:
What's your host OS?
When you run "vagrant up", what is the output? Check if it says this:
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- ssh: 22 => 2222 (adapter 1)
[default] -- webrick: 3000 => 3033 (adapter 1)
[default] -- web: 80 => 8088 (adapter 1)
[default] -- mysql: 3306 => 3366 (adapter 1)
[default] -- postgres: 5432 => 5434 (adapter 1)
[default] -- sinatra: 4567 => 4568 (adapter 1)
What do you get when you run the command "mtr google.com" in Virtualbox itself?
VirtualBox shares the host internet with the virtual machine, and it seems like there's an issue with that. Depending on how your network is set up, you might have port restrictions or MAC/IP limitations, and you'll need to switch networking modes (Bridged vs. NAT).
Fixing this also looks like it will clear up your other problem, with the HTTP resolution failure. I think the main issue is connecting to the internet at all.
Wow! After troubleshooting a lot, it finally worked with just destroying the vagrant session and opening another...
Thanks Henry for your help!
PD: When I prompt the command "vagrant halt" it also halts my OS (OS X 10.6). Is there any other command?
You have three choices listed here: http://vagrantup.com/docs/getting-started/teardown.html
suspend, halt or destroy.
Dan
I am currently using the third (destroy) but I was asking because at the end of the tutorial it says to use halt and not destroy. The question is: WHY?
I'll let Andy speak for himself (he originally said to use destroy), but I don't think it matters much. The differences are described on that web page, and I'd think one would make the choice that's most suitable to their situation, resources limitations and needs. I've used "suspend" because it starts up faster, but I'm eating up more disk space doing so on my old laptop, so I may use "destroy" more often than not. Six of one, half-dozen of the other. I'd suggest you use the one that works for you.
I think "halt" is usually the best option, as it tears down the VM and its resources but saves changes.
"destroy" will delete any changes you made to the VM itself (except the /shared directory). This will eventually be an annoyance because it will (for instance) "uninstall" git and any other OS updates you make.
"destroy" will be convenient if you ever accidentally screw up the environment beyond easy repair. This is one reason I wanted everyone to install the VM, even if they already had access to a Linux-based machine.
In that case, I'll be staying away from "destroy"! :^)
Dan
hii
just want to ask do i have to send the same information in the email and in the signup task form ... or just the email ???
Just email, as that allows me to organize better. Feel free to put whatever you want in the sign up task form: I won't really look at it.
Andy - hope you don't mind me asking but do we have to send you a pull request on git?
The reason I ask is because I believe I've done everything to get in but haven't been added on the course. Please let me know there's anything else I should do. Thanks!
Apply using the "Apply" button on the course page; I won't start doing acceptances until 19 January-ish.
Thanks :)
Thank chunky bacon for that!
Thanks Andy :)
Hi Andy,
looking at the network graph on github I save the time to register also, but wanted to thank you for the crazy idea to let 200 people fork the repo at the same time.
..Carsten
Carsten: Do you plan to apply? I don't seem to have an email from you.
Sign-up task submitted yesterday, looking forward to hearing from you Andy :)