Quote:
|
Originally Posted by falko
That's not true. The error is displayed.
|
The ISPConfig error is displayed, but I have no idea of what steps it took to get there so that I can troubleshoot and find the root problem.
Quote:
|
Originally Posted by falko
The reason why you have to start over is that the installer modifies quite a lot files in the install_ispconfig directory. So if the installation fails you can't use the same install_ispconfig directory again because it simply won't work due to the changes the previous installation made. That's why the install_ispconfig directory is deleted if the installation failed.
|
Regardless of what reasons you have, even if they're good ones, it's
never OK to delete a user's files without at least warning first that you're going to. The first time I ran that script, I had copied other files into that directory so I could use them for reference and made some notes about the install I was running. They were all wiped out and I had to start over.
Quote:
|
Originally Posted by falko
If you rename it, the installation will most likely fail...
|
No, it worked fine actually... why would it fail?
Quote:
|
Originally Posted by falko
BTW, there's a reason why we wrote all those "Perfect Setup" tutorials on HowtoForge. If you follow them to the letter, you won't have any problems installing ISPConfig. 
|
What about people who are using an OS (such as CentOS in my case) that doesn't happen to have a "Perfect Setup" listing? Or someone using (such as me) who is renting a VPS that already had the OS installed? Or someone who for one reason or another wants to modify their OS in some way?
The Perfect Setup guides are great and have lots of good info in them, but not everyone can or will follow them. And I realize you probably have had lots of people screw up their installs by trying to rerun it and having stuff break.
But for someone who has a clue to what they're doing, it's very frustrating to sit and wait for Apache to compile half a dozen times while I try to get things running. And frankly, I want to see what the script is doing at each step of the way, because a hosting control panel such as this is really in control of the entire OS and I want to know what's going on.
So while I can appreciate why your script takes the safe approach and deletes everything to start over, it would be really nice if it warned the user first and ask if this is OK, and had an easy way to turn it off or even skip certain steps like the Apache compile (some sort of "expert mode") for people who want to try several different approaches before finally deciding how they want to proceed.
Recent comments
21 hours 57 min ago
22 hours 2 min ago
1 day 3 hours ago
1 day 9 hours ago
1 day 10 hours ago
1 day 11 hours ago
1 day 16 hours ago
1 day 22 hours ago
2 days 2 hours ago
2 days 4 hours ago