[wplug] RE: wplug Digest, Vol 24, Issue 4

Tej Shah tshah at andrew.cmu.edu
Sat Feb 4 23:53:28 EST 2006


I have done both and these are my experiences:

 If you know Linux, and you have some sort of automated packaging system 
already installed (like apt or portage), then apache on Linux is MUCH 
easier to install than windows. If you don't have much experience with 
Linux or can't get any kind of  automated installer, then I say stick 
with windows. This is under the assumption you don't need PHP or MySQL. 
If you do need PHP and/or MySQL and you have some free time, you can try 
Kubuntu (http://www.kubuntu.org/) since it has a good installer built 
into it (Adept).

Now, to really answer your question:
Windows (from my experiance 2 years ago, some things may have changed 
since then):
    - Uses a Wizard Installer
    - Puts a taskbar icon on the bottom right of your screen (Nice if 
you just want to turn it off or on)
    - Once you restart your computer, Apache turns on every time
    - If you need to install PHP (which is also a wizard install), you 
need to edit the config file while is a text file afterwards
    - To add your own content, you can easily drag your files and drop 
them off to the default webpage directory (which I believe to be 
somewhere like C:/Program Files/Apache Foundation/httpd).
Linux:
    - Simple if you have an automated installer (like apt or portage).
    - A large pain to install if you don't have an automated installer 
(or have to compile it... agh!)
    - On (k)ubuntu, it automagicly sets up Apache to have PHP enabled 
when you install it
    - Most of the people on this mailing list will say it is more secure 
;-) (Bill Gates would tell you otherwise)
    - When you add files to your webpage directory (in many Linux 
systems, it is located in /var/www/ by default), the permissions are 
such that you need to either be a "SuperUser" or "root" to add your own 
stuff. If you don't know much about Unix-like permissions, this can 
become a major problem when you try to put up your own files up.
In both cases:
    - THERE IS NO easy graphical interface for setting it up (on both 
OS). Most of the GUIs for Apache are either not free and/or not user 
friendly. For my Human-computer interaction project, I tried to make a 
very User-Friendly GUI for setting up Apache but it just didn't work out 
well for a number of reasons.
    - You will have to play with the apache config text file in order to 
change which directory Apache will look at

    In conclusion, I have to know your specific situation in order to 
give you proper advice. I hope this long message helps you out.

PS: To the rest of the people, please feel free to correct me if I said 
something wrong.


Ying-Ju Suen wrote:
>
> Hello, I am wondering what are the differences between windows version 
> of Apache and Linux version of Apache.  Besides that, my friend 
> suggested me to use the windows one since it's easier to install.  
> What do you think?
>
> 1stDec
>
>     ------------------------------------------------------------------------
>     From:  /wplug-request at wplug.org/
>     Reply-To:  /wplug at wplug.org/
>     To:  /wplug at wplug.org/
>     Subject:  /wplug Digest, Vol 24, Issue 4/
>     Date:  /Sat, 4 Feb 2006 12:00:06 -0500/
>     >Send wplug mailing list submissions to
>     > wplug at wplug.org
>     >
>     >To subscribe or unsubscribe via the World Wide Web, visit
>     > http://www.wplug.org/mailman/listinfo/wplug
>     >or, via email, send a message with subject or body 'help' to
>     > wplug-request at wplug.org
>     >
>     >You can reach the person managing the list at
>     > wplug-owner at wplug.org
>     >
>     >When replying, please edit your Subject line so it is more specific
>     >than "Re: Contents of wplug digest..."
>     >
>     >
>     >Today's Topics:
>     >
>     >    1. Signing up with Apache (WAS: Re: 45 Minutes with High
>     >       Schoolers) (J Aaron Farr)
>     >
>     >
>     >----------------------------------------------------------------------
>     >
>     >Message: 1
>     >Date: Fri, 3 Feb 2006 15:43:28 -0500
>     >From: J Aaron Farr <farra at apache.org>
>     >Subject: [wplug] Signing up with Apache (WAS: Re: 45 Minutes with
>     High
>     > Schoolers)
>     >To: Wplug <wplug at wplug.org>
>     >Message-ID:
>     > <7a31ebb30602031243k502f7a66r2b044d40d716d189 at mail.gmail.com>
>     >Content-Type: text/plain; charset=ISO-8859-1
>     >
>     >Meant to send this out to everyone on the list...
>     >
>     >On 2/3/06, Zach <netrek at gmail.com> wrote:
>     > > Where do you go to sign up?
>     >
>     >   http://www.apache.org/foundation/how-it-works.html
>     >
>     >Apache, like most open source organizations, functions as a
>     >meritocracy.  Everyone is invited to participate.  Getting involved
>     >means subscribing to the mailing lists of a project you use,
>     answering
>     >questions, submitting patches and documentation.  You can get more
>     >ideas from my website:
>     >
>     >   http://www.jadetower.org/muses/archives/000009.html
>     >
>     >Once you've shown that you're serious about sticking around and
>     >helping out with a given project, you'll be offered commit access.
>     >And after really sticking around and getting involved in more
>     projects
>     >and more "behind the scenes" work like infrastructure maintenance,
>     >you'll find yourself nominated to be a member of Apache.  This
>     process
>     >of meritocracy isn't designed to be exclusive, but to ensure that
>     >those who are entrusted with guiding the organization really care
>     >about it.
>     >
>     >That's the traditional way of "signing up."
>     >
>     >Today, Apache actually adds more committers through the "Incubator"
>     >than anywhere else.  Existing open source or commercial projects
>     which
>     >want to join Apache (and for commercial projects that means becoming
>     >open source) have to go through an "incubation" process to ensure all
>     >the copyrights and other legal issues are handled properly.
>     >Incubation is also a time for project developers to learn to build a
>     >healthy open source community.  So in this way, developers become
>     part
>     >of Apache by taking their project through incubation.  The ASF if
>     >growing rapidly in this respect, as you can see from the list of
>     >incubating projects:
>     >
>     >   http://incubator.apache.org/projects/index.html
>     >
>     >
>     >Anyway, that's probably a longer answer than you expected, but I
>     >figure some others on the mailing list might also be interested.
>     >Moreover, the basic process I've described here works for most open
>     >source projects, be they formal organizations like Apache or just
>     some
>     >small singular project on SourceForge.  So pick one, or start you
>     own,
>     >and get involved!
>     >
>     >--
>     >   jaaron
>     >
>     >
>     >
>     >------------------------------
>     >
>     >_______________________________________________
>     >wplug mailing list
>     >wplug at wplug.org
>     >http://www.wplug.org/mailman/listinfo/wplug
>     >
>     >
>     >End of wplug Digest, Vol 24, Issue 4
>     >************************************
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug
>   



More information about the wplug mailing list