-
Notifications
You must be signed in to change notification settings - Fork 43
Clone needs to be reviewed #22
Comments
I cannot reproduce this. Was this using the most recent version? Is there any other steps we can see to reproduce? |
I was finally able to reproduce this, fresh build, fresh new environment, then the first time I tried to clone I got this: $ ./virtphp-jk/bin/virtphp clone batbaz foobar
Cloning virtPHP env from /home/jordan/projects/foobar to /home/jordan/projects/batbaz
Copying contents of /home/jordan/projects/foobar to /home/jordan/projects/batbaz
Updating activate file.
Updating PHP ini file.
Updating PHP bin wrapper.
Updating virtual PEAR install and config
Setting proper permissions on cloned bin directory
Error: cloning directory failed. I was able to clone using |
I have also noticed after running
|
Did you initiate the Perhaps you could also show us the virtphp-relevant directory structure starting from |
Ok, looking at this again, is it the case that the "new" environment is in |
This is good to know and should be looked at when the clone functionality, which is currently broken, gets fixed. |
On OSX, clone is failing due to this error: You can add a print_r($e); on line 103 of src/Virtphp/Workers/Cloner.php to see the exact error. |
I just ran through the Cloner process by hand, and I couldn't reproduce the I am, however, seeing the following issue as I step through the Cloner: When creating a new environment, a new record is inserted into the |
Clone seems to be not working properly. When I provide the environment name I want to cloned environment to show up as, I get the following error message:
"Sorry, but that is not a valid environment name."
The text was updated successfully, but these errors were encountered: