You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, the project skeleton is deployed to the folder with the specified name. But if you try to install it into the current or existing folder (even if they are empty), an error message will appear.
phalcon project . --force
Success: Project '.' was successfully
An error when deploying to an existing folder may be caused by the intention not to damage the files that are located.
But I would like to be able to implement the deployment forcibly.
The text was updated successfully, but these errors were encountered:
I believe at the very least the error message should mention the existence of the --force flag.
I can see the use case of people creating a blank directory then cd'ing into it very common, and no reason to request the --force flag provided it is indeed a blank directory. If it's not a blank directory, I think showing an error message, which mentions the --force flag is in the best interest of the user so they have a chance to review and verify they know what they are doing. Then if they are sure, they can run the command again with the --force flag.
phalcon project . --force Success: Project '.' was successfully
An error when deploying to an existing folder may be caused by the intention not to damage the files that are located.
But I would like to be able to implement the deployment forcibly.
The text was updated successfully, but these errors were encountered: