Timeline for What to do with XAMPP/MAMP/WAMP questions
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 19, 2013 at 19:49 | comment | added | Chris | I work for nonprofits, and most times you have what you have. I've made several long-term, medium-traffic intranet systems on WAMP, by necessity. Best practice is great, and I can talk all day about the virtues of hosting on a *nix platform, but at the end of the day life often falls short of best practice. No lives will be lost if I deploy on WAMP. | |
| Sep 14, 2012 at 2:55 | comment | added | HopelessN00b | +1 for not wanting to be too restrictive on what's "professional" in someone's unknown production environment. As awful an idea as it is, when project or task constraints are "whatever equipment you can beg borrow or steal, $0, and completed by yesterday," the proper professional behavior can be shoving a MAMP stack into production, as dirty as I feel saying so. And in shops with shoestring budgets for hardware and software, I've had great results shoving a LAMP stack onto an old desktop and reminding the boss/client it's an awful idea that will hurt later, but you insisted, so, there it is. | |
| Aug 30, 2011 at 5:47 | comment | added | womble Mod | Aha, I think I misunderstood your stance. | |
| Aug 29, 2011 at 22:22 | comment | added | John Gardeniers | @womble, yes it would and that would be constructive. Simply closing the question or sending it to SU wouldn't be at all helpful. | |
| Aug 29, 2011 at 20:11 | comment | added | womble Mod |
Wouldn't it be best to point that hypothetical new admin at something that described exactly why *AMP is a bad idea, and what a better option is, so that they can fix the problem before they become deeply embedded in it's tentacles?
|
|
| Aug 28, 2011 at 22:37 | history | answered | John Gardeniers | CC BY-SA 3.0 |