Skip to main content
replaced http://serverfault.com/ with https://serverfault.com/
Source Link

It's generally known that it's a horrible idea to use these one-click LAMP stack installers for anything but local development. That said, with surprising regularity, we seem to get questions from people that are trying to use these in production. The vast majority of these users fall into the category where they should be migrated to SU, but often times that doesn't happen.

It would be quite nice if we could come to a concensus as to how to handle these questions.

My thoughts are thus:

  1. If it's obvious that the Q is better suited for SU, then migrate it there.
  2. If there's a chance that it's being used in a professional capacity, but they're trying to use it for production, then close it as a dupe of the canonical "Why *AMPP shouldn't be used in production" question"Why *AMPP shouldn't be used in production" question.
  3. If it doesn't match 1 or 2, then answer the question as appropriate.

It's generally known that it's a horrible idea to use these one-click LAMP stack installers for anything but local development. That said, with surprising regularity, we seem to get questions from people that are trying to use these in production. The vast majority of these users fall into the category where they should be migrated to SU, but often times that doesn't happen.

It would be quite nice if we could come to a concensus as to how to handle these questions.

My thoughts are thus:

  1. If it's obvious that the Q is better suited for SU, then migrate it there.
  2. If there's a chance that it's being used in a professional capacity, but they're trying to use it for production, then close it as a dupe of the canonical "Why *AMPP shouldn't be used in production" question.
  3. If it doesn't match 1 or 2, then answer the question as appropriate.

It's generally known that it's a horrible idea to use these one-click LAMP stack installers for anything but local development. That said, with surprising regularity, we seem to get questions from people that are trying to use these in production. The vast majority of these users fall into the category where they should be migrated to SU, but often times that doesn't happen.

It would be quite nice if we could come to a concensus as to how to handle these questions.

My thoughts are thus:

  1. If it's obvious that the Q is better suited for SU, then migrate it there.
  2. If there's a chance that it's being used in a professional capacity, but they're trying to use it for production, then close it as a dupe of the canonical "Why *AMPP shouldn't be used in production" question.
  3. If it doesn't match 1 or 2, then answer the question as appropriate.
Added a link to the canonical question to mark as a dupe, as found in http://meta.serverfault.com/questions/1986/what-are-the-canonical-answers-weve-discovered-over-the-years
Source Link
yagmoth555 Mod
  • 17.5k
  • 15
  • 23

It's generally known that it's a horrible idea to use these one-click LAMP stack installers for anything but local development. That said, with surprising regularity, we seem to get questions from people that are trying to use these in production. The vast majority of these users fall into the category where they should be migrated to SU, but often times that doesn't happen.

It would be quite nice if we could come to a concensus as to how to handle these questions.

My thoughts are thus:

  1. If it's obvious that the Q is better suited for SU, then migrate it there.
  2. If there's a chance that it's being used in a professional capacity, but they're trying to use it for production, then close it as a dupe of a yet-to-be-createdthe canonical "Why *AMPP shouldn't be used in production" question"Why *AMPP shouldn't be used in production" question.
  3. If it doesn't match 1 or 2, then answer the question as appropriate.

It's generally known that it's a horrible idea to use these one-click LAMP stack installers for anything but local development. That said, with surprising regularity, we seem to get questions from people that are trying to use these in production. The vast majority of these users fall into the category where they should be migrated to SU, but often times that doesn't happen.

It would be quite nice if we could come to a concensus as to how to handle these questions.

My thoughts are thus:

  1. If it's obvious that the Q is better suited for SU, then migrate it there.
  2. If there's a chance that it's being used in a professional capacity, but they're trying to use it for production, then close it as a dupe of a yet-to-be-created canonical "Why *AMPP shouldn't be used in production" question.
  3. If it doesn't match 1 or 2, then answer the question as appropriate.

It's generally known that it's a horrible idea to use these one-click LAMP stack installers for anything but local development. That said, with surprising regularity, we seem to get questions from people that are trying to use these in production. The vast majority of these users fall into the category where they should be migrated to SU, but often times that doesn't happen.

It would be quite nice if we could come to a concensus as to how to handle these questions.

My thoughts are thus:

  1. If it's obvious that the Q is better suited for SU, then migrate it there.
  2. If there's a chance that it's being used in a professional capacity, but they're trying to use it for production, then close it as a dupe of the canonical "Why *AMPP shouldn't be used in production" question.
  3. If it doesn't match 1 or 2, then answer the question as appropriate.
edited tags
Link
Michael Hampton Mod
  • 251k
  • 1
  • 55
  • 126
edited tags
Link
John Gardeniers
  • 27.7k
  • 23
  • 38
Loading
canonical tag
Link
gWaldo
  • 12k
  • 17
  • 12
Loading
Tweeted twitter.com/#!/ServerFault/status/108063018297987072
deleted 10 characters in body
Source Link
EEAA
  • 110.2k
  • 28
  • 45
Loading
Source Link
EEAA
  • 110.2k
  • 28
  • 45
Loading