thedevdojo/voyager

Artisan Commands Fail: Add ability to configure PHP Path in ENV file.

Open

#2,201 opened on Nov 9, 2017

View on GitHub
 (6 comments) (0 reactions) (0 assignees)PHP (11,817 stars) (2,652 forks)batch import
Technical Debthelp wantedopen for suggestionspossible bug

Description

  • Laravel Version: 5.5.*
  • Voyager Version: ^1.0
  • PHP Version: 7.1.*
  • Database Driver & Version: n/a

Description:

Voyager needs the ability to define the php path in the env file. Currently I can't use any of the artisan based features because both my local and remote environments use multiple versions of php. For example if I want to use php 7.1, I must specify a handler which uses a binary named php71.

If you could simply add the ability to define the php path in the env file that would help developers in my position. Thank you!

Steps To Reproduce:

Install on a server where php7 binary is not in expect path or uses unexpected file name.

Contributor guide

Tech stack
phplaravel
Domain
backenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic PHP knowledgeLaravel basicsunderstanding of .env files
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests adding a configuration option for the PHP binary path in the .env file. First, locate where Voyager executes Artisan commands internally (e.g., in VoyagerServiceProvider or related classes). Look for hardcoded 'php' references. Then, determine how to inject a config value (e.g., from config/voyager.php) that can be overridden via .env. The change likely involves modifying the command execution logic to use the configured path instead of the default 'php' binary.