test-laravel | Test Laravel repository for End-to-End testing of Deployer | Testing library
kandi X-RAY | test-laravel Summary
kandi X-RAY | test-laravel Summary
Test Laravel repository for End-to-End testing of Deployer
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of test-laravel
test-laravel Key Features
test-laravel Examples and Code Snippets
Community Discussions
Trending Discussions on test-laravel
QUESTION
I figured this out myself while I was revising my question, but I'm going to post my original question anyway with the solution in case it helps anyone else.
The solution has nothing to do with symbolic links or Deployer, but I'm going to leave my question as is in case someone came to the same problem in a similar way.
I'm trying to set up a Laravel 5.8 deployment using Deployer on a CentOS 7 server.
The deployment is successful. The storage
folder is set as a shared directory in my deploy.php
file, so what it does it sets up the storage
folder as a persistent shared folder between releases. It does this by creating a symbolic link to a shared storage
folder for the releases.
There is a folder for the current release at /var/www/test-laravel/current
, which is actually a symbolic link to the folder with the most recent release (in this case /var/www/test-laravel/releases/18
). Inside that folder the storage
folder is actually a symbolic link to /var/www/test-laravel/shared/storage
.
I was getting the following error,
After trying a few variations of permissions/owners/groups, out of frustration I manually ran chmod -R 777
and chown -R apache.apache
on not just the original storage folder but on all of the symlink folders as well.
This hasn't changed anything at all. I'm still getting the same error.
I don't think this should make a difference, but just for good measure I've run php artisan cache:clear
, php artisan view:clear
and php artisan config:clear
.
ANSWER
Answered 2020-Jun-25 at 03:00It turns out the problem was SELinux.
I disabled SELinux, (setenforce 0
) and after that it worked just fine. However, I know that disabling SELinux is not preferable, so I re-enabled SELinux (setenforce 1
) and instead, I tried changing the label on the storage folder like so,
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install test-laravel
PHP requires the Visual C runtime (CRT). The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable for all these PHP versions, see visualstudio.microsoft.com. You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. The CRT installer supports the /quiet and /norestart command-line switches, so you can also script it.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page