From: Ken Youens-C. <ky...@gm...> - 2005-04-15 14:13:17
|
On Apr 15, 2005, at 7:14 AM, Chris Winters wrote: > On Apr 14, 2005, at 5:33 PM, Ken Youens-Clark wrote: >> Unfortunately, I had already checked that the "action.ini" was >> kosher. I even upped the package.ini::version and installed a new >> package. Still the same error. I also tried deleting older versions >> of the package installed into $WEBSITE_DIR, starting/stopping. I >> should mention that I'm doing all this on a Intel Celeron/Debian >> Woody system that I just set up expressly for testing/learning OI2. >> I installed Perl 5.8.6 from source and all the modules are the latest >> from CPAN. I'm using the Apache/mod_perl (solo) setup. > > Just to be clear: did you check the action.ini in the > $WEBSITE_DIR/conf/book/action.ini was ok? The reason I'm emphasizing > this is that there are two copies: one in the website directory and > one in the package directory: > > Website: $WEBSITE_DIR/conf/book/action.ini > Package: $WEBSITE_DIR/pkg/book-0.09/conf/action.ini > > The one in 'Package' is NOT used, the one in 'Website' is. > > (Sidenote: I'll create a new JIRA issue to automatically put a README > in the 'Package' directory with this information.) > > If the one in 'Website' checks out ok we've got some more > investigation to do. Ah, enlightenment! Yes, you are right. I changed the action.ini in the Website dir and it works now. >> ... >> 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. 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. So, what is the purpose of the "$WEBSITE_DIR/pkg/book-xx" dir? And should I be working my package contents in my "/usr/local/openinteract" dir or my "$HOME/work" dir? Or maybe I'm not using the right command ("package_all") to move my working code into the $WEBSITE_DIR? Maybe if you could just share your general workflow for creating OI2 apps -- kind of a "best practices"? [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? ------- 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, ky |