Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

[Warren Young]

On May 14, 2016, at 7:08 AM, Piotr Orzechowski  
wrote:
> 
> You solution seems to work with single repo only.

There are two easy ways to extend it to multiple repos:

1. Point “fossil serve” in the fslsrv wrapper at a directory of *.fossil files, 
not at a single fossil.  Then both of these URLs will work:

https://example.com/code/1st-repo
https://example.com/code/2nd-repo

2. Clone fslsrv for each repository, serving each on a different random 
localhost port, proxying each separately.  Run them all on server startup.

(You’ll have to either remove the bit of the script where it auto-kills the 
previous one or replace it with a /var/run/fslsrv-$reponame.pid scheme so one 
fslsrv script doesn’t kill Fossil instances that don’t belong to it.)

The only reason I can think of to choose this solution over the first is if you 
need each repository to appear somewhere else in the URL scheme.  For example, 
you might be serving each repo on a separate subdomain:

https://1st-repo.example.com
https://2nd-repo.example.com

This also requires adding separate server { } blocks to the nginx configuration 
for the subdomains.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

[Piotr Orzechowski]

Hi Warren,
thanks for your help! In fact, I have already set an "A+" graded site. The 
problem is I'm hosting multiple repositories, as you can see here: 
https://orzechowski.tech. You solution seems to work with single repo only. I 
was just trying to migrate from xinetd to systemd with my fossil configuration, 
but to no avail.
Regards,
Orzech___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

[Warren Young]

On May 11, 2016, at 1:58 PM, Piotr Orzechowski  
wrote:
> 
> "At this stage, the standalone server (e.g. "fossil server") does not support 
> SSL.”

The standard advice is to tell the fossil server to bind to localhost (as 
you’re already doing) and put it behind stunnel or an HTTPS-capable reverse 
proxy server.

I wrote up an extensive HOWTO on this for nginx + Let’s Encrypt here:

  https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg22907.html

That not only gets you TLS-encrypted connections, it gets you a 
globally-recognized certificate, achieving an “A” grade on two major “SSL” 
tests.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Unrecognized command-line option, or missing argument: --https

[Piotr Orzechowski]

Ah, I didn't read the:

"At this stage, the standalone server (e.g. "fossil server") does not support 
SSL."

here: https://www.fossil-scm.org/xfer/doc/trunk/www/server.wiki.

Still, online help should mention that as well, IMHO.

Regards,
Orzech


Dnia 11 maja 2016 21:08 Piotr Orzechowski  
napisał(a):

> Hello,
> 
> when I try to run fossil server behind https proxy with:
> 
> HOME=//fossil //fossil server --https --localhost --port  
> //fossil/
> 
> I get the following error:
> 
> unrecognized command-line option, or missing argument: --https
> 
> Am I doing something wrong? --https is listed as valid "server" option here: 
> https://www.fossil-scm.org/index.html/help?cmd=server.
> 
> Regards,
> Orzech
> 
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users