-
Notifications
You must be signed in to change notification settings - Fork 27
Open
Description
I would like to test a local git repository for Canopy blog posts before pushing it to the actual repo. I built Canopy locally, but then I have not manage to get it to read posts from a local git repository.
$ ./mir-canopy -r /home/gasche/Scolaire/neu/icfp-sv/icfp2016-blog/ -i Welcome -p 8080 -u 12345
Manager: connect
Manager: configuring
2016-10-14 20:45.10: INF [git.memory] Reading HEAD
Pulling repository
Fail pull (Failure "Unknown Git protocol")
2016-10-14 20:45.10: INF [git.memory] Reading HEAD
2016-10-14 20:45.10: INF [git.memory] Reading refs/heads/master
2016-10-14 20:45.10: INF [git.memory] Reading HEAD
2016-10-14 20:45.10: INF [git.memory] Reading HEAD
2016-10-14 20:45.10: INF [git.memory] Reading refs/heads/master
HTTP server listening on port 8080
$ ./mir-canopy -r file:///home/gasche/Scolaire/neu/icfp-sv/icfp2016-blog/ -i Welcome -p 8080 -u 12345
Manager: connect
Manager: configuring
2016-10-14 20:44.41: INF [git.memory] Reading HEAD
Pulling repository
Fail pull (Failure "file is not a supported Git protocol")
2016-10-14 20:44.41: INF [git.memory] Reading HEAD
2016-10-14 20:44.41: INF [git.memory] Reading refs/heads/master
2016-10-14 20:44.41: INF [git.memory] Reading HEAD
2016-10-14 20:44.41: INF [git.memory] Reading HEAD
2016-10-14 20:44.41: INF [git.memory] Reading refs/heads/master
HTTP server listening on port 8080
Could this be supported? I grepped for not a supported protocol in the sources but couldn't find any hit for this error message. Which piece of the ecosystem is it that fails to support file?
Also, why does Canopy still run a server and loops infinitely when it failed to resolve the Git repository? Is there anything useful in that, or could it just not quit on this error?
Metadata
Metadata
Assignees
Labels
No labels