Hello, before I installed ISPconfig I had a normal webserver now the default part is / var / www / html Now I have installed ispconfig on it and if I assign the domain to a customer he gets the path / var / www / clients / client1 / web1 How can I change that now? / Var / www / clients / client1 / web1 How do I change that the web1 user also the main domain path is the website. Sorry for bad english.
in the control panel, go to system -> server config, select the relevant webserver, and then switch to the web tab. you'll see something like: Server Type: apache Website Basedir: /var/www website path: /var/www/clients/client[client_id]/web[website_id] website symlinks: /var/www/[website_domain]/:/var/www/clients/client[client_id]/[website_domain]/ just be aware that this will change the paths for all clients and sites on that server. also, i'm not sure if changing these will affect already existing sites, or if you'll need to run a resync, maybe someone else on here can confirm that. lee.
I highly recommend to not change any path settings there, you'll most likely break your server if you do so and the path /var/www/clients/client1/web1 is correct and there is also a symlink added with the domain name inside for easy shell navigation.
that's like asking why make running 'rm -rf' from / a command line option. or why does windows allow you to edit the system registry? or why allow a road car to reach 200mph+ it's there because there is a genuine usage case for the option. that doesn't mean that using it in the wrong way/situation isn't dangerous. it just means the option should only be used by people who know what they're doing, and why, and what the consequences are. people who don't know how to use it safely should just leave it the hell alone.
I think @till only gave high recommendation to use the default, since the question is about /var/www/clients/client1/web1, with actual reality it also symbolically linked to /var/www/client1.web.tld for easy navigation. There is also no clear indications of what he really wanted or why he wanted to change that to any others, rather than to the assigned domain, which is already there (symlinked) by default. By that I don't deny a genuine usage case but more details as to the reasons and the objectives should help us figuring out, rather than leaving us guessing with no clear indications, like I said earlier.
That's not a good comparison. It wasn't like "oh it can be in there, let's put it there!". And I was actually asking this because you wrote "i'm not sure if changing these will affect already existing sites" and this was unclear to me. Thus far it has not changed paths for existing sites, so you need to delete and re-enter site-data, and then change paths in databases and web-app config etc. to make it work. But I see no issues from then on, as long as someone involved in ispconfig (like til) does not decide to write "I highly recommend to not change any path settings there, you'll most likely break your server".
When taking a look at the initial post, you find this request: And this will break his system as the path should never contain the domain name as the domain name can be changed for a website, and this will then break many things like chroots and even many website software that stores paths. There is also a path that uses the domain name, but that is a symlink so you can navigate to the site easily on the shell, but the path for the site itself must be a fixed path. You can e.g. change /var/www to /var/sites without running into significant issues, except that some Apache modules that have /var/www compiled into their code might stop working, suexec is a candidate for this. But you should not change the structure of the path. If you can't live with that and don't want to adapt to the way the panel works that you just started using, then you better choose a different panel or write the config by hand.
