LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   Versions and tips for webserver with apache (https://www.linuxquestions.org/questions/debian-26/versions-and-tips-for-webserver-with-apache-558976/)

mouse_x 06-04-2007 03:21 AM

Versions and tips for webserver with apache
 
Hi

I'm setting up a webserver that's going to have apache.
I'm a little new to this, but I have successfully set up an debian-computer before, although with Sarge Stable. I guess it's best to use a newer version, and I've been adviced to use an unstable version (earlier this year). Now I see that the stable version isn't that old, should I use it? (etch)


As for Apache, after searching I found out there were three versions. Is there any reasons not to use the newest (2.2.x) ?


Sorry if some of this has been covered on the forum before, I've seached a little, but cant find excactly what I want to know..

MoMule 06-04-2007 11:15 AM

I wont be much help here, but can tell you that I am always using the newest versions as they come out - with no problems.

Sorry,

Deion "Mule" Christopher

mouse_x 06-05-2007 02:40 AM

Thanks :) I'll probably go for the newest stable debian, and newest version of all software..

jlinkels 06-05-2007 06:20 AM

It depends on you application. If this is going to be a production server, use Stable (Etch now). Stable doesn't get changed anymore, and I expect it to be there for 18 or 24 months. You won't have the latest and the greatest, but it runs, and it'll keep runnning until you switch it off.

On the other hand, if this is a server to study and play around, use 'Testing', and continue to follow the repository contents. You'll be more up-to-date. However, it might be one day that you install a new package which needs intervention to get it running, or breaks your system and you'll have to fix it. Not that testing provides unstable packages, it is more that some config file becomes incompatible or so.

Of course if you install 'Testing' now and leave it there, you have a fine running system which is stable as well. But be careful when installing additional packages in the future, they might depend on and install upgrades of youexisting programs.

jlinkels

mouse_x 06-06-2007 02:27 AM

Thanks :) I've now installed Etch, and I'm currently setting it up..

Will soon install apache2, hopefully it will all work out :)
Might have some more questions later

ErrorBound 06-06-2007 06:12 AM

The only reason you would use apache (1.3.x) instead of apache2 (2.2.x) is if you have some binary modules that are not available for apache2.

I'm assuming you don't have any of these, so apache2 should be the better choice.

mouse_x 06-07-2007 05:31 AM

Quote:

Originally Posted by ErrorBound
The only reason you would use apache (1.3.x) instead of apache2 (2.2.x) is if you have some binary modules that are not available for apache2.

Such as mod_put.so? I can't find any way of using PUT in apache2, so I'm probably going to install apache1.3 also, and install mod_put there.. (see also other thread)

There should be no problems having both of them installed at the same time?

mouse_x 06-07-2007 07:29 AM

For others with the same problem:

Installed apache1.3, loaded mod_put.so and set "EnablePut On" for my folders.
Seems to be working now.

Took me about half an hour, just duplicating the setup from another computer.
Been trying for many hours on apache2, and nothing worked.
Got a tip that the module for PUT is mod_dav.so, but haven't tried it myself.


All times are GMT -5. The time now is 08:51 PM.