porcelain web_daemon unclear how to use #942
-
What is the way to successfully run a web_daemon unsing porcelain? I run into the issue, that dulwich\server.py fails in open_repository after joining path and root folder since the relative web url always starts with a / resulting in os.path.join to skip the basepath since the relative path is from root :-( resulting in is it me or do i miss something? i have a folder structure like /opt/something/etc/apps/ with folders in it that have or have not a .git (repo) and would like to serve this - can i just set /opt/something/etc/apps/ as root and then access the repos using http://>servername>:8123/ or how would this work? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
How are you invoking the web_daemon() function exactly? If you're looking for a web viewer, you'd want to look at something like klaus (https://github.com/jonashaag/klaus). porcelain.web_daemon() will just allow you to clone the repository with git. |
Beta Was this translation helpful? Give feedback.
-
hi, on the server side i run this
running it in a folder that is a repo and passing . as gitdir
on the serverside this gives me the output (with a little debug output extra)
the client says
does that help? |
Beta Was this translation helpful? Give feedback.
-
in the end i would like to provide the three urls /refs/heads (?) upload and download pack behind a rest service (splunk) but first i want to see if it works kinda and if that is all right proceed. |
Beta Was this translation helpful? Give feedback.
-
You're specifying a different path than you're actually exporting. You'd want: git clone http://localhost:8123/opt/splunk/git To get different behaviour, you can look at providing your own version of dulwich.server.FilesystemBackend in combination with dulwich.web.make_server. |
Beta Was this translation helpful? Give feedback.
You're specifying a different path than you're actually exporting. You'd want:
git clone http://localhost:8123/opt/splunk/git
To get different behaviour, you can look at providing your own version of dulwich.server.FilesystemBackend in combination with dulwich.web.make_server.