Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


Forgot your password?
Close
typodupeerror
×
Apache Businesses Software Apple

Setting Up A Site Server with Jaguar 104

Posted by Hemos from the run-faster-better dept.
rgraham writes "James Duncan Davidson (the original author of Apache Tomcat and Apache Ant) has an article over at O'Reilly's MacDevCenter that walks you through the steps of not only getting Apache up and running on 10.2 (pretty simple, I know) but also DNS and Mail. The aricle goes along well with Alan Graham article on how to setup your own .Mac type service."
This discussion has been archived. No new comments can be posted.

Setting Up A Site Server with Jaguar More

Setting Up A Site Server with Jaguar

Comments Filter:

  • Apache on OS X can do a lot more than that (Score:3, Informative)

    by ynotds ( 318243 ) on Sunday September 08, 2002 @06:44AM (#4215217) Homepage Journal
    The last line of /etc/httpd/httpd.conf in the default OS X.1.5 installation reads:

    Include /private/etc/httpd/users

    one /private/etc/httpd/users file being added for each user which enable you to serve anything you put in the Sites folder in your personal home directory. These are served in turn as http://your.domain.name/~username/page.html or the prevailing DirectoryIndex file to you (me) locally as http://127.0.0.1/~ynotds/

    The main config file includes a script alias to run any CGI scripts in /library/webserver/CGI-Executables

    They have put one Perl test script in that directory which you can view locally at http://127.0.0.1/cgi-bin/test-cgi [127.0.0.1], or at least you can after you have done a

    sudo chmod 775 /library/webserver/CGI-Executables/*

    from your Terminal window.

    From there, it isn't a lot of work to tweak your config files and uncomment AddHandler cgi-script .cgi to get scripts running throughout your site.

    Of course the real point to setting up your Mac as a fully functional server is that you get to do all your editing in BBEdit [barebones.com] which not only does syntax checking and colour coding on the fly of HTML, Perl, JavaScript and more, but also can directly run Perl in an open document window, enabling you to all manner of extrancting and reporting on the fly.

    Now I just need to get brave enough to install MySQL.
    • Of course the real point to setting up your Mac as a fully functional server is that you get to do all your editing in BBEdit which not only does syntax checking and colour coding on the fly of HTML, Perl, JavaScript and more, but also can directly run Perl in an open document window, enabling you to all manner of extrancting and reporting on the fly.

      That would be nice; we've never seen anything like that [gnu.org] before in the Unix world...

      *smiles*

  • on jagwyre, setting apache and PHP and sendmail all on their own is doable for the not so experienced (like me)

    However, the shit hits the fan when you're trying to make php pages send mail. SO far, I've tried every walkthrough I could find, but still get errors like this (sorry for long lines):


    Sep 7 12:51:19 visbak sendmail[448]: g87ApJxR000448: from=www, size=262, class=0, nrcpts=1, msgid=, relay=localhost
    Sep 7 12:51:20 visbak sendmail[450]: g87ApJxR000448: to="jeroen clarysse" , ctladdr=www (70/70), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30241, relay=in.mx.skynet.be. [195.238.3.129], dsn=5.6.0, stat=Data format error
    Sep 7 12:51:20 visbak sendmail[450]: g87ApJxR000448: g87ApKxQ000450: DSN: Data format error
    Sep 7 12:51:20 visbak sendmail[451]: g87ApKxQ000450: SYSERR(www): openmailer: insufficient privileges to change gid, RunAsUid=70, new_gid=0, gid=70, egid=25Sep 7 12:51:20 visbak sendmail[450]: g87ApKxQ000450: to=www, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31286, dsn=4.0.0, stat=Deferred: local mailer (/usr/bin/procmail) exited with EX_TEMPFAIL

    Anyone an idea ?
  • I've been enjoying using my iMac as a development server, but Apple sure doesn't make it easy when they change the file locations and settings with every upgrade and security tweak.

  • Ah, the joy of a real dev/small deployment/test bo (Score:4, Insightful)

    by ronabop ( 520121 ) on Sunday September 08, 2002 @08:57AM (#4215387)
    What, to me, is a real development/test box?

    1. It's not some wonky, secure, stripped, stable *nix box that can't run GUI IDEs.

    2. It can give me multicolored colored visual cues to code, so monochrome terminal sessions are out. Colored terminals are OK, but they lack the same elegance of a full GUI.

    3. It can quickly deal with running those additional programs I need when reading laughable client 'specs' in PowerPoint, MS word, HTML email from hell, etc.

    4. The code, on my GUI-heavy isolated dev box, can run identically to the code deployed on the stripped, burly, boxen.

    5. If I need to test speeds without a GUI, I can ignore it, and use the box in a stripped, clean, mode.

    6. It must be stable without being cold and wooden (Red flag of personal preference, I find almost all *nix platforms to be far less comfortable than they could potentially be. I know the KDE/Gnome/Solaris folks are working on it, and have their advantages as well)

    7. It must support additional "development necessary tools" such as playing mp3's, accounting for my time with professional accounting software, play mpg's, and run the occasional "break tool" in the form of some game that isn't 5 (or more) years old.

    8. It must support running javascript, and be able to test IE, NN, *and* lynx, and be able to run MacOS 9, MacOS X, X windows (and sub-managers), as well as MS windows (and their many variants).

    9. The hardware and software should need my personal intervention for tweaking and updates, well, almost never. I am not paid to update my box, I am paid for writing original code.

    I run a business, and I use (deep breath) LinuxPPC, Yellow Dog Linux, SuSe (on X86 and PPC), Debian (on PPC and X86), Mac OSX, RedHatX86 (four versions), OpenBSD (PPC and X86), FreeBSD (X86), SunOS (really, some clients still use it), Solaris (all 'of the flock, ugly), Win 3.1, Win 95, Win 98, Win ME, Win NT 3.x, Win NT 4.x, Win2K, Win XP (all).

    Of all of the above OS's, which one, do you think, can actually do requirements 1-9? (There's only one, take your time...) I used to do dev work on no less than 3 different boxes a day to meet those requirements. Now I use one.

    Of course, if I have a few sites with a few million hits a day (I do), I'll host it elsewhere than my test box, an OS X box.. But I'm not going to develop on that box. I'm going to develop on a box that makes me the most productive, a box where I don't care about IRQ's, drivers, optimizing window managers, running rpm or apt-get or any other time-wasting CLUI tools that interfere with writing code.

    For writing code, use a box that meets *your* needs. All platforms prior to OS X meant I was using far too many comps, because I needed multi-platform, multi-client-platform, code. No other platform allows you to test as many platforms at once as PPC/OS 9/OSX on Mac.

    -Bop

  • Mac OS X Server (Score:3, Informative)

    by daveschroeder ( 516195 ) on Sunday September 08, 2002 @09:37AM (#4215472)
    I know the point of this article is to set up all these services on plain-jane Mac OS X, but even easier than all that, and still cheaper than (m)any commercial solutions, is Mac OS X Server:

    http://www.apple.com/macosx/server/ [apple.com]

    Instead of going through 4 pages of convoluted configuration (if that's not your cup of tea), Mac OS X Server reason for existence is to provice a nice GUI for all of the server components. It's really amazing; anyone here who likes Mac OS X and hasn't really seen what Apple's done with Mac OS X Server 10.2 should check it out.
  • im glad people are taking mac os x seriously now for servers. in spring 2002, i used by ibook running 10.1.4 to deliver an online voting system for a cs class project. along with apache we used tomcat, ant, and postgresql. setup was easy, i downloaded the source, compiled, and that was it. the only thing else i had to do to set it up was download the correct jdbc driver for postgres. (i think its included now...) the app itself was developed on freebsd 4.x and required no code changes from freebsd -> os x. when we presented it in class the only hitch was a mozilla 0.9 crash, and that was no biggie. macintosh + unix == WOW!
  • I don't know why that little blurb got in the summary. Actually reading the article you find the typical "explaination" that you should let someone else do it or read a book on Bind.

    When I went to get my server set up I looked all over for how to set up DNS so I could have a real domain name. Then I just went with DNSMadeEasy.com

    http://www.icarusindie.com/dotcom/

    gives a run down of all the components you need to get a web-server up and running and where to get them. My server has been running on Win2K Pro for 1 year 8 months and hasn't had a single crash.

    If someone has a REAL tutorial (step by step guide) on getting your computer set up as a name server or knows where to find one please post it. I'd personally like to run my own name server so I don't have to pay someone else or use a crappy ad ridden service.

    Ben
    • errr.... just register a domain name and have it pointed (via your registrar's name servers) at your web server, then. You can't get around paying for a (real) domain name* and vendors like NetSol (or whomever) will allow you to point at whatever IP you want. You don't need to have your own DNS server for that (and you can't just fire up a ns and add any domain name you want -- it doesn't work like that). In fact, that will be more of a headache for you and a bit like setting up a telephone company just to service your home phone line.

      * Well, OK, you 'can' get around paying for a domain name (just like you have) but you end up at someone else's mercy and it will not get you what you're asking for.

  • I cannot believe he didn't even mention turning on your firewall (which is so simple in OS X, since a GUI interface to the ipfw software that has always been there is now available right in System Preferences). It is very irresponsible to tell people to set up a server without telling them how to protect it. Come on. (I use BrickHouse [tds.net] instead of Apple's interface, but they both provide a GUI interface to ipfw, so it's pretty similar, just more full-featured.) Also, the author does not mention alternatives to Sendmail. Many people consider Postfix to be superior. See Installing Postfix and UW IMAP on MacOS X Server [afp548.com] for instructions on setting it up for OS X.

Slashdot Top Deals

If all else fails, lower your standards.

Close