views:

1331

answers:

7

See title. Is this a bad idea?

So everyone knows, and I don't see how this mattered, we've paid for a windows dedicated box and we have existing IIS apps. We just wanted to use a PHP based CMS which installs easier on apache (since it has some dependencies). So, as the title indicated, windows, apache, php, and mysql are requirements.

Additionally, I'm talking specifically of the WampServer flavor of WAMP.

A: 

Why not just use LAMP? PHP code is portable. I used WAMP for development, LAMP for production.

WAMP would probably work for production, but why not just use LAMP?

A: 

LAMP is more stable, but i have wamp running intranet-sites succesfully in two organisations with over a 1000 users.

Overbeeke
In what ways is WampServer unstable?
TheDeeno
A: 

WampServer themselves says they are not appropriate for production, only for development. Security issues, load balancing, etc., are definitely part of it... plus, deploying Apache on Windows is just a nightmare.

Use LAMP. Alternatively, use IIS... if you're going to deploy a Windows production server (don't), use IIS.

Steve Paulo
Where do they say that?
apathetic
Apparently I stand corrected... I thought the installation process included a disclaimer to that effect. Apparently I am confusing WampServer2 with some other WAMP package (EasyPHP perhaps?)
Steve Paulo
I found that deploying Apache on Windows was actually straightforward and very easy.
Owen
Thanks for the clarification guys.
TheDeeno
A: 

I don't see why not, but why use Apache on Windows when you can quite easily install PHP on IIS?

apathetic
A: 

I love how the only guy who answered the actual question by paying attention to the fact that the OP was asking about the all in one product that is WampServer has a -1 rating. To reiterate what he said though, yes it would be a bad idea to use it in a production environment.

Tons0fun
+1  A: 

If you're not going onto the internet, there isn't any reason really not to. Of course you'd have to look at all the normal caveats - backups etc.

Instead of using an already made one, why not try to do your own? It would be a good learning experience and really they aren't that hard to get working together.

Tubs
Did it manually. Wasn't too bad. Took me about 3.5 hours and I'm much more comfortable with each component and their interactivity now.
TheDeeno
A: 

You know, it would be nice if at least 1 person came on here to provide proof as to why WAMP shouldn't be used for production use...

But I guess that's too much to ask for since it would take a person actually knowledgeable about a given issue.

Wolf_22