Jump to content
The Uniform Server Community

Search the Community

Showing results for tags 'laravel'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Forum
    • Announcements
    • Developer
  • Support
    • Uniform Server - Windows
    • Plug-Ins Support
    • Programming & Web Design
    • Trackers
  • Community
    • Open Discussion
    • Off-Topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


SourceForge ID


Wiki ID


IRC Nickname

Found 1 result

  1. I have a freshly-installed Uniserver 13.2.2 Zero XIII. I have my virtualhosts configured as follows: <VirtualHost *:80> DocumentRoot ${US_ROOTF}/../../repo/test/public ServerName 55.dev ErrorLog "${US_ROOTF}/../../logs/55.error.log" CustomLog "${US_ROOTF}/../../logs/55.access.log" common <Location /> AllowOverride all Require all granted </Location> </VirtualHost>The example above is a Laravel 5.5 app freshly installed from the CLI. It works as expected. However, the identically configured app at /repo/lt-assets/public returns a 404 error for any route requested. It is also a Laravel 5.5 app, but it was added to the server by git pull from my Bitbucket repo. <VirtualHost *:80> DocumentRoot ${US_ROOTF}/../../repo/lt-assets/public ServerName lt-assets.dev ErrorLog "${US_ROOTF}/../../logs/lt-assets.error.log" CustomLog "${US_ROOTF}/../../logs/lt-assets.access.log" common <Location /> AllowOverride all Require all granted </Location> </VirtualHost>This app, however, is a Laravel 5.4 app. It was also setup by git pull from the repo. All routes in this app generate 404 errors. <VirtualHost *:80> DocumentRoot ${US_ROOTF}/../../repo/vnc-adminapp/public ServerName vnc.dev ErrorLog "${US_ROOTF}/../../logs/vnc-admin.error.log" CustomLog "${US_ROOTF}/../../logs/vnc-admin.access.log" common <Location /> AllowOverride all Require all granted </Location> </VirtualHost>Lastly, I have a WordPress app, also setup by git pull. It works as expected. <VirtualHost *:80> DocumentRoot ${US_ROOTF}/../../repo/lde/web ServerName lde.dev ErrorLog "${US_ROOTF}/../../logs/lde.error.log" CustomLog "${US_ROOTF}/../../logs/lde.access.log" common <Location /> AllowOverride all Require all granted </Location> </VirtualHost>So, it seems the only commonality to the non-working apps is that they satisfy both conditions: "is Laravel" && "pull from git repo". WP apps or Laravel installed form the CLI work just fine. All the apps work on Ubuntu 16.04/nginx/php7.1 dev and staging servers...which tells me it's not the underlying Laravel code per se. The contents of the public/.htaccess files on the Laravel apps are identical: <IfModule mod_rewrite.c> <IfModule mod_negotiation.c> Options -MultiViews </IfModule> RewriteEngine On # Redirect Trailing Slashes If Not A Folder... RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_URI} (.+)/$ RewriteRule ^ %1 [L,R=301] # Handle Front Controller... RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^ index.php [L] # Handle Authorization Header RewriteCond %{HTTP:Authorization} . RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] </IfModule>With the VirtualHost configs and .htaccess settings, I've done everything I can find by Googling this issue. All these repos worked under the same version of UniServer that wasi nstalled on my flash drive -- this newer setup is on an SSD external drive. I put this in the general area rather than the Apache area because I'm not completely sure it's an Apache issue. I destroyed the earlier setup on the flash drive too quickly, and don't know if the PHP module config is identical to what it was. I'm about ready to setup the SSD again, as I know there are some subtle differences. I don't think they are anything that affects UniServer -- only my command-line functionality....things like cmdr instead of bare conEmu, cygwin instead of the GNU windows CLI tools (such as nano). One thing I suppose could be pertinent (since git pull is one of the commonalities) is that I'm using the git for Windows that's packaged with cmdr (git version 2.11.0.windows.1) rather than a separate install of 2.14.1. Before I do that, where else can I turn?
×
×
  • Create New...