Vagrant Laravel 8.x App deployment to VPS LAMP server
The app is for only One person the Admin, and the server has /public_html folder
but Laravel has /public folder
for this case required /public_html folder being /public of Laravel??? other files one level up???
Also, the Database,... etc gets environment vars from file .env even in Production??? having .env -- can Not read by hackers or online criminals? the "." in .env do file hidden and never accessible????
If you are using an Virtual Machine, you can able to edit the Apache Site Configuration files in /etc/apache2/sites-available/ directory to point to the public folder of Laravel application.
If you were using the managed VPS provided by various Hosting Providers, you can raise a Support Ticket for them to do do OR you can do it yourself.
basically --- if you have 2 PHP frameworks in 2 subdomains
CakePHP from before admin.yyyy.com point at public_html/admin
and intent to add another framework Laravel admin2.yyyy.com point at public_html/admin2
I have to have Laravel public/ folder as is public and other folders up the tree [inaccessible] --- or Not really matters, I can put all Laravel folders in public_html/admin2...???
.env <<< this file contains access data and in Production like in testing/Vagrant/Homestead???
Also, I have to put in the Non-accessible folder[in production]?