PHP classes stored outside of web root

[adam5532]

Hi, My websites have all the PHP classes stored in a folder above the web root. It seems that this breaks the ability of Laragon being able to switch easily between projects in Laragon. It seems curious that Laragon doesn't support this, as it is best practice for all PHP websites. Do I need to limit to one project configuration at a time, is there anything special that I need to do, will this cause any problems or loss of other features in Laragon, and will there be any issues with PHP accessing those files as they normally do on an Apache webserver?

[AWqxKAWERbXo]

I'm not sure if I understand the issue and why you store your PHP classes "outside of web root", but I think you can accomplish what you need like this.

1. accept the fact that www is the root folder for Apache auto-configured by Laragon - for localhost:80 and localhost:443.
2. use a folder inside this for a local domain - e.g. example.org will create a example.org Apache configuration file and also a example.org.testhosts entry so you can access http(s)://example.org.test instead of http(s)://localhost.
3. edit the auto-created configuration file to define your document root, usually public. It may look like this: Different document roots and local domains possible? #1487 (reply in thread)

So you have your document root defined with the PHP classes "outside" but still in your site. Which is btw best practice also on live servers in case of misconfiguration: Your webserver will not make credentials or code publicly available by accident.

[adam5532]

To clarify, each site is structured this way:
/includes
/public_html

So, you are saying that I can set it up this way:
/www

/www/site1.com
/www/site1.com/includes
/www/site1.com/public_html

/www/site2.com
/www/site2.com/includes
/www/site2.com/public_html

and be able to switch between them from the menu? Thanks.

[AWqxKAWERbXo]

Yes