just to be a bit more clear;
in your myapp directory is a .git/config file
open it
edit
[remote "origin"]
url = [email protected]:myapp.git
fetch = +refs/heads/*:refs/remotes/origin/*
just edit the url line to include herokugarden like so
[remote "origin"]
url = [email protected]:myapp.git
fetch = +refs/heads/*:refs/remotes/origin/*
while in your myapp directory
git push
Everything up-to-date
done
On Jan 19, 8:24 am, Chris Schumann <[email protected]> wrote:
> This was close, but the syntax is incorrect. In any case,gitalready
> has an "origin" repository, so I changed that one to herokugarden.com,
> and that has finally allowed me to continue to work.
>
> Thanks for the lead, Waldo, and the huge hint, did!
>
> Just for history's sake, and in case anyone else is still having this
> problem:
>
> I tried this:gitremote add herokugarden [email protected]:appname.git
>
> That was added to the .git/config file, but "origin" was unchanged,
> and that seems to be the remote repository used for pushing. (Nogit
> expert here!)
>
> I then edited the .git/config file and changed the "origin" to point
> to herokugarden, as suggested by did, and that got me running.
>
> Chris
>
> On Jan 19, 7:49 am, waldo <[email protected]> wrote:
>
> > This should probably be used with caution... but I also had to tell
> >gitto change it's info about its remote repository (I presume this is
> > what the herokugardengit:transition is intended to do - although that
> > didn't run for me either).
>
> >gitremote add [email protected]:my_app_name.git
>
> > This seemed to replace the dead link to the remote repository on
> > heroku with the valid herokugarden repository.
>
> > Waldo
>
> > On Jan 18, 12:01 am, did <[email protected]> wrote:
>
> > > Hey guys,
>
> > > I think I've got a similar issue with my heroku account. I switched to
> > > herokugarden by installing the new gem. Then, I added my keys
> > > successfully.
>
> > > > herokugarden list ===> no pb
>
> > > But, when I run:
>
> > > > herokugardengit:transition => Authentication failure
>
> > > I precise that my modifications were committed to my localgitbut not
> > > pushed. Obviously, if I try topushthem, it fails since the old
> > > herokugitrepository is not available anymore. What does exactly
> > > "herokugardengit:transition" ?
>
> > > For now, the only solution to my problem is to make agitclone from
> > > my new herokugarden repository (it worked) and then try to merge my
> > > modifications from my local heroku repository to the new one
> > > (herokugarden). I've to digg into thegitdocumentation to see if
> > > that's possible (I'm not agitguru). Unless someone has a better
> > > idea.
>
> > > Thanks.
>
> > > Did
>
> > > On Jan 17, 3:00 pm, Chris Schumann <[email protected]> wrote:
>
> > > > I am not. It may be an issue with keys, and I'm not sure how to
> > > > correct it, since I "herokugarden list" works, but "gitpush" does
> > > > not. I do have one key in my keylist according to "herokugarden keys".
>
> > > > Also, mortgageqb is still giving 502 errors, but venuematic is running
> > > > (or at least the first page is!).
>
> > > > Thanks for your work,
> > > > Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---