Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Jeroen Janssen
On Thu, Jan 29, 2009 at 6:49 PM, Chaim Kirby
chaim.ki...@childrens.harvard.edu wrote:
 I'm trying to get a clear view in my head of what happens when
 extensions are deployed to a server, and the process that I can use to
 deploy them.  I have noticed some extensions come with deployment
 directions and others don't. Is there some standard set of commands I
 should be using to deploy an extension? I searched through the
 documentation, but did not find an authoritative guide.

I think there are two rake tasks related to extensions that you might
be interested in:

rake db:migrate:extensions
rake radiant:extensions:update_all

These rake tasks will perform actions as specified by an extension.
(i.e. run the database migration, install any public assets from the
extensions).

Best regards,

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


Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Nate Turnage
On Thu, Jan 29, 2009 at 12:23 PM, Jeroen Janssen
jeroen.jans...@gmail.comwrote:

 rake db:migrate:extensions
 rake radiant:extensions:update_all



Or if you don't want to migrate extensions after they have already been
migrated, assuming the extension is called templates, this works:

rake radiant:extensions:templates:migrate
rake radiant:extensions:templates:update



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


Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Chaim Kirby
Nate Turnage wrote:
 On Thu, Jan 29, 2009 at 12:23 PM, Jeroen Janssen
 jeroen.jans...@gmail.comwrote:
 
 rake db:migrate:extensions
 rake radiant:extensions:update_all

 
 
 Or if you don't want to migrate extensions after they have already been
 migrated, assuming the extension is called templates, this works:
 
 rake radiant:extensions:templates:migrate
 rake radiant:extensions:templates:update
 
 
 
 ~Nate

How do I know if I want to migrate or not?

Chaim


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


Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Sean Cribbs
Migrations are idempotent.  That is, it doesn't hurt anything to run 
them again if you're unsure.


Sean

Chaim Kirby wrote:

Nate Turnage wrote:
  

On Thu, Jan 29, 2009 at 12:23 PM, Jeroen Janssen
jeroen.jans...@gmail.comwrote:



rake db:migrate:extensions
rake radiant:extensions:update_all

  

Or if you don't want to migrate extensions after they have already been
migrated, assuming the extension is called templates, this works:

rake radiant:extensions:templates:migrate
rake radiant:extensions:templates:update



~Nate



How do I know if I want to migrate or not?

Chaim


___
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] Extenision help for a newbie

2009-01-29 Thread Chaim Kirby
Ok - trying it out I get an error.
I put the extension page_group_permissions in my vendor/extensions
folder and ran (from my $RADIANT_HOME):

# rake db:migrate:extensions

got:
(in /opt/radiant)
rake aborted!
PGError: ERROR:  relation extension_meta does not exist
: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
d.adsrc, a.attnotnull
  FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
 WHERE a.attrelid = 'extension_meta'::regclass
   AND a.attnum  0 AND NOT a.attisdropped
 ORDER BY a.attnum

(See full trace by running task with --trace)

please help.

Thanks,
Chaim

Sean Cribbs wrote:
 Migrations are idempotent.  That is, it doesn't hurt anything to run 
 them again if you're unsure.
 
 Sean
 
 Chaim Kirby wrote:
 Nate Turnage wrote:
   
 On Thu, Jan 29, 2009 at 12:23 PM, Jeroen Janssen
 jeroen.jans...@gmail.comwrote:

 
 rake db:migrate:extensions
 rake radiant:extensions:update_all

   
 Or if you don't want to migrate extensions after they have already been
 migrated, assuming the extension is called templates, this works:

 rake radiant:extensions:templates:migrate
 rake radiant:extensions:templates:update



 ~Nate
 
 How do I know if I want to migrate or not?

 Chaim


 ___
 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] Extenision help for a newbie

2009-01-29 Thread Sean Cribbs
Wow, that's a weird error.  I read on the Raleigh.rb mailing list over 
the past few days about some strangeness with Rails and PostrgeSQL, 
having to do with using the root schema, etc.  Not sure if that relates.


Did your Radiant bootstrap ok?

Sean

Chaim Kirby wrote:

Ok - trying it out I get an error.
I put the extension page_group_permissions in my vendor/extensions
folder and ran (from my $RADIANT_HOME):

# rake db:migrate:extensions

got:
(in /opt/radiant)
rake aborted!
PGError: ERROR:  relation extension_meta does not exist
: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
d.adsrc, a.attnotnull
  FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
 WHERE a.attrelid = 'extension_meta'::regclass
   AND a.attnum  0 AND NOT a.attisdropped
 ORDER BY a.attnum

(See full trace by running task with --trace)

please help.

Thanks,
Chaim

Sean Cribbs wrote:
  
Migrations are idempotent.  That is, it doesn't hurt anything to run 
them again if you're unsure.


Sean

Chaim Kirby wrote:


Nate Turnage wrote:
  
  

On Thu, Jan 29, 2009 at 12:23 PM, Jeroen Janssen
jeroen.jans...@gmail.comwrote:




rake db:migrate:extensions
rake radiant:extensions:update_all

  
  

Or if you don't want to migrate extensions after they have already been
migrated, assuming the extension is called templates, this works:

rake radiant:extensions:templates:migrate
rake radiant:extensions:templates:update



~Nate



How do I know if I want to migrate or not?

Chaim


___
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] Extenision help for a newbie

2009-01-29 Thread Chaim Kirby
Sean Cribbs wrote:
 Wow, that's a weird error.  I read on the Raleigh.rb mailing list over 
 the past few days about some strangeness with Rails and PostrgeSQL, 
 having to do with using the root schema, etc.  Not sure if that relates.
 
 Did your Radiant bootstrap ok?
 
 Sean

It bootstrapped fine, and I have the default styled blog when I go to
the site I am hosting it on.
Any thoughts, or should I try to use another db (not sure if I can - I
am implementing this but have some mandates from On High(TM))

Chaim

 
 Chaim Kirby wrote:
 Ok - trying it out I get an error.
 I put the extension page_group_permissions in my vendor/extensions
 folder and ran (from my $RADIANT_HOME):

 # rake db:migrate:extensions

 got:
 (in /opt/radiant)
 rake aborted!
 PGError: ERROR:  relation extension_meta does not exist
 : SELECT a.attname, format_type(a.atttypid, a.atttypmod),
 d.adsrc, a.attnotnull
   FROM pg_attribute a LEFT JOIN pg_attrdef d
 ON a.attrelid = d.adrelid AND a.attnum = d.adnum
  WHERE a.attrelid = 'extension_meta'::regclass
AND a.attnum  0 AND NOT a.attisdropped
  ORDER BY a.attnum

 (See full trace by running task with --trace)

 please help.

 Thanks,
 Chaim

 Sean Cribbs wrote:
   
 Migrations are idempotent.  That is, it doesn't hurt anything to run 
 them again if you're unsure.

 Sean

 Chaim Kirby wrote:
 
 Nate Turnage wrote:
   
   
 On Thu, Jan 29, 2009 at 12:23 PM, Jeroen Janssen
 jeroen.jans...@gmail.comwrote:

 
 
 rake db:migrate:extensions
 rake radiant:extensions:update_all

   
   
 Or if you don't want to migrate extensions after they have already been
 migrated, assuming the extension is called templates, this works:

 rake radiant:extensions:templates:migrate
 rake radiant:extensions:templates:update



 ~Nate
 
 
 How do I know if I want to migrate or not?

 Chaim


 ___
 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
 


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


Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Chaim Kirby
Nate Turnage wrote:
 On Thu, Jan 29, 2009 at 1:50 PM, Sean Cribbs seancri...@gmail.com wrote:
 
 Did your Radiant bootstrap ok?

 
 
 I am guessing that is the problem, too.
 
 
 ~Nate

Here is the output from the bootstrapping step (it is a lot):

# rake production db:bootstrap
(in /opt/radiant)
This task will destroy any data in the database. Are you sure you want to
continue? [yn] y
== 1 CreateRadiantTables: migrating
===
-- create_table(config, {:force=true})
NOTICE:  CREATE TABLE will create implicit sequence config_id_seq for
serial column config.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
config_pkey for table config
   - 0.0434s
-- add_index(config, [key], {:name=key, :unique=true})
   - 0.0325s
-- create_table(pages, {:force=true})
NOTICE:  CREATE TABLE will create implicit sequence pages_id_seq for
serial column pages.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
pages_pkey for table pages
   - 0.0531s
-- create_table(page_parts, {:force=true})
NOTICE:  CREATE TABLE will create implicit sequence page_parts_id_seq
for serial column page_parts.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
page_parts_pkey for table page_parts
   - 0.0681s
-- create_table(snippets, {:force=true})
NOTICE:  CREATE TABLE will create implicit sequence snippets_id_seq
for serial column snippets.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
snippets_pkey for table snippets
   - 0.0695s
-- add_index(snippets, [name], {:name=name, :unique=true})
   - 0.0222s
-- create_table(layouts, {:force=true})
NOTICE:  CREATE TABLE will create implicit sequence layouts_id_seq for
serial column layouts.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
layouts_pkey for table layouts
   - 0.0396s
-- create_table(users, {:force=true})
NOTICE:  CREATE TABLE will create implicit sequence users_id_seq for
serial column users.id
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
users_pkey for table users
   - 0.0511s
-- add_index(users, [login], {:name=login, :unique=true})
   - 0.0286s
== 1 CreateRadiantTables: migrated (0.4126s)
==

== 2 InsertInitialData: migrating
=
== 2 InsertInitialData: migrated (0.s)


== 3 RenameBehaviorColumn: migrating
==
-- rename_column(:pages, :behavior, :behavior_id)
   - 0.0029s
== 3 RenameBehaviorColumn: migrated (0.0031s)
=

== 4 RenameFilterColumn: migrating

-- rename_column(:page_parts, :filter, :filter_id)
   - 0.0041s
-- rename_column(:snippets, :filter, :filter_id)
   - 0.0031s
== 4 RenameFilterColumn: migrated (0.0075s)
===

== 5 AddVirtualColumnToPage: migrating

-- add_column(pages, virtual, :boolean, {:default=false, :null=false})
   - 0.0083s
== 5 AddVirtualColumnToPage: migrated (0.0085s)
===

== 6 IntegerColumnsToBoolean: migrating
===
== 6 IntegerColumnsToBoolean: saving User data

-- remove_column(users, admin)
   - 0.0035s
-- add_column(users, admin, :boolean, {:default=false, :null=false})
   - 0.0084s
== 6 IntegerColumnsToBoolean: restoring User data
=
== 6 IntegerColumnsToBoolean: saving User data

-- remove_column(users, developer)
   - 0.0027s
-- add_column(users, developer, :boolean, {:default=false,
:null=false})
   - 0.0081s
== 6 IntegerColumnsToBoolean: restoring User data
=
== 6 IntegerColumnsToBoolean: migrated (0.0258s)
==

== 7 RemoveVirtualColumnFromPage: migrating
===
-- remove_column(pages, virtual)
   - 0.0028s
== 7 RemoveVirtualColumnFromPage: migrated (0.0029s)
==

== 8 AddVirtualColumnToPageAgain: migrating
===
-- add_column(pages, virtual, :boolean, {:default=false, :null=false})
   - 0.0084s
== 8 AddVirtualColumnToPageAgain: migrated (0.0086s)
==

== 9 AddContentTypeFieldToLayout: migrating
===
-- add_column(layouts, content_type, :string, {:limit=40})
   - 0.0028s
== 9 AddContentTypeFieldToLayout: migrated (0.0029s)
==

== 10 MergeBehaviorsAndPages: migrating
===
== 10 MergeBehaviorsAndPages: converting behavior names to class names

-- rename_column(:pages, :behavior_id, :type)
   - 0.0025s
== 10 MergeBehaviorsAndPages: migrated (0.0032s)
==

== 11 RenameTypeColumnOnPageToClassName: migrating

-- rename_column(pages, type, class_name)
   - 0.0025s
== 11 

Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Nate Turnage
On Thu, Jan 29, 2009 at 1:50 PM, Sean Cribbs seancri...@gmail.com wrote:

 Did your Radiant bootstrap ok?



I am guessing that is the problem, too.


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


Re: [Radiant] Extenision help for a newbie

2009-01-29 Thread Chaim Kirby
I got the extension to install (it seems) by running:

#rake db:boostrap

instead of:

#rake production db:bootstrap (this is the command I found on the
radiant wiki: http://wiki.radiantcms.org/Create_your_first_Radiant_project)

then I run #ruby script/server -e production and I get the site home
page but the /admin page gives me:

Application error

Change this error message for exceptions thrown outside of an action
(like in Dispatcher setups or broken Ruby code) in public/500.html

Chaim


Chaim Kirby wrote:
 Nate Turnage wrote:
 On Thu, Jan 29, 2009 at 1:50 PM, Sean Cribbs seancri...@gmail.com wrote:

 Did your Radiant bootstrap ok?


 I am guessing that is the problem, too.


 ~Nate
 
 Here is the output from the bootstrapping step (it is a lot):
 
 # rake production db:bootstrap
 (in /opt/radiant)
 This task will destroy any data in the database. Are you sure you want to
 continue? [yn] y
 == 1 CreateRadiantTables: migrating
 ===
 -- create_table(config, {:force=true})
 NOTICE:  CREATE TABLE will create implicit sequence config_id_seq for
 serial column config.id
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 config_pkey for table config
- 0.0434s
 -- add_index(config, [key], {:name=key, :unique=true})
- 0.0325s
 -- create_table(pages, {:force=true})
 NOTICE:  CREATE TABLE will create implicit sequence pages_id_seq for
 serial column pages.id
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 pages_pkey for table pages
- 0.0531s
 -- create_table(page_parts, {:force=true})
 NOTICE:  CREATE TABLE will create implicit sequence page_parts_id_seq
 for serial column page_parts.id
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 page_parts_pkey for table page_parts
- 0.0681s
 -- create_table(snippets, {:force=true})
 NOTICE:  CREATE TABLE will create implicit sequence snippets_id_seq
 for serial column snippets.id
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 snippets_pkey for table snippets
- 0.0695s
 -- add_index(snippets, [name], {:name=name, :unique=true})
- 0.0222s
 -- create_table(layouts, {:force=true})
 NOTICE:  CREATE TABLE will create implicit sequence layouts_id_seq for
 serial column layouts.id
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 layouts_pkey for table layouts
- 0.0396s
 -- create_table(users, {:force=true})
 NOTICE:  CREATE TABLE will create implicit sequence users_id_seq for
 serial column users.id
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 users_pkey for table users
- 0.0511s
 -- add_index(users, [login], {:name=login, :unique=true})
- 0.0286s
 == 1 CreateRadiantTables: migrated (0.4126s)
 ==
 
 == 2 InsertInitialData: migrating
 =
 == 2 InsertInitialData: migrated (0.s)
 
 
 == 3 RenameBehaviorColumn: migrating
 ==
 -- rename_column(:pages, :behavior, :behavior_id)
- 0.0029s
 == 3 RenameBehaviorColumn: migrated (0.0031s)
 =
 
 == 4 RenameFilterColumn: migrating
 
 -- rename_column(:page_parts, :filter, :filter_id)
- 0.0041s
 -- rename_column(:snippets, :filter, :filter_id)
- 0.0031s
 == 4 RenameFilterColumn: migrated (0.0075s)
 ===
 
 == 5 AddVirtualColumnToPage: migrating
 
 -- add_column(pages, virtual, :boolean, {:default=false, :null=false})
- 0.0083s
 == 5 AddVirtualColumnToPage: migrated (0.0085s)
 ===
 
 == 6 IntegerColumnsToBoolean: migrating
 ===
 == 6 IntegerColumnsToBoolean: saving User data
 
 -- remove_column(users, admin)
- 0.0035s
 -- add_column(users, admin, :boolean, {:default=false, :null=false})
- 0.0084s
 == 6 IntegerColumnsToBoolean: restoring User data
 =
 == 6 IntegerColumnsToBoolean: saving User data
 
 -- remove_column(users, developer)
- 0.0027s
 -- add_column(users, developer, :boolean, {:default=false,
 :null=false})
- 0.0081s
 == 6 IntegerColumnsToBoolean: restoring User data
 =
 == 6 IntegerColumnsToBoolean: migrated (0.0258s)
 ==
 
 == 7 RemoveVirtualColumnFromPage: migrating
 ===
 -- remove_column(pages, virtual)
- 0.0028s
 == 7 RemoveVirtualColumnFromPage: migrated (0.0029s)
 ==
 
 == 8 AddVirtualColumnToPageAgain: migrating
 ===
 -- add_column(pages, virtual, :boolean, {:default=false, :null=false})
- 0.0084s
 == 8 AddVirtualColumnToPageAgain: migrated (0.0086s)
 ==
 
 == 9 AddContentTypeFieldToLayout: