Multiple Laravel Projects on the same Server

I'm not sure that it's a good idea to share the vendor folder, because if one website is down for some unknown problem with the dependencies, all websites will be down.

Can you post your composer.json? It's interesting what dependencies can eat 3 Gb.

I also wouldn't share vendor folder among projects, you definitely will face huge problems with updates even if you force your 7 sites to use the same dependencies. Better buy more space on your VPS.

It sounds like you've possibly outgrown your VPS tbh and would be better off with something from the likes of Hetzner or DigitalOcean where you'd have some more freedom.

I'd say there's an issue with your dependencies too. I currently have a local copy of our cyber security application on this laptop and it's a fair sized app that started as a Laravel 7 project and now upgraded to Laravel 11, and the vendor dir is 206MB. I'd start by looking at what's causing such a huge amount of storage usage in there.

Check your composer.json file for the following entry in the config {} section, if it's not there, I'd suggest adding it:

"preferred-install": "dist",

This will preferably only pull package dependencies from the required section and ignore the required-dev section, which recursively, through the dependency chain, could result in a substantial difference.

Definitely also follow @vincent15000 's advice and don't share dependencies.. you could find that catastrophic later down the road with version mismatches.

Cheers..

Ian

Your vendor folder should be nothing like that size.

A recent Laravel 12 project with a couple of extra packages is only 112Mb.

I would delete the vendor folder and re-install with composer install

I just did an analysis and my Sebastian folder is 1.2gb, PHP Unit is 600mb and Laravel is nearly 500mb, on my new computer where everything works right and is shiny and new those folders are <30mb combined heh. So I guess it probably is that zip warning

@nancyjames Doesn’t sound like a very good VPS if they’re then imposing such disk space limits. But, as others have said, a 1 GB+ vendor directory is massive. I’ve just calculated the vendor folder size for one of my more mature projects and it’s only 171 MB.

In regard to the subject of your question, what are the seven sites on this VPS? Are they related in some way? Are they sites that can be rolled up and served from a single application using a multi-tenancy approach, rather than re-building seven sites as seven Laravel applications?

A couple years ago I had 4 sites on the same server, but just doing some testing.

You place main laravel one level higher than the web folders.

Nginx conf I had

       location /laravel859/ {
            root   www;
            index  index.php index.html index.htm;
            try_files $uri $uri/ /laravel859/index.php?$args;

        }


        location /mini4/ {
            root   www;
            index  index.php index.html index.htm;
            try_files $uri $uri/ /mini4/index.php?$args;

        }


        location /tjhs/ {
            root   www;
            index  index.php index.html index.htm;
            try_files $uri $uri/ /tjhs/index.php?$args;

        }

        location /cake40/ {
            root   www;
            index  index.php index.html index.htm;
            try_files $uri $uri/ /cake40/index.php?$args;

        }

laravel859 was public inside www, another folder laravel859up housed main laravel files. one level higher than www.

However for a real production site and as others has said, I would not recommend doing this.