Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option in starter.ini to generate a phpinfo.php to /public #168

Closed
apolopena opened this issue Dec 21, 2021 · 3 comments
Closed

Add an option in starter.ini to generate a phpinfo.php to /public #168

apolopena opened this issue Dec 21, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main

Comments

@apolopena
Copy link
Owner

apolopena commented Dec 21, 2021

Problem this feature will solve

A phpinfo.php page must be created manually in public/ when debugging PHP extensions and PHP versions and PHP packages.

<?php phpinfo( ); ?>

Background

A phpinfo page for a php project increases the DevX.

Proposed Solution

Add a name value pair in the [PHP] section of starter.ini. The default value should be 1 (yes):
generate_phpinfo=1
If a value is set to anything other than 1 then do not generate a phpinfo.php file in public/

Constraints and Assumptions

<! -- Any constraints and/or assumption relevant for the development and use of this feature? -->

Alternatives or Workarounds

Add a phpinfo.php page to /public manually each time you create a workspace for a project.

Additional context

Add any other context or screenshots about the feature request here.

@apolopena apolopena added the enhancement New feature or request label Dec 21, 2021
@apolopena apolopena self-assigned this Jan 22, 2022
@apolopena apolopena added this to the v1.4 release 🚀 milestone Jan 22, 2022
@apolopena apolopena added the in-development Bug or feature is currently being worked on label Jan 22, 2022
apolopena added a commit that referenced this issue Jan 22, 2022
@apolopena apolopena added in-dev-qa and removed in-development Bug or feature is currently being worked on labels Jan 22, 2022
apolopena added a commit that referenced this issue Jan 22, 2022
apolopena added a commit that referenced this issue Jan 22, 2022
apolopena added a commit that referenced this issue Jan 22, 2022
apolopena added a commit that referenced this issue Jan 22, 2022
@apolopena apolopena added passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main and removed in-dev-qa labels Jan 22, 2022
@strausmann
Copy link
Contributor

image

@apolopena
Copy link
Owner Author

Yeah I added a space to the log message to try to fix that. Sometimes the spinner chops off a character.

@strausmann
Copy link
Contributor

ah ok, known issue :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main
Projects
None yet
Development

No branches or pull requests

2 participants