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
This skeleton is bust, causes Packager to Fail #13
Comments
What's the error? |
Hi, So at time of writing I perform a clean setup with "Laravel New Project" which sets up a new laravel 8.0.3 project then I pull in your package with "composer require jeroen-g/laravel-packager" once its installed I attempt to perform the "php artisan packager:new ACME ABC" At the first step I see the following
Looking in the packages directory I can see the ACME/ABC folder with what appears to be the skeleton source but it was never renamed etc. This is a clean project, came here from reference on Laracasts and my experience has had no success with this package or skeleton |
Thank you, now I can look into it! |
On the latest release I was not able to reproduce it. Please try again! |
I am having laravel 8.20.1 installed with jeroen-g/laravel-packager v2.6 all this running on php 7.4.10 (on Homestead) When I run php artisan packager:new foo/bar I see it creates the boilerplate packages/foo/bar but the files are not renamed as required. Further investigation revealed that this code in
Is causing the issue, the thing is So I think problem is not this Can you please check? Update:Still further when I investigate, I figured there is no files in src folder when the RecursiveDirectoryIterator instance is created when it is running. Instead of |
That is very precise information and something I can work with, thank you. If you happen to find the solution, don't hesitate to open a PR! |
Jeroen-G/laravel-packager#101 @Jeroen-G I'm facing it again, going to try and get to the root this time. |
Hey there back again, So I ran into this issue again and I was using a VM in this case homestead. Looking at other user feedback and @bilogic link to a similar ticket this is actually a timing issue so in my case I just went into the and just put a delay between the retrieval of the archive/extraction and the rename step This could be a mix of several factors, system extract performance and file system speed on mount etc and the step may just be one step to fast and execute before the files are there to be renamed. so I just added a sleep(2); to just give a bit of a delay I will add that I tried this on the system directly and it worked no issue but the virtual environment was a permanent issue. below is the adjustment I made just to get this working for me. $manifest = (file_exists($this->conveyor->packagePath().'/rewriteRules.php')) ? $this->conveyor->packagePath().'/rewriteRules.php' : null;
sleep(2);
$this->conveyor->renameFiles($manifest); |
Title Says it all and it effectively breaks the Packager
The text was updated successfully, but these errors were encountered: