Movable Type

2002-03-16 Thread Matt Patterson

Hey all.

Has anyone got Movable Type running on Mac OS X yet?

I'm debating whether to run it on my OS X box or my Linux box, and was
wondering whether there were any traumas awaiting which might make me
prefer the Linux box.

Thanks

Matt


-- 
   Matt Patterson | Typographer
   [EMAIL PROTECTED] | http://reprocessed.org/



Re: Movable Type

2002-03-16 Thread Nicolas Bertrand

Hi Matt

No trauma at all. A real piece of cake to install. just follow the 
instructions.

Cheers,

Nicolas

Le samedi 16 mars 2002, à 12:37 , Matt Patterson a écrit :

 Hey all.

 Has anyone got Movable Type running on Mac OS X yet?

 I'm debating whether to run it on my OS X box or my Linux box, and was
 wondering whether there were any traumas awaiting which might make me
 prefer the Linux box.

 Thanks

 Matt


 --
Matt Patterson | Typographer
[EMAIL PROTECTED] | http://reprocessed.org/





Re: Movable Type

2002-03-16 Thread Pete Prodoehl


Same here, a pretty simple install - one of the strengths of Movable Type.

Pete

--

 Has anyone got Movable Type running on Mac OS X yet?

 I'm debating whether to run it on my OS X box or my Linux box, and was
 wondering whether there were any traumas awaiting which might make me
 prefer the Linux box.




2,000,000,000 Web Pages--you only need 1. Save time with My Lycos.
http://my.lycos.com



Re: Movable Type

2002-03-16 Thread Morbus Iff

Has anyone got Movable Type running on Mac OS X yet?

Yup. I mention it in my Apache series on OS X. No
issues at all. I specifically mention it here:

 http://oreillynet.com/pub/a/mac/2001/12/14/apache_two.html?page=1

But the whole series is here:

 http://www.oreillynet.com/pub/ct/49

-- 
Morbus Iff ( insert pithy quote here )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Tech: http://www.oreillynet.com/pub/au/779 - articles and weblog
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus



Re: how to include a file

2002-03-16 Thread Michael Maibaum

On Sat, Mar 16, 2002 at 07:37:18PM -0600, Puneet Kishor wrote:
 question from a newbie. How do I include a code fragment in a perl 
 script so it first gets included and then interpreted/compiled?
 
 Ok. that's the short question. In other words, this is what I am trying 
 to do --
 
 I have one index.pl (this is a web app), and everything passes through 
 this. So, if the call is to index.pl?do=login then the login page is 
 included, if the call is to index.pl?do=verify then the verify page is 
 included. This is how I work in the world of other web programming (Cold 
 Fusion, PHP, etc.). This way I have to declare all my use statements (to 
 import packages), other declarations, param checking, etc. in one place. 
 I also have one master template, and everything else is simply 
 included...

look at HTML::Mason, you will like it :).
http://www.masonhq.com/

HTH

Michael
-- 
Dr Michael A. Maibaum - (W)+1 (415) 561 1682 - (H)+1 (415) 626 6733
[EMAIL PROTECTED] URL:http://www.gene-hacker.net/



Re: how to include a file

2002-03-16 Thread Michael Maibaum

On Sat, Mar 16, 2002 at 10:30:44PM -0600, Puneet Kishor wrote:
 Michael, Thanks for the Mason tip. It does look exactly like what I 
 need. Although I wonder how it compares with embperl... anyone any 
 thoughts?
I don't really know embperl well, so I'll leave that to someone else..
 
 On another note... I saw that the mod_perl lines were commented out in 
 my httpd.conf. Since mod_perl is required for Mason (well, Mason 
 performs best with mod_perl), I uncommented the mod_perl lines. Now 
 httpd won't start. I get the following error when I tail my error_log

Well, the stock apache (with stock perl) and stock mod_perl work fine.

It looks like you updated the perl on your machine...I recompiled
mod_perl and apache when I upgraded my perl
 
 perl: warning: Setting locale failed.
 perl: warning: Please check that your locale settings:
 LC_ALL = (unset),
 LANG = en_US
 are supported and installed on your system.
 perl: warning: Falling back to the standard locale (C).

This is a fairly minor issue, set LC_ALL to LC_ALL=C in the system
startup scripts, but this error shouldn't break anything.

For me, when I upgraded perl, mod_perl would crash apache until I
recompiled it.
 
 Looks like I have made a bigger mess than I was in.
Was apache working before this? Anything else in the error log?
 
 Please help, someone.

I imagine someone more expert than I could have something to add...
Michael
-- 
Dr Michael A. Maibaum - (W)+1 (415) 561 1682 - (H)+1 (415) 626 6733
[EMAIL PROTECTED] URL:http://www.gene-hacker.net/



Re: how to include a file

2002-03-16 Thread Puneet Kishor


On Saturday, March 16, 2002, at 10:49  PM, Michael Maibaum wrote:
 On another note... I saw that the mod_perl lines were commented out in
 my httpd.conf. Since mod_perl is required for Mason (well, Mason
 performs best with mod_perl), I uncommented the mod_perl lines. Now
 httpd won't start. I get the following error when I tail my error_log

 Well, the stock apache (with stock perl) and stock mod_perl work fine.

well, when I got my iBook it had the stock apache with stock perl on it, 
but I never activated the stock mod_perl (if it was there... I didn't 
check).

 It looks like you updated the perl on your machine...I recompiled
 mod_perl and apache when I upgraded my perl

Yes, I updated Perl to 5.6.1, and mod_perl and Apache using Ray 
Zimmerman's steps oft quoted on this and other lists. My results were 
the same as his (and many others) but for some reason I did not have any 
success with mod_perl. I guess I had disabled mod_perl and forgotten all 
about it. So, when I included it in this evening it Apache croaked with 
the following message...


 perl: warning: Setting locale failed.
 perl: warning: Please check that your locale settings:
 LC_ALL = (unset),
 LANG = en_US
 are supported and installed on your system.
 perl: warning: Falling back to the standard locale (C).

 This is a fairly minor issue, set LC_ALL to LC_ALL=C in the system
 startup scripts, but this error shouldn't break anything.

I remember something about this... I think I used to get this error 
everytime I would run perl in the Terminal, and then I used the SETENV 
command once to set the locale settings and I haven't experienced this 
error since in the Terminal. This is the first time I am seeing this in 
the error_log when trying to start Apache. I guess it seems Apache is 
not recognizing the locale settings that the Terminal recognizes.

 Looks like I have made a bigger mess than I was in.
 Was apache working before this? Anything else in the error log?

Yes, Apache works fine (and so does Perl) as long as I comment out the 
mod_perl load lines in httpd.conf. Only when I try to start Apache with 
mod_perl is that it croaks. Also, there are no syntax errors in my 
httpd.conf (at least according to apachectl configtest). I guess I have 
to make Apache recognize the locale settings, no? How do I do that for 
the entire system, preferably automatically when the system starts?

Thanks for the guidance,

pk/