Re: [Openinteract-help] "No template found" error

[Chris W. <ch...@cw...>]

* Ken Youens-Clark (ky...@gm...) [050415 10:26]:
> 
> Ah, enlightenment!  Yes, you are right.  I changed the action.ini in 
> the Website dir and it works now.

Excellent!
 
> >>...
> >>I would like "oi2_manage package_all" to automatically kill an 
> >>existing .zip package of the same version, too.
> >
> >You mean delete the files in the pkg/mypackage-old-x.xx directory? 
> >That's a valid option, and related to the earlier one where we delete 
> >the files from a 'remove_package':
> >
> >  http://jira.openinteract.org/browse/OIN-158
> 
> OK, here's where I get really confused.  I set my $ENV{'OPENINTERACT2'} 
> = '/usr/local/openinteract' and then used "oi2_manage" to create the 
> "book" package in my "$HOME/work/oi2/book."  My understanding was that 
> I would work on the package outside of the OI2 $WEBSITE_DIR (the 
> "OPENINTERACT2" dir) and then use "oi2_manage package_all" to put my 
> latest stuff from $HOME/work into the $WEBSITE_DIR.

That's how it's supposed to work.

> What I'm seeing with this setup are a couple issues:
> 
> [1] My new stuff from $HOME/work doesn't always seem to get moved over, 
> or at least not to where I think.  Maybe I'm not understanding what the 
> "$WEBSITE_DIR/pkg" dir is for because I was under the (now discredited) 
> assumption that "$WEBSITE_DIR/pkg/book-xx/conf/action.ini" was used and 
> didn't even know about "$WEBSITE_DIR/conf/book/action.ini."  Also, I've 
> read something that the libs in "$WEBSITE_DIR/pkg/book-xx/" aren't used 
> but the ones in "$WEBSITE_DIR/tmplib" are.

That's a half-truth -- when you fire up the server the libs from
pkg/book-xx/ are copied to tmplib/. We do this so we don't have 15+
directories on @INC.

> ... Maybe 
> if you could just share your general workflow for creating OI2 apps -- 
> kind of a "best practices"?

You're doing it the right way. The other useful workflow is to edit
the live website files (especially for templates/HTML files) and once
you're done run a 'update_package' command to sync your development
package from the live package.
 
> [2] Running the mod_perl_solo version runs into many permissions 
> issues.  I first started out the tutorial using the "oi2_daemon" and 
> had no problems because it was running under my permissions, but moving 
> to Apache running as "nobody" I find that httpd can't write to many 
> directories ("logs," "error," "overflow," "cache") so I run around 
> chmod'ing 777, which isn't so good, eh?  Any advice?

It would probably be good to have a helper script for this that would
need to be run as root; or if anyone knows a standard solution I'm all
ears.
 
> I'm pretty excited by OI2.  I looked at Ruby on Rails, Class::DBI, 
> Maypole, Catalyst, etc., and OI2 was the first to really seem to work 
> for me.  If I can just figure out how to really get rolling, I think 
> this is going to save me a lot of time and make my users happy (to see 
> lots of solid interfaces produced quickly).

Thanks! I hope it continues. Reports like this are extremely useful
and greatly appreciated.

BTW, if you want/need to use Class::DBI in OI2 shoot me an email. I
have a module to enable this but don't want to put it on CPAN until
the next beta of OI2 is out since it relies on a feature in CVS.

Chris

-- 
Chris Winters (http://www.cwinters.com)
Building enterprise-capable snack solutions since 1988