@fluxxus Put the “old” site in the public directory of your Laravel application. Set up your web server to first check for a file, and only if a file does not exist, to pass the request through Laravel.
The .htaccess file that ships with Laravel does this already:
# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]
That checks the request does not match a directory or file, before passing the request to Laravel’s index.php front controller. You’ll be able to do something similar with nginx too if you use that instead.
If you already have an index.php file for your existing website, then you could rename Laravel’s to say, index-laravel.php and then update the .htaccess / nginx.conf rule:
# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index-laravel.php [L]
Once you do have Laravel installed and your old website working together in tandem, I would make an effort to start migrating pages to Laravel. You can do them one at a time to ensure that the output is same from the “old” site to the Laravel-served, Blade version.
