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
I wonder if it is possible to run webdiff on a webserver so it is accessible publicly? E.g., to be able to show differences between versions of a text in my git project.
I also tried to save the locally produced webpage ( Save Complete webpage after running git webdiff <left> <right> text.txt), but it is not shown on a (different) webserver anyway (it's shown for a second or less and than it disappears).
The text was updated successfully, but these errors were encountered:
I'm not sure I completely understand. You can create/edit a config file for webdiff that will serve its diff on your computer's hostname so other who can resolve your hostname can access the diff in a browser. If the machine is on a public internet then anyone could browse to your hostname and specified port.
If you want it to be something where people on the public internet to initiate the webdiff rather than you initiating it, I don't know how to do that. It feels possible, but I haven't really done any web development myself yet.
I just found a way to make webdiff publicly accessible on a server without random port
with just 4 easy steps:
1 - make config dir and several files ( dotfiles ), mine is in $HOME/.config/webdiff
2 - copy the configs directive as shown in the picture ( git-webdiff.sh and webdiff.sh is the same file except on which command ... git-websiff.sh use $(which git-webdiff) $* )
3 - make alias for webdiff and git-webdiff
4 - change your hostname ip address to 0.0.0.0 on /etc/hosts
I wonder if it is possible to run webdiff on a webserver so it is accessible publicly? E.g., to be able to show differences between versions of a text in my git project.
I also tried to save the locally produced webpage ( Save
Complete webpage
after runninggit webdiff <left> <right> text.txt
), but it is not shown on a (different) webserver anyway (it's shown for a second or less and than it disappears).The text was updated successfully, but these errors were encountered: