librelist archives

« back to archive

Git pull?

Git pull?

From:
James Abbott
Date:
2011-03-13 @ 15:32
I'm trying to update my Nesta installation to the latest version of the gem.
It's already installed as a gem, so I just want that to be up-to-date.
Trying "git pull" from the app directory resulted in:

fatal: Where do you want to fetch from today?
>

I guess that would be https://github.com/gma/nesta.git, so should I use "git
pull https://github.com/gma/nesta.git"? Don't want to overwrite something or
botch something up, so your help is appreciated.

Cheers,
James

Re: [nesta] Git pull?

From:
steven shingler
Date:
2011-03-13 @ 15:36
If you're using nesta as a gem already, then doing "gem update nesta" would
be the way to update nesta.

On Sun, Mar 13, 2011 at 3:32 PM, James Abbott <abbottjam@gmail.com> wrote:

> I'm trying to update my Nesta installation to the latest version of the
> gem. It's already installed as a gem, so I just want that to be up-to-date.
> Trying "git pull" from the app directory resulted in:
>
> fatal: Where do you want to fetch from today?
>>
>
> I guess that would be https://github.com/gma/nesta.git, so should I use
> "git pull https://github.com/gma/nesta.git"? Don't want to overwrite
> something or botch something up, so your help is appreciated.
>
> Cheers,
> James
>
>

Re: [nesta] Git pull?

From:
James Abbott
Date:
2011-03-13 @ 15:55
Thanks - that seemed to work nicely, however there are files and directories
that don't show after running that. I created a separate installation just
days ago and in there are things like "tail" (a file), and "content-demo" (a
directory) - these were not fetched by "gem update".

This is probably nitpicking, but it would be nice to know how to make the
installation reflect the latest version.



On Sun, Mar 13, 2011 at 4:36 PM, steven shingler <shingler@gmail.com> wrote:

> If you're using nesta as a gem already, then doing "gem update nesta" would
> be the way to update nesta.
>
>
> On Sun, Mar 13, 2011 at 3:32 PM, James Abbott <abbottjam@gmail.com> wrote:
>
>> I'm trying to update my Nesta installation to the latest version of the
>> gem. It's already installed as a gem, so I just want that to be up-to-date.
>> Trying "git pull" from the app directory resulted in:
>>
>> fatal: Where do you want to fetch from today?
>>>
>>
>> I guess that would be https://github.com/gma/nesta.git, so should I use
>> "git pull https://github.com/gma/nesta.git"? Don't want to overwrite
>> something or botch something up, so your help is appreciated.
>>
>> Cheers,
>> James
>>
>>
>

Re: [nesta] Git pull?

From:
Graham Ashton
Date:
2011-03-14 @ 10:28
On 13 Mar 2011, at 15:55, James Abbott wrote:

> I'm trying to update my Nesta installation to the latest version of the 
gem. It's already installed as a gem, so I just want that to be 
up-to-date. Trying "git pull" from the app directory resulted in:
> 
> fatal: Where do you want to fetch from today?

As Steven said, the only way to upgrade Nesta itself is to update the gem.

What are you trying to upgrade from and to (i.e. what are the version numbers)?

> there are files and directories that don't show after running [gem 
upgrade]. I created a separate installation just days ago and in there are
things like "tail" (a file), and "content-demo" (a directory) - these were
not fetched by "gem update".

I suspect I've misunderstood you here, but just to be clear; when you 
upgrade a gem it doesn't have any effect on any files in your current 
directory. It just updates the gem itself which lives elsewhere entirely 
(usually somewhere in your Ruby installation; the path is revealed by `gem
environment gemdir`).

I suspect you've made the tail file yourself by accident (that kind of 
thing happens to me on occasion). The content-demo folder is created if 
you run the `nesta demo:content` command. It's just a clone of the 
gma/nesta-demo-content repo on GitHub.

> This is probably nitpicking, but it would be nice to know how to make 
the installation reflect the latest version.

The last two blog posts are about upgrading. Each release will get a new 
blog post that will tell you how to upgrade existing sites (if there's 
actually anything to do; usually there won't be).

You can't upgrade to the *very* latest copy of the code in the git repo 
(actually you can, but it requires some git/bundler fu that I won't be 
documenting; it's extra complexity with no real benefit). If there are any
commits in the Git repo that people need urgently I'll release a new 
version of the gem.

Re: [nesta] Git pull?

From:
James Abbott
Date:
2011-03-15 @ 11:20
Hi Graham and thanks for the clarification.

What are you trying to upgrade from and to (i.e. what are the version
> numbers)?
>

Just upgraded 0.9.3 to 0.9.4.

As regards the update gem command, yes, I knew it was updating the gem and
not the app directory. Of course I had created the "content-demo" directory
myself, with the nesta demo:content command. As regards the mysterious
"tail" file, well, there are more things between heaven and earth...


> The last two blog posts are about upgrading. Each release will get a new
> blog post that will tell you how to upgrade existing sites (if there's
> actually anything to do; usually there won't be).
>

All right!

Cheers,
James

On Mon, Mar 14, 2011 at 11:28 AM, Graham Ashton <graham@effectif.com> wrote:

> On 13 Mar 2011, at 15:55, James Abbott wrote:
>
> > I'm trying to update my Nesta installation to the latest version of the
> gem. It's already installed as a gem, so I just want that to be up-to-date.
> Trying "git pull" from the app directory resulted in:
> >
> > fatal: Where do you want to fetch from today?
>
> As Steven said, the only way to upgrade Nesta itself is to update the gem.
>
> What are you trying to upgrade from and to (i.e. what are the version
> numbers)?
>
> > there are files and directories that don't show after running [gem
> upgrade]. I created a separate installation just days ago and in there are
> things like "tail" (a file), and "content-demo" (a directory) - these were
> not fetched by "gem update".
>
> I suspect I've misunderstood you here, but just to be clear; when you
> upgrade a gem it doesn't have any effect on any files in your current
> directory. It just updates the gem itself which lives elsewhere entirely
> (usually somewhere in your Ruby installation; the path is revealed by `gem
> environment gemdir`).
>
> I suspect you've made the tail file yourself by accident (that kind of
> thing happens to me on occasion). The content-demo folder is created if you
> run the `nesta demo:content` command. It's just a clone of the
> gma/nesta-demo-content repo on GitHub.
>
> > This is probably nitpicking, but it would be nice to know how to make the
> installation reflect the latest version.
>
> The last two blog posts are about upgrading. Each release will get a new
> blog post that will tell you how to upgrade existing sites (if there's
> actually anything to do; usually there won't be).
>
> You can't upgrade to the *very* latest copy of the code in the git repo
> (actually you can, but it requires some git/bundler fu that I won't be
> documenting; it's extra complexity with no real benefit). If there are any
> commits in the Git repo that people need urgently I'll release a new version
> of the gem.
>