Skip to content

Conversation

@gmsantos
Copy link
Contributor

In my work I must rely only with PHP built-in server in my develop machine to comply with IT policies, I can't use Apache, Ngnix, VMs or Vagrant.

While working with multiple projects at time, I found boring typing over and over a different host/port (php artisan serve --host xpto --port 8088), so override php artisan serve defaults into a .env file sounded a good idea for me.

I don't know if this is the best approach, maybe extract this to a config file.

In my work I must rely only with PHP built-in server in my develop machine to comply with IT policies, I can't use Apache or Vagrant.

While working with multiple projects at time, I found boring typing over and over a different host/port (`php artisan serve --host xpto --port 8088`), so override `php artisan serve` defaults into a `.env` file sounded a good idea for me.

I don't know if this is the best approach, maybe extract to a config file.
@GrahamCampbell
Copy link
Collaborator

This adds coupling between the command and the environment system. This is not allowed. If we were to do this, we should inject the defaults into the command instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants