Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1

2009-10-12 Thread Nate Turnage
On Mon, Oct 12, 2009 at 12:26 PM, Anton Aylward anton.aylw...@rogers.comwrote:

 Arthur Gunn said the following on 10/12/2009 08:24 AM:
  Perhaps, then, you can suggest a source of How To for GIT for
  non-developers.
 
  There are no end of resources out there, my personal recommendation
  though:

  http://www-cs-students.stanford.edu/~blynn/gitmagic/http://www-cs-students.stanford.edu/%7Eblynn/gitmagic/

 Ah.  about 50 pages more than I wanted.
 Telling me all the things that as a non-developer I don't need to know
 about, and not answering fundamental questions like when do I have to
 worry about a 'module' or 'submodule' and how can I keep from geting
 an update from 0.9 when I've got a 0.6.9 based application or vice
 versa, and what if I'm using 0.9 and I try to ... clone? ... an
 extension that hasn't a 0.9 revision now but will have in the future?

 I'm sure I'm not the only person on this list who has questions like that.



I can assure you that you are not. I am also come from a 'non-developer'
background (wishing I had gotten that CS degree, though) and I blazed the
git trail myself back in January when I moved a project from 0.6.9 to 0.7.0.
There is a lot to learn, especially if you haven't worked with source
control before.

I tell ya what, I have been meaning to resurrect/rebuild my long dormant
blog and I'll make that the first topic. If you can give me a few days I'll
compile a short Newbies guide to Git and Radiant describing my whole
development process. It's something I promised to do a long time ago and
never had the time.

In the meantime, if you have any specific questions about the process,
please ask them. So far I see the git-related questions are:
- What are submodules? Which is really a question about how to install
extensions when your project is managed with git and is related to using
Ray.
- How can I make sure the extension I am using will work with my project
running v.X.X.X?

This isn't a git question that I intend to cover because I think it is in
the wiki already, but I'll answer it here:
- How can I install newer gem versions of Radiant but stay with 0.6.9 on
this project?

By default, Radiant will try and use the latest version of the gem that you
have installed. To use a specific version of Radiant, go into environment
file (config/environment.rb) and add this line under the require 'radius'
line (substitute your version for 0.8.1):
RADIANT_GEM_VERSION = '0.8.1'
Then save the file and restart the server.

What I am not certain on is how you *create* a Radiant project using a
specific version of the gem. If anyone could chime in here it would be
great. I didn't see it mentioned in the wiki either.

I hope that clears up some part of your confusion, Arthur. Like I said, I'll
get to the git 'splaining shortly. I know what it's like to have a developer
point you to a source of info chock-full of stuff that you don't understand
when you ask what seems like a simple question.



~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1

2009-10-12 Thread Dayne Broderson
On Mon, Oct 12, 2009 at 10:19 AM, Nate Turnage pixeln...@gmail.com wrote:


 snip


 What I am not certain on is how you *create* a Radiant project using a
 specific version of the gem. If anyone could chime in here it would be
 great. I didn't see it mentioned in the wiki either.

 snip


 ~Nate


Ahh, that is actually pretty easy.  Just ask gem where you're gems are
installed.  You can find that from 'gem environment' and looking at
GEM_PATHS.   Mine is typically /usr/local/lib/ruby/gems/1.8.   In that
directory is another gems directory with inside that each of your installed
gems.  If you have a few radiants installed they will be hanging out there.
Use the explicit path to the version of radiant you want.  Pasted below is
the series of commands from my box if I were interested in a 0.7.1 install:

[dbrod...@beef ~]$ gem environment
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
  - INSTALLATION DIRECTORY: /home/dbroders/usr/gems
  - RUBY EXECUTABLE: /usr/local//bin/ruby
  - EXECUTABLE DIRECTORY: /home/dbroders/usr/gems/bin
  - RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
  - GEM PATHS:
 *- /usr/local/lib/ruby/gems/1.8*
  - GEM CONFIGURATION:
 - :update_sources = true
 - :verbose = true
 - :benchmark = false
 - :backtrace = false
 - :bulk_threshold = 1000
  - REMOTE SOURCES:
 - http://gems.rubyforge.org/
[dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
[dbrod...@beef ~]$
/usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant


-dayne
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1

2009-10-12 Thread Nate Turnage
On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson da...@gina.alaska.eduwrote:


 Ahh, that is actually pretty easy.  Just ask gem where you're gems are
 installed.  You can find that from 'gem environment' and looking at
 GEM_PATHS.   Mine is typically /usr/local/lib/ruby/gems/1.8.   In that
 directory is another gems directory with inside that each of your installed
 gems.  If you have a few radiants installed they will be hanging out there.
 Use the explicit path to the version of radiant you want.  Pasted below is
 the series of commands from my box if I were interested in a 0.7.1 install:

 [dbrod...@beef ~]$ gem environment
 RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
  - INSTALLATION DIRECTORY: /home/dbroders/usr/gems
  - RUBY EXECUTABLE: /usr/local//bin/ruby
  - EXECUTABLE DIRECTORY: /home/dbroders/usr/gems/bin
  - RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
  - GEM PATHS:
 *- /usr/local/lib/ruby/gems/1.8*
  - GEM CONFIGURATION:
 - :update_sources = true
 - :verbose = true
 - :benchmark = false
 - :backtrace = false
 - :bulk_threshold = 1000
  - REMOTE SOURCES:
 - http://gems.rubyforge.org/
 [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
 radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
 [dbrod...@beef ~]$
 /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant


That's pretty easy? :^O

I guess it's not that difficult, but I could have sworn there was an easier
way. Something like this:
radiant -v=0.7.1 --database [mysql] project

That of course doesn't work, but I thought there was something easy like
that. I could be wrong, probably am.


~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1

2009-10-12 Thread john muhl
On Mon, Oct 12, 2009 at 3:02 PM, Nate Turnage pixeln...@gmail.com wrote:
 On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson da...@gina.alaska.eduwrote:
 [dbrod...@beef ~]$ gem environment
 ...
 [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
 radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
 [dbrod...@beef ~]$
 /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant

 That's pretty easy? :^O

 I guess it's not that difficult, but I could have sworn there was an easier
 way. Something like this:
 radiant -v=0.7.1 --database [mysql] project

 That of course doesn't work, but I thought there was something easy like
 that. I could be wrong, probably am.

i've found the following to be pretty easy to use once it's setup.

- clone the latest radiant source to somewhere in your home directory;
i use ~/.radiant

git clone git://github.com/radiant/radiant.git ~/.radiant

- add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as:

alias radiant-0.6.8=PWD=`pwd`  cd ~/.radiant  git checkout -q
0.6.8  cd $PWD  ~/.radiant/bin/radiant
alias radiant-0.6.9=PWD=`pwd`  cd ~/.radiant  git checkout -q
0.6.9  cd $PWD  ~/.radiant/bin/radiant
alias radiant-0.7.0=PWD=`pwd`  cd ~/.radiant  git checkout -q
0.7.0  cd $PWD  ~/.radiant/bin/radiant
alias radiant-0.7.1=PWD=`pwd`  cd ~/.radiant  git checkout -q
0.7.1  cd $PWD  ~/.radiant/bin/radiant
alias radiant-0.8.0=PWD=`pwd`  cd ~/.radiant  git checkout -q
0.8.0  cd $PWD  ~/.radiant/bin/radiant
alias radiant-0.8.1=PWD=`pwd`  cd ~/.radiant  git checkout -q
0.8.1  cd $PWD  ~/.radiant/bin/radiant
alias radiant-edge=PWD=`pwd`  cd ~/.radiant  git checkout -q
master  cd $PWD  ~/.radiant/bin/radiant

(http://gist.github.com/208708 in case the mailing list mangles the
line endings)

- reload your .bashrc (or .profile or whatever you edited); i.e.
`source ~/.bashrc`

you can test them by running commands like `radiant-0.7.1 --version`
and `radiant-0.8.1 --version`

you may see errors having to do with submodules but those are harmless
for the use of simply being able to generate new sites from any
version of radiant.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1

2009-10-12 Thread john muhl
oh and once you've created a radiant from an older version (or edge)
you probably want to freeze it with `rake radiant:freeze:edge
TAG=0.7.1` or whatever

On Mon, Oct 12, 2009 at 3:35 PM, john muhl johnm...@gmail.com wrote:
 On Mon, Oct 12, 2009 at 3:02 PM, Nate Turnage pixeln...@gmail.com wrote:
 On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson 
 da...@gina.alaska.eduwrote:
 [dbrod...@beef ~]$ gem environment
 ...
 [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
 radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
 [dbrod...@beef ~]$
 /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant

 That's pretty easy? :^O

 I guess it's not that difficult, but I could have sworn there was an easier
 way. Something like this:
 radiant -v=0.7.1 --database [mysql] project

 That of course doesn't work, but I thought there was something easy like
 that. I could be wrong, probably am.

 i've found the following to be pretty easy to use once it's setup.

 - clone the latest radiant source to somewhere in your home directory;
 i use ~/.radiant

 git clone git://github.com/radiant/radiant.git ~/.radiant

 - add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as:

 alias radiant-0.6.8=PWD=`pwd`  cd ~/.radiant  git checkout -q
 0.6.8  cd $PWD  ~/.radiant/bin/radiant
 alias radiant-0.6.9=PWD=`pwd`  cd ~/.radiant  git checkout -q
 0.6.9  cd $PWD  ~/.radiant/bin/radiant
 alias radiant-0.7.0=PWD=`pwd`  cd ~/.radiant  git checkout -q
 0.7.0  cd $PWD  ~/.radiant/bin/radiant
 alias radiant-0.7.1=PWD=`pwd`  cd ~/.radiant  git checkout -q
 0.7.1  cd $PWD  ~/.radiant/bin/radiant
 alias radiant-0.8.0=PWD=`pwd`  cd ~/.radiant  git checkout -q
 0.8.0  cd $PWD  ~/.radiant/bin/radiant
 alias radiant-0.8.1=PWD=`pwd`  cd ~/.radiant  git checkout -q
 0.8.1  cd $PWD  ~/.radiant/bin/radiant
 alias radiant-edge=PWD=`pwd`  cd ~/.radiant  git checkout -q
 master  cd $PWD  ~/.radiant/bin/radiant

 (http://gist.github.com/208708 in case the mailing list mangles the
 line endings)

 - reload your .bashrc (or .profile or whatever you edited); i.e.
 `source ~/.bashrc`

 you can test them by running commands like `radiant-0.7.1 --version`
 and `radiant-0.8.1 --version`

 you may see errors having to do with submodules but those are harmless
 for the use of simply being able to generate new sites from any
 version of radiant.

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: Git Confusion - thread detour from [Radiant] [ANN] Radiant 0.9.0 RC1

2009-10-12 Thread Nate Turnage
On Mon, Oct 12, 2009 at 3:35 PM, john muhl johnm...@gmail.com wrote:
snip

 i've found the following to be pretty easy to use once it's setup.

 - clone the latest radiant source to somewhere in your home directory;
 i use ~/.radiant

 git clone git://github.com/radiant/radiant.git ~/.radiant

 - add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as:

/snip


That's insanely cool if you don't use the gem. I might switch to doing it
that way. If you don't mind, I may use that in my tutes.


~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant