-
-
Notifications
You must be signed in to change notification settings - Fork 243
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
docpad init
runs across some problems
#631
Labels
Comments
@balupton Here's the CLI output:
|
This was actually my fault entirely. The starting of the local docpad instance was in |
balupton
added a commit
that referenced
this issue
Sep 7, 2013
- v6.52.1 September 8, 2013 - Fixed "structure already exists" errors after successful `docpad init` and `docpad skeleton` completion - Thanks to [Eduán Lávaque](https://github.com/Greduan) for [issue #631](#631) - Better errors when a skeleton fails via the global `docpad run`
Works great now. :) |
balupton
added a commit
that referenced
this issue
Oct 23, 2013
- v6.52.1 September 8, 2013 - Fixed "structure already exists" errors after successful `docpad init` and `docpad skeleton` completion - Thanks to [Eduán Lávaque](https://github.com/Greduan) for [issue #631](#631) - Better errors when a skeleton fails via the global `docpad run`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that running
docpad init
will run it with the global version first, and then when it gets to the local version it'll try to run it again but run across problems because the folders already exist.What could be a possible solution for this?
You can observe this behavior in this video: http://youtu.be/KkHHR0MKLx0?t=6m15s
Again, I'm not sure if that's really what's happening, but it's the only thing I can come up with.
The text was updated successfully, but these errors were encountered: