Menu
▾
▴
slashcode-general
|
From: Craig H. <cra...@go...> - 2007-09-25 13:39:11
|
I've found a couple of stories on slashcode.com regarding Slash on OSX, however nothing recent and I was wondering if the situation has changed any with Tiger (and indeed perhaps Leopard). For example, while somepody mentioned a good guide to installing mod_perl for OSX, AFAIK it was written around four years ago, and a lot has changed since then. Unlike back in the day, the likes of PHP4 and mod_perl can now be enabled in OSX simply by uncommenting them in httpd.conf, and MySQL (as well as PHP5) can be installed with a friendly binary. As someone who's looking to install Slash on Tiger, do any of these developments make things any more straightforward or does Slash still require everything to be built from scratch? If it's the latter, does anyone have any pointers for someone who's not afraid of the command line but a bit of a greenhorn when it comes to the likes of apt-get and make? Also, how does the OSX install process differ from the Linux one? Thanks! |
|
From: shane <sh...@lo...> - 2007-09-25 14:30:15
|
On Sep 25, 2007, at 9:39 AM, Craig Hand wrote: > I've found a couple of stories on slashcode.com regarding Slash on > OSX, however nothing recent and I was wondering if the situation > has changed any with Tiger (and indeed perhaps Leopard). For > example, while somepody mentioned a good guide to installing > mod_perl for OSX, AFAIK it was written around four years ago, and a > lot has changed since then. Unlike back in the day, the likes of > PHP4 and mod_perl can now be enabled in OSX simply by uncommenting > them in httpd.conf, and MySQL (as well as PHP5) can be installed > with a friendly binary. > > As someone who's looking to install Slash on Tiger, do any of these > developments make things any more straightforward or does Slash > still require everything to be built from scratch? If it's the > latter, does anyone have any pointers for someone who's not afraid > of the command line but a bit of a greenhorn when it comes to the > likes of apt-get and make? Also, how does the OSX install process > differ from the Linux one? > > Thanks! I do virtually all of my mod_perl/slashcode development on OSX machines. Typically, I don't replace the existing perl, I keep it. I install MySQL v5.x via one of the MySQL Installer Packages from mysql.com. I'll use fink or one of the other source code repo's to install some of the "extras" (ie GD, libreq, whatever) that don't come with the perl bundle Bundle::Slash (or, that perl packages w/in that bundle require). I do keep the stock Apache installed - but not to run slash. I install Apache 1.3.x from tarball and keep it in /usr/local/slash. It's not that you probably couldn't try and use the stock Apache, but I typically use that for other code development. It's easier for me if they are completely separate. And that way I can match the version of the tarball w/ what we are running in production at any given time from any given system, and I don't have to worry about messing with the stock Apache wrt Apple Updates (if any). As long as you follow the INSTALL documentation (I recommend setting up CPAN as it says, because it makes the install of Bundle::Slash _far_ easier) you're good to go. Once you have all the required software that slash needs installed, installation is no different from a linux box. Just 'make install'. If you do use the stock Apache, I would love to hear back from you as to how it goes and what you had to do to make it work, if anything. Shane -- My slashcode stuff: http://slash.lottadot.com/ Slashcode faq: http://slash.lottadot.com/slash-faq How to ask a question: http://www.catb.org/~esr/faqs/smart- questions.html#before |
|
From: Craig H. <cra...@go...> - 2007-09-25 14:42:12
|
Thanks Shane, I'll give it another go tonight. I have a couple of questions though: If I'm installing a seperate instance of Apache from the default one, can I use the binary or will I have to install it with make install, and will it include mod_perl? Is there anything that I definately need to get via fink that's not mentioned in the Slash install file? Cheers, Craig On 25/09/2007, shane <sh...@lo...> wrote: > > > On Sep 25, 2007, at 9:39 AM, Craig Hand wrote: > > I've found a couple of stories on slashcode.com regarding Slash on OSX, > however nothing recent and I was wondering if the situation has changed any > with Tiger (and indeed perhaps Leopard). For example, while somepody > mentioned a good guide to installing mod_perl for OSX, AFAIK it was written > around four years ago, and a lot has changed since then. Unlike back in the > day, the likes of PHP4 and mod_perl can now be enabled in OSX simply by > uncommenting them in httpd.conf, and MySQL (as well as PHP5) can be > installed with a friendly binary. > > As someone who's looking to install Slash on Tiger, do any of these > developments make things any more straightforward or does Slash still > require everything to be built from scratch? If it's the latter, does anyone > have any pointers for someone who's not afraid of the command line but a bit > of a greenhorn when it comes to the likes of apt-get and make? Also, how > does the OSX install process differ from the Linux one? > > Thanks! > > > I do virtually all of my mod_perl/slashcode development on OSX machines. > Typically, I don't replace the existing perl, I keep it. I install MySQL > v5.x via one of the MySQL Installer Packages from mysql.com. I'll use fink > or one of the other source code repo's to install some of the "extras" (ie > GD, libreq, whatever) that don't come with the perl bundle Bundle::Slash > (or, that perl packages w/in that bundle require). > > > I do keep the stock Apache installed - but not to run slash. I install > Apache 1.3.x from tarball and keep it in /usr/local/slash. It's not that > you probably couldn't try and use the stock Apache, but I typically use that > for other code development. It's easier for me if they are completely > separate. And that way I can match the version of the tarball w/ what we are > running in production at any given time from any given system, and I don't > have to worry about messing with the stock Apache wrt Apple Updates (if > any). > > > As long as you follow the INSTALL documentation (I recommend setting up > CPAN as it says, because it makes the install of Bundle::Slash _far_ easier) > you're good to go. > > > Once you have all the required software that slash needs installed, > installation is no different from a linux box. Just 'make install'. > > > If you do use the stock Apache, I would love to hear back from you as to > how it goes and what you had to do to make it work, if anything. > > > Shane > > > > > -- > My slashcode stuff: http://slash.lottadot.com/ > Slashcode faq: http://slash.lottadot.com/slash-faq > How to ask a question: > http://www.catb.org/~esr/faqs/smart-questions.html#before > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > > |
|
From: shane <sh...@lo...> - 2007-09-25 17:25:47
|
I doubt you can use a binary. And besides, if you were going to use a binary, what'd be the point of not using the binary that's already built into the system? Generally I put the latest mod_perl, apache, mysql in /usr/local/src and untar/gz them all. Then I install Apache, bare, and make sure that works. Then do something like this (see the INSTALL for more specifics) to build Apache with mod_perl and all the goodies such that slash likes it and I can play with things like gzip/relocate/rewrite to emulate production tests/code: USE_APACI=1 ./configure \ --activate-module=src/modules/extra/mod_relocate.c \ --activate-module=src/modules/extra/mod_gzip.c \ --activate-module=src/modules/perl/libperl.a \ --enable-module=so \ --enable-module=alias \ --enable-module=rewrite \ --disable-module=info \ --disable-rule=EXPAT \ --disable-module=userdir \ --disable-module=status then perl Makefile.PL APACHE_SRC=/usr/local/src/apache_1.3.37 DO_HTTPD=1 \ USE_APACI=1 PERL_MARK_WHERE=1 EVERYTHING=1 \ APACHE_PREFIX=/usr/local/apache As to what you'd have to grab via fink. I don't know offhand. Whenever CPAN can't install a module, I drop to a CPAN shell and attempt the module install by hand. That generally shows/tells you if it's missing any libraries it needs. I then open up another term window, fire up fink and install that. Then hop back to CPAN and perl Makefile.PL && install etc etc. It can take a little bit of time. But once all the requirements are in place it's a snap. Shane On Sep 25, 2007, at 10:41 AM, Craig Hand wrote: > Thanks Shane, I'll give it another go tonight. I have a couple of > questions though: > > If I'm installing a seperate instance of Apache from the default > one, can I use the binary or will I have to install it with make > install, and will it include mod_perl? > > Is there anything that I definately need to get via fink that's not > mentioned in the Slash install file? > > Cheers, > Craig > > On 25/09/2007, shane <sh...@lo...> wrote: > > On Sep 25, 2007, at 9:39 AM, Craig Hand wrote: > >> I've found a couple of stories on slashcode.com regarding Slash on >> OSX, however nothing recent and I was wondering if the situation >> has changed any with Tiger (and indeed perhaps Leopard). For >> example, while somepody mentioned a good guide to installing >> mod_perl for OSX, AFAIK it was written around four years ago, and >> a lot has changed since then. Unlike back in the day, the likes of >> PHP4 and mod_perl can now be enabled in OSX simply by uncommenting >> them in httpd.conf, and MySQL (as well as PHP5) can be installed >> with a friendly binary. >> >> As someone who's looking to install Slash on Tiger, do any of >> these developments make things any more straightforward or does >> Slash still require everything to be built from scratch? If it's >> the latter, does anyone have any pointers for someone who's not >> afraid of the command line but a bit of a greenhorn when it comes >> to the likes of apt-get and make? Also, how does the OSX install >> process differ from the Linux one? >> >> Thanks! > > I do virtually all of my mod_perl/slashcode development on OSX > machines. Typically, I don't replace the existing perl, I keep it. > I install MySQL v5.x via one of the MySQL Installer Packages from > mysql.com. I'll use fink or one of the other source code repo's to > install some of the "extras" (ie GD, libreq, whatever) that don't > come with the perl bundle Bundle::Slash (or, that perl packages w/ > in that bundle require). > > > I do keep the stock Apache installed - but not to run slash. I > install Apache 1.3.x from tarball and keep it in /usr/local/slash. > It's not that you probably couldn't try and use the stock Apache, > but I typically use that for other code development. It's easier > for me if they are completely separate. And that way I can match > the version of the tarball w/ what we are running in production at > any given time from any given system, and I don't have to worry > about messing with the stock Apache wrt Apple Updates (if any). > > > As long as you follow the INSTALL documentation (I recommend > setting up CPAN as it says, because it makes the install of > Bundle::Slash _far_ easier) you're good to go. > > > Once you have all the required software that slash needs installed, > installation is no different from a linux box. Just 'make install'. > > > If you do use the stock Apache, I would love to hear back from you > as to how it goes and what you had to do to make it work, if anything. > > > Shane > > > > > -- > My slashcode stuff: http://slash.lottadot.com/ > Slashcode faq: http://slash.lottadot.com/slash-faq > How to ask a question: http://www.catb.org/~esr/faqs/smart- > questions.html#before > > > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general |
|
From: Craig H. <cra...@go...> - 2007-09-25 16:47:49
|
For example? I've been through all the alternatives and they all have problems. Either they don't do what Slash does, or they do but only with a lot of modification, or they do and have similar installation issues. While I'd love to use something easy to install that runs on shared hosting, I haven't come across anything that will do this that has a comment/moderation system as good as Slash. If there is something I've missed, do tell! On 25/09/2007, Eric Dannewitz <eri...@ja...> wrote: > > Why would you even want to install slash when there are so many other > great alternatives out there? > > Craig Hand wrote: > > I've found a couple of stories on slashcode.com > > <http://slashcode.com/> regarding Slash on OSX, however nothing recent > > and I was wondering if the situation has changed any with Tiger (and > > indeed perhaps Leopard). For example, while somepody mentioned a good > > guide to installing mod_perl for OSX, AFAIK it was written around four > > years ago, and a lot has changed since then. Unlike back in the day, > > the likes of PHP4 and mod_perl can now be enabled in OSX simply by > > uncommenting them in httpd.conf, and MySQL (as well as PHP5) can be > > installed with a friendly binary. > > > > As someone who's looking to install Slash on Tiger, do any of these > > developments make things any more straightforward or does Slash still > > require everything to be built from scratch? If it's the latter, does > > anyone have any pointers for someone who's not afraid of the command > > line but a bit of a greenhorn when it comes to the likes of apt-get > > and make? Also, how does the OSX install process differ from the Linux > > one? > > > > Thanks! > |
|
From: Craig H. <cra...@go...> - 2007-09-25 16:57:18
|
I've had a look at PostNuke, however I didn't manage to find a comparable moderation system, is there an extension that does anything similar to Slash? On 25/09/2007, Eric Dannewitz <eri...@ja...> wrote: > > I don't really think you looked enough. PHP Nuke would be one. > > I loved slash, and ran it for years, but it really is a pain to run and > update. > > Craig Hand wrote: > > For example? I've been through all the alternatives and they all have > > problems. Either they don't do what Slash does, or they do but only > > with a lot of modification, or they do and have similar installation > > issues. While I'd love to use something easy to install that runs on > > shared hosting, I haven't come across anything that will do this that > > has a comment/moderation system as good as Slash. If there is > > something I've missed, do tell! > > > > |
|
From: shane <sh...@lo...> - 2007-09-25 18:11:36
|
While this thread is probably OT (or minimally OT for OSX Install on Tiger thread) I'll chime in. I don't think updating Slashcode is difficult. Yesterday we just up'd from _169 to _175, 2 systems, 2 sets of code, in about a half an hour yesterday. Most of that was just double-triple checking for errors once the new version was installed/removed/installed on a dev system. What's a PITA, and admittedly so, is for the common person to attempt to upgrade from Slashcode v2.2.6 to current-cvs/T-Tag. There no "upgrademe.pl" script to run that "just does it". It's not that there aren't instructions on how to do the update. There are, in the INSTALL. It's not that those instructions don't work (they do). People would have to read them, and then _do them_. For people who have sites hosted by a slash-hosting company, most of those are 2.2.6, and most don't want to pay the man-hours to get everything upgraded. So they still run 2.2.6. Which wasn't css-based, and people went and modified/hacked the heck out of the templates to get css in there. So each of your customers templates are so wacked that updating them to CSS would either force the ISP to pay their guys to port the customizations (ha, ya, that'll happen) or you're forcing your customer to port their changes to CSS by XX date, which would more then likely be a rather painful process. But if you know what you're doing, are familiar w/ the upgrade process, etc. It's not bad. I've upgraded probably 10 or 15 customer's websites from 2.2.6 to current, and each probably averaged a little over an hour of time. If you do the upgrade to a later version that's css-ified, updates are then cake from that point. And most of the OSTG updates that come down the pipe are internal, or the more internal templates, so your custom css isn't messed with. Then you get the added functionality of the Instant Messenger updates, Discussion2, Ajax, tags, the Firehose, and more. <advertisement> FWIW, I do upgrade services and slash-hosting. If anyone's interested, email me off-list. </advertisement> Shane On Sep 25, 2007, at 12:57 PM, Craig Hand wrote: > I've had a look at PostNuke, however I didn't manage to find a > comparable moderation system, is there an extension that does > anything similar to Slash? > > On 25/09/2007, Eric Dannewitz <eri...@ja...> wrote: > I don't really think you looked enough. PHP Nuke would be one. > > I loved slash, and ran it for years, but it really is a pain to run > and > update. > > Craig Hand wrote: > > For example? I've been through all the alternatives and they all > have > > problems. Either they don't do what Slash does, or they do but only > > with a lot of modification, or they do and have similar installation > > issues. While I'd love to use something easy to install that runs on > > shared hosting, I haven't come across anything that will do this > that > > has a comment/moderation system as good as Slash. If there is > > something I've missed, do tell! > > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general -- My slashcode stuff: http://slash.lottadot.com/ Slashcode faq: http://slash.lottadot.com/slash-faq How to ask a question: http://www.catb.org/~esr/faqs/smart- questions.html#before |
|
From: Jamie M. <ja...@mc...> - 2007-09-25 18:36:59
|
I generally agree with Shane on this (except the advertisement part which I officially express no opinion on). Upgrading beyond 2.2.6 is hard; once you are beyond 2.2.6 it's easy if you take your time and read carefully. --=20 Jamie McCarthy http://mccarthy.vg/ ja...@mc... |
|
From: Craig H. <cra...@go...> - 2007-09-25 19:30:21
|
OK, I'm getting there, however Apache comes up with an error during configuration: Error: could not find any of these C compilers anywhere in your PATH: gcc cc acc c89 I tried installing GCC with Fink, however it still came up and after some Googling I installed GCC from the Apple Developer Tools. Still no dice however. On 25/09/2007, Jamie McCarthy <ja...@mc...> wrote: > > I generally agree with Shane on this (except the advertisement part > which I officially express no opinion on). Upgrading beyond 2.2.6 > is hard; once you are beyond 2.2.6 it's easy if you take your time > and read carefully. > -- > Jamie McCarthy > http://mccarthy.vg/ > ja...@mc... > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > |
Thanks for helping keep SourceForge clean.
X