VHOST Folder

Discussion in 'Installation/Configuration' started by mbsouth, Dec 10, 2010.

  1. mbsouth

    mbsouth Member

    Hi ISPConfig freaks!

    Is there a way (or config setting) to rename the web folder in
    /var/www/clients/client[id]/web[id]/web to www or docroot permanently?

    What I need is:
  2. falko

    falko Super Moderator ISPConfig Developer

    I don't think so, but maybe you can create a symlink pointing from www or docroot to web.
  3. mbsouth

    mbsouth Member

    Hi Falko, thanks for your reply!
    I tried symlinks before I post the thread above. Symlinks works as expected but symlinks are more of a patchwork than a solution. To find a better once, I searched the source code to find the definition of the paths inside the document_root.

    Unfortunately the result was disappointing:
    - there are no common config(file) for paths definition inside the document_root
    - the paths are hard coded in multiple files - multiple times

    this makes ispconfig not compatible to migrate our existing environments yet:
    - no standard for directories within web root (error and stats should be placed outside the web root [in this case: /web])
    - our web root is /www (possible solutions will be symlinks but this approach ends in hundreds of support requests)

    In our tests ispconfig was the best (free) hosting panel solution at all and
    I hope, custom-defined paths are possible in upcomming versions.

  4. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig has a standard, and this standard is that the name for the error folder is error and that its inside the web folder and the stats folder is inside the web folder and named stats. We use this standard since ispconfig 2. It might be that you used a different standrad in your old enviroment, but this does not mean that ispconfig hs no standard folders.

    In ispconfig and several other controlpanels, the standard name for thsi folder is web.
    Last edited: Dec 13, 2010
  5. mbsouth

    mbsouth Member

    Hello Till, thanks for your reply!

    I have made myself misunderstood, sorry about that.
    !!! I did not want to make ISPConfig down - quite the reverse - ispconfig is the best (free) hosting panel solution at all !!!
    What I meant was that we do not impose standards to our customers. In this case each customer can create their own folder trees without restrictions (inside the web root). But predefined folders are restrictions (my opinion). In some projects error or stats are used by our customers. I have to migrate more than 300 vhost from different server to a new multi-server-environment!
    I´ll do this once[!], straight[!] and flawless! I think ispconfig could help me a lot!

    What makes the use of ispconfig attractive over other control panels? The same standards(?), same restrictions(?) or what?

    Things like customized settings, stability, diversity... makes ispconfig attractive and it´s not necessary to compare it with other control panels - ispconfig "shows something a clean pair of heels" (I think this is like - etwas weit zurück/hinter sich lassen?).

    Btw - advantages to define the paths in a common config (like /usr/local/ispconfig/server/lib/config.inc.php) are clear code, simple to change, adjustment, debugg and customizable and not realy hard to do.

    Thank you for your attention
    just my 2 cent
    Last edited: Dec 13, 2010

Share This Page