This is a recent development with the extensions moving into gems. I've found that the common way to take care of this is to run the following tasks:
$ rake radiant:extensions:update_all $ rake db:migrate:extensions That'll run them all. - Joel On Tue, Jun 21, 2011 at 11:08 AM, Benny Degezelle < [email protected]> wrote: > Gemified extensions should have an extra rake task that copies their rake > tasks to the project's lib/tasks/. > So; > - add an extension gem to config/environment.rb > - run rake radiant:extensions:update_all > - run rake db:migrate:extensions or rake > radiant:gemmified_extension:migrate (the rake task will be made available by > the previous step) > > > 2011/6/21 Michael Stalker <[email protected]> > >> I've been copying my local JavaScript and CSS and pasting it in the >> remote site when I set up a Radiant site. That's not exactly >> automated, I know, but it doesn't take long for me. >> >> When I deploy a Radiant site, I've already done my asset updates and >> migrations locally, so all that work get deployed. >> >> -Michael >> >> >> On Jun 21, 9:49 am, [email protected] wrote: >> > I am working with deploying Radiant now and I am also curious in this >> area. >> > I noticed in the extension registry a capistrano extension aimed at >> > updating assets etc. that might be an answer. I would appreciate >> > suggestions re deployment. I am concerned about workflow since I want to >> >> > develop my sass stylesheets and javascript stuff off line and then find >> a >> > quick way to update them in the database. >> > >> > It seem to me that there are two issues - Deploying Radiant to begin >> with >> > which is the same as any other rails app - and then upgrading content >> > styles etc that is held in the database >> > >> > I would be glad for suggestion on either >> > >> > Thanks >> > >> > Tom >> > >> > On , Michael Stalker <[email protected]> wrote: >> > >> > >> > >> > >> > >> > >> > >> > > It seems like some people are gemifying their Radiant extensions, but >> > > it's not clear to me what is the best way to run their migrations and >> > > asset updates. Is there a standard way to handle that? I could install >> > > the extension, run the migrations and updates, uninstall the >> > > extension, and then use the gem. That process seems a bit long, >> > > though. >> > > I've looked through the group archives and Googled a bit, but what are >> > > your suggestions? >> > > > > -- > Met vriendelijke groeten, > > Benny Degezelle > > Gorilla webdesign > www.gorilla-webdesign.be >
