Discussion:
Who runs Fossil servers on Windows?
(too old to reply)
Richard Hipp
2018-08-07 16:55:57 UTC
Permalink
If you are running a Fossil server on Windows, please share with me
how you set it up. You can respond via private email directly to me
if you like.

(1) Run using "fossil server"
(2) Run using "fossil winsrv"
(3) Using Apache with CGI
(4) Using Apache with SCGI
(5) Using Nginx with SCGI
(6) Via SSH using some kind of SSHD for Windows
(7) Some other webserver (please specify)
(8) Other (please specify)

I have the impression that most if not all Fossil servers on Windows
are run using either (1) or (2). If you are using any of the other
approaches, then I especially want to hear from you.

Thanks.
--
D. Richard Hipp
***@sqlite.org
Artur Shepilko
2018-08-07 18:33:03 UTC
Permalink
Post by Richard Hipp
(1) Run using "fossil server"
Actually, it runs local to the PC, mainly to [self-]serve Wiki.

Now looking at 'fossil help winsrv' it seems that this would be a
better fit for such a use... Thanks :)
The Tick
2018-08-07 19:25:16 UTC
Permalink
Post by Richard Hipp
If you are running a Fossil server on Windows, please share with me
how you set it up. You can respond via private email directly to me
if you like.
(1) Run using "fossil server"
(2) Run using "fossil winsrv"
(3) Using Apache with CGI
(4) Using Apache with SCGI
(5) Using Nginx with SCGI
(6) Via SSH using some kind of SSHD for Windows
(7) Some other webserver (please specify)
(8) Other (please specify)
I have the impression that most if not all Fossil servers on Windows
are run using either (1) or (2). If you are using any of the other
approaches, then I especially want to hear from you.
Thanks.
I played with fossil under windows and, as far as I know, got it to
work. I used the Abyss Web Server. At one time I set up port forwarding
on my router for another little project and friends were able to connect
successfully although they did not access the fossil stuff.

A link in a web page:
Tcl <a href="cgi-bin/fossil/CWind">CWind</a> extension

cgi-bin/fossil:
#!C:/bin/fossil.exe
directory: C:/Progra~1/AbyssW~1/htdocs/FossilRepositories
notfound: /badfossil.php

.../htdocs/Fossil/Repositories contains hardlinks to the actual fossil
repositories:
htdocs/Fossil/Repositories/CWind.fossil <linked to>
C:/Users/<me>/Downloads/MyTclStuff/CWind.fossil

badfossil.php:
<html>
<head>
<title>Fossil Repository Not Found</title>
</head>
<body>
<h1>Fossil Repository Not Found</h1>
<?php
phpinfo();
?>
</body>
</html>




I asked some time ago if there was a way to pass more specific
information to the "badfossil.php" page but, since I got no response, I
assume the answer is "no".
Eugene Mindrov
2018-08-07 23:18:14 UTC
Permalink
Richard,

I'm running fossil as a server on my Windows laptop using approach #1:

fossil.exe server --localhost --port 80
Post by Richard Hipp
If you are running a Fossil server on Windows, please share with me
how you set it up. You can respond via private email directly to me
if you like.
(1) Run using "fossil server"
(2) Run using "fossil winsrv"
(3) Using Apache with CGI
(4) Using Apache with SCGI
(5) Using Nginx with SCGI
(6) Via SSH using some kind of SSHD for Windows
(7) Some other webserver (please specify)
(8) Other (please specify)
I have the impression that most if not all Fossil servers on Windows
are run using either (1) or (2). If you are using any of the other
approaches, then I especially want to hear from you.
Thanks.
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Jan Nijtmans
2018-08-08 08:19:59 UTC
Permalink
Post by Richard Hipp
If you are running a Fossil server on Windows, please share with me
how you set it up. You can respond via private email directly to me
if you like.
(1) Run using "fossil server"
(2) Run using "fossil winsrv"
(3) Using Apache with CGI
(4) Using Apache with SCGI
(5) Using Nginx with SCGI
(6) Via SSH using some kind of SSHD for Windows
(7) Some other webserver (please specify)
(8) Other (please specify)
I have the impression that most if not all Fossil servers on Windows
are run using either (1) or (2). If you are using any of the other
approaches, then I especially want to hear from you.
In april 2016, I was setting up fossil using a combination of (2) and
(7). The IIS frontent was simply used as proxy, forwarding the generic
port 80 to the internal port used by the fossil service. That's how I
discovered that at that time the --baseurl option didn't work correctly
on Windows. I fixed ithat n commit
<https://www.fossil-scm.org/index.html/info/6f35075ad72b8608>
(and a minor follow-up in the next commit). Since then,
everything is working fine.

Regards,
Jan Nijtmans

Loading...