matthewbdaly / laravel-package-boilerplate

Boilerplate for Laravel packages
MIT License
16 stars 3 forks source link

PHP Warning: mkdir(): File exists in Command line code on line 1 #1

Closed ptejada closed 6 years ago

ptejada commented 6 years ago

Last output after running the suggested command composer create-project matthewbdaly/laravel-package-boilerplate {project-name}

Writing lock file
Generating optimized autoload files
> php -r "mkdir('bootstrap');"
> php -r "mkdir('bootstrap'.DIRECTORY_SEPARATOR.'cache');"
> php -r "mkdir('src'.DIRECTORY_SEPARATOR.'Http');"
> php -r "mkdir('src'.DIRECTORY_SEPARATOR.'Http'.DIRECTORY_SEPARATOR.'Controllers');"
> php -r "mkdir('src'.DIRECTORY_SEPARATOR.'Http'.DIRECTORY_SEPARATOR.'Middleware');"
> php -r "mkdir('src'.DIRECTORY_SEPARATOR.'database'.DIRECTORY_SEPARATOR.'factories');"
PHP Warning:  mkdir(): File exists in Command line code on line 1

Warning: mkdir(): File exists in Command line code on line 1
> php -r "mkdir('src'.DIRECTORY_SEPARATOR.'database'.DIRECTORY_SEPARATOR.'migrations');"
PHP Warning:  mkdir(): File exists in Command line code on line 1

Warning: mkdir(): File exists in Command line code on line 1
> php -r "mkdir('routes');"
matthewbdaly commented 6 years ago

Does the command complete successfully otherwise?

I'll have a look over the weekend and see if I can resolve this

ptejada commented 6 years ago

The command completes.

On Fri, Sep 7, 2018, 1:57 AM Matthew Daly notifications@github.com wrote:

Does the command complete successfully otherwise?

I'll have a look over the weekend and see if I can resolve this

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/matthewbdaly/laravel-package-boilerplate/issues/1#issuecomment-419331579, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPd3VHAZmIYf8nwV1mtz5UOlyEdx2Jsks5uYgrGgaJpZM4WeKFy .

--

Sincerely,

Pablo Tejada

From Mobile

matthewbdaly commented 6 years ago

OK, I've tagged a new version which should resolve this issue.

I've also updated it to use the Orchestra Testbench packages for Laravel 5.6 - I would use 5.7, but for the fact that the package that supports Browserkit in 5.7 isn't ready yet, but if you need to test against 5.7 and don't need Browserkit support, you can just drop orchestra/testbench-browser-kit in the created composer.json and change the version of orchestra/testbench to 3.7. I'll keep an eye on it here and do another release once that's available.

I was able to reproduce the issue myself, and running the new version just now resolved the issue. Can you confirm it's now working as expected for you?

ptejada commented 6 years ago

Closing this since you were able to reproduce and fix the issue.