Re: [Radiant] [ANN] Ray extension
On 2008/07/21, at 13:37, Tim Gossett wrote: But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. I just pushed the changes up to github to support submodules during installation. What happens now is ray looks for a `git` command in your PATH, then if that's found it checks for `.git/HEAD` in your RAILS_ROOT and if that's found does a `git add submodule` otherwise just a regular `git clone` happens. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
On Tue, Jul 22, 2008 at 11:26 AM, john muhl [EMAIL PROTECTED] wrote: On 2008/07/21, at 13:37, Tim Gossett wrote: But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. I just pushed the changes up to github to support submodules during installation. What happens now is ray looks for a `git` command in your PATH, then if that's found it checks for `.git/HEAD` in your RAILS_ROOT and if that's found does a `git add submodule` otherwise just a regular `git clone` happens. Awesome. I've added it as a submodule of my playground Radiant install. Thanks. -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Aslak On Sun, Jul 20, 2008 at 12:54 AM, john muhl [EMAIL PROTECTED] wrote: One more tiny update to point out Ray no longer depends on wget for fallback, instead that functionality has been replaced using the standard Ruby HTTP library. Hopefully it will make Ray useful in a wider variety of environments. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
It is possible. I'm just not sure the best way to do it. When I started both options were considered and I guessed (possibly wrongly) most people aren't “scm'ing” their Radiant app. So instead of going around git init'ing everyone's RADIANT_ROOT for them I figured clones were less fuss, less muss. So would you change the default to pull-in a submodule? Or add another option to switch from clone to submodule mode (i.e. `use=submodule`)? On 2008/07/21, at 02:43, aslak hellesoy wrote: Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Aslak On Sun, Jul 20, 2008 at 12:54 AM, john muhl [EMAIL PROTECTED] wrote: One more tiny update to point out Ray no longer depends on wget for fallback, instead that functionality has been replaced using the standard Ruby HTTP library. Hopefully it will make Ray useful in a wider variety of environments. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
In the case that the project is in git, you could manually create the .gitsubmodule file from the sha of the HEAD of the extension, since the submodules are just git repos themselves. I may support a switch in the script/extension installer for a scenario like this, but it will require some thought. Sean john muhl wrote: It is possible. I'm just not sure the best way to do it. When I started both options were considered and I guessed (possibly wrongly) most people aren't “scm'ing” their Radiant app. So instead of going around git init'ing everyone's RADIANT_ROOT for them I figured clones were less fuss, less muss. So would you change the default to pull-in a submodule? Or add another option to switch from clone to submodule mode (i.e. `use=submodule`)? On 2008/07/21, at 02:43, aslak hellesoy wrote: Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Aslak On Sun, Jul 20, 2008 at 12:54 AM, john muhl [EMAIL PROTECTED] wrote: One more tiny update to point out Ray no longer depends on wget for fallback, instead that functionality has been replaced using the standard Ruby HTTP library. Hopefully it will make Ray useful in a wider variety of environments. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
You mean RAILS_ROOT, but yes, that would be reasonable. Sean john muhl wrote: On 2008/07/21, at 10:39, Sean Cribbs wrote: In the case that the project is in git, you could manually create the .gitsubmodule file from the sha of the HEAD of the extension, since the submodules are just git repos themselves. I may support a switch in the script/extension installer for a scenario like this, but it will require some thought. Now I'm thinking that it might be simplest to just look for RADIANT_ROOT/.git and if it's found switch into submodule mode, otherwise a clone is done. My thinking is that if you have a .git directory at RADIANT_ROOT you've either decided to scm your install or someone put it there for you because they wanted to scm your install. In either case the best option is be a submodule. On 2008/07/21, at 02:43, aslak hellesoy wrote: Can Ray install extensions as Git submodules? I always use Git submodules - I never copy. Does the above scenario sound like the behavior you were after? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
On Mon, Jul 21, 2008 at 2:25 PM, john muhl [EMAIL PROTECTED] wrote: On 2008/07/21, at 10:39, Sean Cribbs wrote: In the case that the project is in git, you could manually create the .gitsubmodule file from the sha of the HEAD of the extension, since the submodules are just git repos themselves. I may support a switch in the script/extension installer for a scenario like this, but it will require some thought. Now I'm thinking that it might be simplest to just look for RADIANT_ROOT/.git and if it's found switch into submodule mode, otherwise a clone is done. My thinking is that if you have a .git directory at RADIANT_ROOT you've either decided to scm your install or someone put it there for you because they wanted to scm your install. In either case the best option is be a submodule. I just passed over the Ray extension because I just saw deploy with Capistrano and thought deploying with git is easy enough. But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. How easily does this fold into an existing Radiant install? Will it detect the submodules that are there already? -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
On 2008/07/21, at 12:30, Sean Cribbs wrote: You mean RAILS_ROOT Whoops, you're right. I must have had Radiant on the brain. On 2008/07/21, at 13:37, Tim Gossett wrote: I just passed over the Ray extension because I just saw deploy with Capistrano and thought deploying with git is easy enough. and that part hasn't even been started yet :) I just removed those words from the github description, sorry about the confusion. But if it automatically installs extensions as git submodules, I'd be much more interested. Especially if the presence of a .git directory at the project's root automatically puts it in git mode. It doesn't do that yet, but it looks like where I'll be taking it the next time I have a few minutes to work on it. It's actually the presence of a working `git` command in your PATH that determines git or http mode. How easily does this fold into an existing Radiant install? Will it detect the submodules that are there already? If you've already installed extensions as submodules and then install Ray you'll be able to add more extensions as submodules (they'll be global to your project just like the others you added), except you can roll it all up in to one handy command, i.e. rake ray:extension:install name=mailer restart=passsenger – of course it won't do that today but within the next day it should be working that way. Pretty soon after that I'll be adding ray:update, ray:extension:update:all and ray:extension:update name=mailer commands and I'll make sure these work off submodules if you've got your extensions (even ray) installed that way. Thanks for the feedback. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
Just a note that Ray is no longer “sort of stupid about migrate/update tasks”. Now an effort is made to determine whether there are any tasks. If a `vendor/extensions/extension_name/lib/tasks/ extension_name_extension_tasks.rake` file is found, Ray takes a peek inside to determine whether there are migrate and update tasks and only runs tasks that it actually finds. If no `vendor/extensions/extension_name/lib/tasks/ extension_name_extension_tasks.rake` file is found the entire post install process is skipped. The changes are available on GitHub.___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
When I try this, with hub and fullname, I get a repository not found error. I think the problem is that the repos url is getting an extra / in there between the github name and the fullname of the extension. Remove that in the rake task and it works great. Keith Bingman On Jul 17, 2008, at 2:24 AM, john muhl wrote: rake ray:extension:install name=sweet-sauce hub=bob fullname=sweet- sauce_for-radiant Right now, Ray is sort of stupid about migrate/update tasks and just blindly runs them both for all extensions regardless. If an extension doesn't need one or both tasks run you might see some errors but they'll be harmless. Once an extension is installed it can be easily disabled or enabled with rake ray:extension:disable name=mailer rake ray:extension:enable name=mailer ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Ray extension
Thanks for catching that, the fix has been pushed up to GitHub. On 2008/07/17, at 03:58, Keith Bingman wrote: When I try this, with hub and fullname, I get a repository not found error. I think the problem is that the repos url is getting an extra / in there between the github name and the fullname of the extension. Remove that in the rake task and it works great. Keith Bingman On Jul 17, 2008, at 2:24 AM, john muhl wrote: rake ray:extension:install name=sweet-sauce hub=bob fullname=sweet- sauce_for-radiant Right now, Ray is sort of stupid about migrate/update tasks and just blindly runs them both for all extensions regardless. If an extension doesn't need one or both tasks run you might see some errors but they'll be harmless. Once an extension is installed it can be easily disabled or enabled with rake ray:extension:disable name=mailer rake ray:extension:enable name=mailer ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
