How to include subfolder in all requests?

@JussiMannisto To my understanding, I need one virtual host config file per domain. I have a static website at mydomain.com, and Laravel projects at mydomain.com/app1, mydomain.com/app2 and so on. The latter are aliases pointing to the Public subfolder of their respective apps. So I think DocumentRoot needs to be /var/www/mydomain.com. I understand your question though, as I have been looking for a way to set a DocumentRoot per alias. Didn't find any that work.

@Amplifiction In that case don't define a DocumentRoot at all. Use aliases with absolute paths:

Alias /app1 /var/www/mydomain.com/websites/app1/public
<Directory /var/www/mydomain.com/websites/app1/public>
	AllowOverride All
	Require all granted
</Directory>

As for APP_URL, I wouldn't try to add paths there. I'd just use a prefix for all routes:

Route::prefix('/app1')->group(function() {
	// App1 route definitions here.
});

In older versions of Laravel, you'd could modify RouteServiceProvider to add prefixes for all routes. I don't know how you'd do it in Laravel 11 since withRouting() only has an argument for an API prefix.

For storage paths, you can modify config/filesystems.php.

@JussiMannisto I put the DocumentRoot line in comments, which resulted in all sites 404'ing, including the one at mydomain.com. So I uncommented DocumentRoot.

Next, I tried the route prefix group. This resulted in a Laravel (not Apache) generated 404 page.

I took the homepage route out of that group, because on the homepage, I also added '/app1' to an img src, and I wanted to test whether at least that worked. The homepage loaded, but the image didn't, and to my surprise, when inspecting the img tag, the src attribute still started with /images instead of /app1/images.

This is a rabbit hole I have spent too much time in. Almost two weeks just to try to get my Laravel+React+Inertia project to work in a subdirectory of my main website. If you or anyone else can recommend a professional to teach me how to pull this off, that would be appreciated. As was your help, @JussiMannisto.

@Amplifiction

I put the DocumentRoot line in comments, which resulted in all sites 404'ing, including the one at mydomain.com. So I uncommented DocumentRoot.

You have to define an alias for each site, including the main site. You must define the root path last so that it doesn't catch requests going to the app*/ paths:

Alias "/app1" /var/www/mydomain.com/websites/app1/public
<Directory /var/www/mydomain.com/websites/app1/public>
	AllowOverride All
	Require all granted
</Directory>

Alias "/app2" /var/www/mydomain.com/websites/app2/public
...

Alias "/" /var/www/mydomain.com/

I'd put the secondary sites somewhere else than under /var/www/mydomain.com. You don't want to accidentally expose your .env files through the main site.

But here's the thing: you can't try one thing at a time and expect everything to start working. You have to configure everything correctly, including paths in the app like I mentioned before. That requires some understanding of how Apache and Laravel routing work.

If you or anyone else can recommend a professional to teach me how to pull this off, that would be appreciated. As was your help @JussiMannisto

Don't be childish. I'm a professional and I was trying to help, but I think I'm done now.

@JussiMannisto Apparently I phrased my reply poorly. First of all, I didn't mean to imply you're not a professional, and your help really has been appreciated.

Also, the aliases along with their root paths have been defined as you described, and the Laravel project is indeed in a directory other than /var/www/mydomain.com. But I still didn't get it to work. The fact that I'm using Inertia might have something to do with that. Controller functions are different than "standard" Laravel, for instance. I don't know right now.

Which makes this a complex project on a server that is constrained, at least to my standards. And that is why I think I need more comprehensive guidance. Which is, again, not to say I don't appreciate your insights. But like I said, I can't sink even more days into this project, not knowing when and if I'll get it to work. And so I'm going for one on one mentoring. Currently looking at Codementor.io, but no idea if that's a good fit. Which is why I'm open to recommendations.