Adding existing Laravel 5.3 project


  • | 233 points

    Managed to use git and clone project into the root Laragon directory. Everything appears to be working fine, except for the fact that Laragon does not seem to be running my app; I get this view when going to {name}.dev of the app in browser: https://puu.sh/vXH2p/26f3af16ea.png

    Any idea why this may be happening? Wondering if I didn't miss a command or something of that nature. This seems to be something you would receive if you forgot to run 'homestead up' or 'php artisan serve' in equivalent OSX, Linux setups.

    I should mention I have another project running at the same time -- it was installed via the Laragon installer, and is loading correctly however.


  • administrators
    | 64704 points

    @Marek-Dobrenko : I made a tutorial for working with Laravel projects on github here:
    https://forum.laragon.org/topic/175/tutorial-how-to-work-with-laravel-projects-on-github

    I believe you missed some steps, such as compose install, ...


  • | 233 points

    Oddly enough, I performed all those steps. The thing I found is that if I run php artisan serve, it will actually serve a working copy of my project (at localhost:8000). It seems to me that the server simply isn't running my project. Any ideas? I have restarted Apache and nothing.


  • | 233 points

    Figured it out -- Laragon set up the apache files so that they pointed to laravel/ rather than the laravel/public directory.


  • administrators
    | 64704 points

    @Marek-Dobrenko : Nice catch!
    Is there a .htaccess file on your public folder?
    I wonder it was excluded from .gitigrone that caused the issue.
    By default, Laragon will check if there is a public.htaccess first to point to laravel/public dir.


Log in to reply
 

Looks like your connection to Laragon was lost, please wait while we try to reconnect.