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

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like thisthis is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X". I expect those cases to be somewhat rare though.

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like this is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X". I expect those cases to be somewhat rare though.

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like this is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X". I expect those cases to be somewhat rare though.

added 50 characters in body
Source Link
Sven Mod
  • 100.3k
  • 2
  • 40
  • 70

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like this is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X". I expect those cases to be somewhat rare though.

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like this is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X"

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like this is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X". I expect those cases to be somewhat rare though.

Source Link
Sven Mod
  • 100.3k
  • 2
  • 40
  • 70

I agree that everything that is really related to a control panel should be closed, for the reasons stated over and over again. However, I dont feel that we should "autoclose" and use the mention of such a panel as a trigger for this, even if the actual problem is clearly unrelated to the presence of the panel.

Something like this is an example of what I wouldn't want to close, as the Apache/DirectAdmin side of the system is unrelated to the core of the question, which is "how do I manually configure nginx to do X"