Forum Moderators: phranque
Then, the folder that was described as a root of my site already had some subfolders and files, like cgi-bin folder and something in regards of site manager, users and so on.
The support guy has described it would be best for me to leave it as it is, plus some of those I would not be able to delete anyway.
He confirmed there would be a possibility of creating a new folder for site root, but then I would lose some capabilities (like some apps).
My main reason for wanting to remove those folders was to actually protect them. My logics tell me I want CGI folder above root of my site. Then I use a local path from my Perl script(s).
Although “like a real server” (VPS), my hosting company takes care of the software and updates, so I would say it is like “managed server”.
All this has prompted me to seek for what you would do with such brand new account?
What is a must or absolute NO NO when you get bit more control then with regular shared hosting.
What do you check first? What do you change first?
I am keen to start learning.
Thanks
Rather than take a chance on interrupting the functionality of your website (s), it's a good idea to leave those host implemented directories alone.
Exceptions might be in directories that are created later by yourself through the CP options.
