Re: [fossil-users] Setting up an internet Fossil server

[John Found]

On Wed, 7 Mar 2018 14:00:58 -0800
Scott Doctor  wrote:

> Putting the repository name into it
> 
> https://nousrandom.net/code/Random

All fossil repositories, placed in this directory must have .fossil extension.
Try to rename this file to "Random.fossil" and then try to access it on

https://nousrandom.net/code/Random

> 
> the browser tries to download the file. So it seems the issue is 
> with the location{} statement. Will respond with the complete 
> nginx.conf file later (got some pay-the-bills work to do at this 
> moment). The config is the default configuration from a clean 
> install of debian, nginx, and certbot installation of 
> letsencrypt.. Except for the ssl stuff added by certbot, it is 
> all default. There are two include files that are linked from 
> with the file. The three server statements are in the include 
> files. I put the location {} in the first server declaration.
> 
> 
> -
> Scott Doctor
> sc...@scottdoctor.com
> -
> 
> On 3/7/2018 09:08, John Found wrote:
> > On Tue, 6 Mar 2018 16:30:58 -0800
> > Scott Doctor  wrote:
> >
> >> Well I did everything in the list. Triple checked eveything.
> >> Keep getting a 403 error (forbidden) when I try to access
> >> through the browser.
> >>
> >> https://nousrandom.net/code/
> >>
> >> I created a new repository in that folder, opened it and did an
> >> empty commit. Must be missing some setting somewhere. I have the
> >> fossil executable in /usr/bin with permissions at 755. I can
> >> execute fossil from the command line (via putty). I think a
> >> problem may be where I put the location {...}.
> >>
> >> Any suggestions what to check?
> >>
> > Very hard to say... Can you download the created .fossil files, by 
> > specifying them in the URL? If so, then the
> > location {} settings are wrong and this directory is served as an usual web 
> > site directory.
> >
> > Think about publishing the nginx.conf files. I don't think it is a big 
> > security risk.
> >
> >> -
> >> Scott Doctor
> >> sc...@scottdoctor.com
> >> -
> >>
> >> On 3/3/2018 15:17, John Found wrote:
> >>> On Sat, 24 Feb 2018 10:57:58 -0800
> >>> Scott Doctor  wrote:
> >>>
>  I am trying to setup an internet server for one of my projects
>  that I am going to make open source using fossil. I have a new
>  Linode server account with a clean install (and fully updated)
>  of debian and nginx with letsencrypt https working properly. I
>  am having trouble getting fossil to work.
> 
>  Is there a step-by-step how to get fossil to work from an
>  internet page?
>  My website I am trying to do this on is:
> 
> >>> If you have working nginx with https, the remaining is straightforward:
> >>>
> >>> 1. Make fossil to work like a scgi server. I have done it through systemd 
> >>> service;
> >>>
> >>> 1.1 create file "/etc/systemd/system/fossil.service" with the following 
> >>> text:
> >>>
> >>> [Unit]
> >>> Description=Fossil scm SCGI script.
> >>> After=network.target network-online.target nss-lookup.target nginx.service
> >>>
> >>> [Service]
> >>> Type=simple
> >>> User=THE_USER_YOU_WANT
> >>> WorkingDirectory=/DOCUMENT_ROOT/fossil/
> >>> ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi 
> >>> --localhost --port 9000 --repolist
> >>> Restart=on-failure
> >>>
> >>> [Install]
> >>> WantedBy=nginx.service
> >>>
> >>> 1.2 Execute:
> >>>
> >>> $sudo systemctl enable fossil
> >>> $sudo systemctl start fossil
> >>>
> >>> 2. Configure nginx.
> >>>
> >>> Include in the server{} section of your config file:
> >>>
> >>> location /fossil/ {
> >>> scgi_pass 127.0.0.1:9000;
> >>> include scgi_params;
> >>> scgi_param SCRIPT_NAME "/fossil";
> >>> client_max_body_size 20M;
> >>> }
> >>>
> >>> 3. Now every .fossil repo, located in the /fossil/ directory will be 
> >>> accessible on:
> >>>
> >>> https://your.web.site/fossil/repo_name/
> >>>
> >>>
> >>>
> >>> Hope will be helpful.
> >>> Regards
> >>>
> >> ___
> >> fossil-users mailing list
> >> fossil-users@lists.fossil-scm.org
> >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> >
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Setting up an internet Fossil server

[Scott Doctor]

Putting the repository name into it

https://nousrandom.net/code/Random

the browser tries to download the file. So it seems the issue is 
with the location{} statement. Will respond with the complete 
nginx.conf file later (got some pay-the-bills work to do at this 
moment). The config is the default configuration from a clean 
install of debian, nginx, and certbot installation of 
letsencrypt.. Except for the ssl stuff added by certbot, it is 
all default. There are two include files that are linked from 
with the file. The three server statements are in the include 
files. I put the location {} in the first server declaration.



-
Scott Doctor
sc...@scottdoctor.com
-

On 3/7/2018 09:08, John Found wrote:

On Tue, 6 Mar 2018 16:30:58 -0800
Scott Doctor  wrote:


Well I did everything in the list. Triple checked eveything.
Keep getting a 403 error (forbidden) when I try to access
through the browser.

https://nousrandom.net/code/

I created a new repository in that folder, opened it and did an
empty commit. Must be missing some setting somewhere. I have the
fossil executable in /usr/bin with permissions at 755. I can
execute fossil from the command line (via putty). I think a
problem may be where I put the location {...}.

Any suggestions what to check?


Very hard to say... Can you download the created .fossil files, by specifying 
them in the URL? If so, then the
location {} settings are wrong and this directory is served as an usual web 
site directory.

Think about publishing the nginx.conf files. I don't think it is a big security 
risk.


-
Scott Doctor
sc...@scottdoctor.com
-

On 3/3/2018 15:17, John Found wrote:

On Sat, 24 Feb 2018 10:57:58 -0800
Scott Doctor  wrote:


I am trying to setup an internet server for one of my projects
that I am going to make open source using fossil. I have a new
Linode server account with a clean install (and fully updated)
of debian and nginx with letsencrypt https working properly. I
am having trouble getting fossil to work.

Is there a step-by-step how to get fossil to work from an
internet page?
My website I am trying to do this on is:


If you have working nginx with https, the remaining is straightforward:

1. Make fossil to work like a scgi server. I have done it through systemd 
service;

1.1 create file "/etc/systemd/system/fossil.service" with the following text:

[Unit]
Description=Fossil scm SCGI script.
After=network.target network-online.target nss-lookup.target nginx.service

[Service]
Type=simple
User=THE_USER_YOU_WANT
WorkingDirectory=/DOCUMENT_ROOT/fossil/
ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi --localhost 
--port 9000 --repolist
Restart=on-failure

[Install]
WantedBy=nginx.service

1.2 Execute:

$sudo systemctl enable fossil
$sudo systemctl start fossil

2. Configure nginx.

Include in the server{} section of your config file:

location /fossil/ {
scgi_pass 127.0.0.1:9000;
include scgi_params;
scgi_param SCRIPT_NAME "/fossil";
client_max_body_size 20M;
}

3. Now every .fossil repo, located in the /fossil/ directory will be accessible 
on:

https://your.web.site/fossil/repo_name/



Hope will be helpful.
Regards


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




___
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] Setting up an internet Fossil server

[John Found]

On Tue, 6 Mar 2018 16:30:58 -0800
Scott Doctor  wrote:

> 
> Well I did everything in the list. Triple checked eveything. 
> Keep getting a 403 error (forbidden) when I try to access 
> through the browser.
> 
> https://nousrandom.net/code/
> 
> I created a new repository in that folder, opened it and did an 
> empty commit. Must be missing some setting somewhere. I have the 
> fossil executable in /usr/bin with permissions at 755. I can 
> execute fossil from the command line (via putty). I think a 
> problem may be where I put the location {...}.
> 
> Any suggestions what to check?
> 

Very hard to say... Can you download the created .fossil files, by specifying 
them in the URL? If so, then the 
location {} settings are wrong and this directory is served as an usual web 
site directory.

Think about publishing the nginx.conf files. I don't think it is a big security 
risk.

> 
> -
> Scott Doctor
> sc...@scottdoctor.com
> -
> 
> On 3/3/2018 15:17, John Found wrote:
> > On Sat, 24 Feb 2018 10:57:58 -0800
> > Scott Doctor  wrote:
> >
> >> I am trying to setup an internet server for one of my projects
> >> that I am going to make open source using fossil. I have a new
> >> Linode server account with a clean install (and fully updated)
> >> of debian and nginx with letsencrypt https working properly. I
> >> am having trouble getting fossil to work.
> >>
> >> Is there a step-by-step how to get fossil to work from an
> >> internet page?
> >> My website I am trying to do this on is:
> >>
> > If you have working nginx with https, the remaining is straightforward:
> >
> > 1. Make fossil to work like a scgi server. I have done it through systemd 
> > service;
> >
> > 1.1 create file "/etc/systemd/system/fossil.service" with the following 
> > text:
> >
> > [Unit]
> > Description=Fossil scm SCGI script.
> > After=network.target network-online.target nss-lookup.target nginx.service
> >
> > [Service]
> > Type=simple
> > User=THE_USER_YOU_WANT
> > WorkingDirectory=/DOCUMENT_ROOT/fossil/
> > ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi --localhost 
> > --port 9000 --repolist
> > Restart=on-failure
> >
> > [Install]
> > WantedBy=nginx.service
> >
> > 1.2 Execute:
> >
> > $sudo systemctl enable fossil
> > $sudo systemctl start fossil
> >
> > 2. Configure nginx.
> >
> > Include in the server{} section of your config file:
> >
> > location /fossil/ {
> >scgi_pass 127.0.0.1:9000;
> >include scgi_params;
> >scgi_param SCRIPT_NAME "/fossil";
> >client_max_body_size 20M;
> > }
> >
> > 3. Now every .fossil repo, located in the /fossil/ directory will be 
> > accessible on:
> >
> > https://your.web.site/fossil/repo_name/
> >
> >
> >
> > Hope will be helpful.
> > Regards
> >
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Setting up an internet Fossil server

[Warren Young]

On Mar 6, 2018, at 5:30 PM, Scott Doctor  wrote:
> 
> Any suggestions what to check?

File permissions, SELinux, web server permissions…there’s a whole pile of 
things that can go wrong here.

I just heard that the venerable Unix and Linux System Administrator’s Handbook 
came out in a new version not long ago.  Hint. :)
___
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] Setting up an internet Fossil server

[Scott Doctor]

Well I did everything in the list. Triple checked eveything. 
Keep getting a 403 error (forbidden) when I try to access 
through the browser.


https://nousrandom.net/code/

I created a new repository in that folder, opened it and did an 
empty commit. Must be missing some setting somewhere. I have the 
fossil executable in /usr/bin with permissions at 755. I can 
execute fossil from the command line (via putty). I think a 
problem may be where I put the location {...}.


Any suggestions what to check?


-
Scott Doctor
sc...@scottdoctor.com
-

On 3/3/2018 15:17, John Found wrote:

On Sat, 24 Feb 2018 10:57:58 -0800
Scott Doctor  wrote:


I am trying to setup an internet server for one of my projects
that I am going to make open source using fossil. I have a new
Linode server account with a clean install (and fully updated)
of debian and nginx with letsencrypt https working properly. I
am having trouble getting fossil to work.

Is there a step-by-step how to get fossil to work from an
internet page?
My website I am trying to do this on is:


If you have working nginx with https, the remaining is straightforward:

1. Make fossil to work like a scgi server. I have done it through systemd 
service;

1.1 create file "/etc/systemd/system/fossil.service" with the following text:

[Unit]
Description=Fossil scm SCGI script.
After=network.target network-online.target nss-lookup.target nginx.service

[Service]
Type=simple
User=THE_USER_YOU_WANT
WorkingDirectory=/DOCUMENT_ROOT/fossil/
ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi --localhost 
--port 9000 --repolist
Restart=on-failure

[Install]
WantedBy=nginx.service

1.2 Execute:

$sudo systemctl enable fossil
$sudo systemctl start fossil

2. Configure nginx.

Include in the server{} section of your config file:

location /fossil/ {
   scgi_pass 127.0.0.1:9000;
   include scgi_params;
   scgi_param SCRIPT_NAME "/fossil";
   client_max_body_size 20M;
}

3. Now every .fossil repo, located in the /fossil/ directory will be accessible 
on:

https://your.web.site/fossil/repo_name/



Hope will be helpful.
Regards



___
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] Setting up an internet Fossil server

[John Found]

On Mon, 5 Mar 2018 16:04:35 -0800
Scott Doctor  wrote:

> 
> This is the first time I am using nginx so I am learning this as 
> I go.
> 
> A couple of questions. Under your 1.1 the [service] section,
> 
> what do I use for THE_USER_YOU_WANT since the access will be 
> from the internet?

Well, I am not very good in security. I am using my own username, simply 
because 
it makes the file ownership to me and this way I can copy/edit/delete them 
easily. :D

I am sure some more advanced Linux user will make it other way. I am not a good 
example
of linux admin.

> 
> The default location for web pages is  /var/www/html/
> 
> is this what I should use for DOCUMENT_ROOT?
> 

Yes, if your web site is located there. My own site is located in 
/home/www/[virtual hosts]
but, see above. 

> I assume from the ExecStart I should place the fossil executable 
> in /usr/bin,
> 
> correct?

Yes, or change the path in the .service file if you prefer to install it 
somewhere else.

> 
> If I reboot the server, is it necessary for me to login and
> 
> manually start by your 1.2 Execute commands?
> 

No. Once you execute "sudo systemctl enable fossil", systemd will start this 
service on every reboot.

You can manually control the service by "sudo systemctl 
[start|stop|restart|status] SERVICENAME"


> I assume the config file you refer in your 1.2 is the 
> /etc/nginx/nginx.conf
> 
> Correct?
> 
> the file has three declared server sections, each follows each.
> 
> Do these catenate? or does each one have a specific use?
> 
> simply, which one am I supposed to insert the location stuff?
> 

In the section "server{}". If you have several "server{}" sections, it means you
have several virtual hosts (subdomains). Then insert it in the "server" section 
of
the subdomain you want to have fossil directory.

There are many variants of the nginx config files. For example I have one main 
/etc/nginx/nginx.conf file and
several include files (one for every subdomain) in /etc/nginx/websites/ 
subdirectory. The include files contain
only settings for the separate subdomain servers, so, my fossil "location" 
section is in one of these.

In your case it can be different. What is the best config pattern? I don't know 
actually. 


> Scott Doctor sc...@scottdoctor.com -
> 

-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Setting up an internet Fossil server

[Scott Doctor]

Ugh, mail program seems to have word wrapped the quoted section 
of your post.


-
Scott Doctor
sc...@scottdoctor.com
-

On 3/3/2018 15:17, John Found wrote:

On Sat, 24 Feb 2018 10:57:58 -0800
Scott Doctor  wrote:


I am trying to setup an internet server for one of my projects
that I am going to make open source using fossil. I have a new
Linode server account with a clean install (and fully updated)
of debian and nginx with letsencrypt https working properly. I
am having trouble getting fossil to work.

Is there a step-by-step how to get fossil to work from an
internet page?
My website I am trying to do this on is:


If you have working nginx with https, the remaining is straightforward:

1. Make fossil to work like a scgi server. I have done it through systemd 
service;

1.1 create file "/etc/systemd/system/fossil.service" with the following text:

[Unit]
Description=Fossil scm SCGI script.
After=network.target network-online.target nss-lookup.target nginx.service

[Service]
Type=simple
User=THE_USER_YOU_WANT
WorkingDirectory=/DOCUMENT_ROOT/fossil/
ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi --localhost 
--port 9000 --repolist
Restart=on-failure

[Install]
WantedBy=nginx.service

1.2 Execute:

$sudo systemctl enable fossil
$sudo systemctl start fossil

2. Configure nginx.

Include in the server{} section of your config file:

location /fossil/ {
   scgi_pass 127.0.0.1:9000;
   include scgi_params;
   scgi_param SCRIPT_NAME "/fossil";
   client_max_body_size 20M;
}

3. Now every .fossil repo, located in the /fossil/ directory will be accessible 
on:

https://your.web.site/fossil/repo_name/



Hope will be helpful.
Regards



___
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] Setting up an internet Fossil server

[Scott Doctor]

This is the first time I am using nginx so I am learning this as 
I go.


A couple of questions. Under your 1.1 the [service] section,

what do I use for THE_USER_YOU_WANT since the access will be 
from the internet?


The default location for web pages is  /var/www/html/

is this what I should use for DOCUMENT_ROOT?

I assume from the ExecStart I should place the fossil executable 
in /usr/bin,


correct?

If I reboot the server, is it necessary for me to login and

manually start by your 1.2 Execute commands?

I assume the config file you refer in your 1.2 is the 
/etc/nginx/nginx.conf


Correct?

the file has three declared server sections, each follows each.

Do these catenate? or does each one have a specific use?

simply, which one am I supposed to insert the location stuff?

-

Scott Doctor sc...@scottdoctor.com -

On 3/3/2018 15:17, John Found wrote

If you have working nginx with https, the remaining is 
straightforward: 1. Make fossil to work like a scgi server. I 
have done it through systemd service; 1.1 create file 
"/etc/systemd/system/fossil.service" with the following text: 
[Unit] Description=Fossil scm SCGI script. 
After=network.target network-online.target nss-lookup.target 
nginx.service [Service] Type=simple User=THE_USER_YOU_WANT 
WorkingDirectory=/DOCUMENT_ROOT/fossil/ 
ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi 
--localhost --port 9000 --repolist Restart=on-failure 
[Install] WantedBy=nginx.service 1.2 Execute: $sudo systemctl 
enable fossil $sudo systemctl start fossil 2. Configure nginx. 
Include in the server{} section of your config file: location 
/fossil/ { scgi_pass 127.0.0.1:9000; include scgi_params; 
scgi_param SCRIPT_NAME "/fossil"; client_max_body_size 20M; } 
3. Now every .fossil repo, located in the /fossil/ directory 
will be accessible on: https://your.web.site/fossil/repo_name/ 
Hope will be helpful. Regards


___
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] Setting up an internet Fossil server

[John Found]

On Sat, 24 Feb 2018 10:57:58 -0800
Scott Doctor  wrote:

> I am trying to setup an internet server for one of my projects 
> that I am going to make open source using fossil. I have a new 
> Linode server account with a clean install (and fully updated) 
> of debian and nginx with letsencrypt https working properly. I 
> am having trouble getting fossil to work.
> 
> Is there a step-by-step how to get fossil to work from an 
> internet page?
> My website I am trying to do this on is:
> 

If you have working nginx with https, the remaining is straightforward:

1. Make fossil to work like a scgi server. I have done it through systemd 
service;

1.1 create file "/etc/systemd/system/fossil.service" with the following text:

[Unit]
Description=Fossil scm SCGI script.
After=network.target network-online.target nss-lookup.target nginx.service

[Service]
Type=simple
User=THE_USER_YOU_WANT
WorkingDirectory=/DOCUMENT_ROOT/fossil/
ExecStart=/usr/bin/fossil server /DOCUMENT_ROOT/fossil/ --scgi --localhost 
--port 9000 --repolist
Restart=on-failure

[Install]
WantedBy=nginx.service

1.2 Execute:

$sudo systemctl enable fossil
$sudo systemctl start fossil

2. Configure nginx. 

Include in the server{} section of your config file:

location /fossil/ {
  scgi_pass 127.0.0.1:9000;
  include scgi_params;
  scgi_param SCRIPT_NAME "/fossil"; 
  client_max_body_size 20M;
}

3. Now every .fossil repo, located in the /fossil/ directory will be accessible 
on:

https://your.web.site/fossil/repo_name/



Hope will be helpful.
Regards

-- 
http://fresh.flatassembler.net
http://asm32.info
John Found 
___
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] Setting up an internet Fossil server

[Richard Hipp]

The SQLite.org website, and the Fossil-SCM.org website (which is the
same server) have always run off of the "althttpd" webserver.  I have
just put up documentation for this very simple but effective webserver
at

https://www.sqlite.org/docsrc/doc/trunk/misc/althttpd.md

If you prefer to run Fossil using Apache or Nginx or Lighttpd or
whatever else you are comfortable with, do so with my blessings.
Diversity is good in this context as it helps to flush out bugs in
Fossil.  Information about althttpd is provide only in case you are
interested.

-- 
D. Richard Hipp
d...@sqlite.org
___
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] Setting up an internet Fossil server

[Roy Keene]

ChiselApp also uses Let's Encrypt

On Tue, 27 Feb 2018, Warren Young wrote:


On Feb 27, 2018, at 8:37 AM, Roy Keene  wrote:


You don't lose support for TLS, since Apache supports TLS.  It's just running 
Fossil as a CGI -- this is exactly how ChiselApp works.


Compare Thomas? post to the HOWTO I linked in my first post in this thread.  
The largest part of the difference between them is that my HOWTO gives you a 
Let?s Encrypt setup as well as a Fossil server.  Since Thomas doesn?t describe 
how to configure TLS on Apache, I?d say that it?s fair to say that?s one big 
reason why Thomas? configuration is simpler than mine.

A much smaller part of the delta is plain old CGI vs ?fossil server --scgi?, 
which I think is well worth the minor complexity to avoid the CPU and disk hits 
of repeated Fossil launches.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
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] Setting up an internet Fossil server

[Warren Young]

On Feb 27, 2018, at 8:37 AM, Roy Keene  wrote:
> 
> You don't lose support for TLS, since Apache supports TLS.  It's just running 
> Fossil as a CGI -- this is exactly how ChiselApp works.

Compare Thomas’ post to the HOWTO I linked in my first post in this thread.  
The largest part of the difference between them is that my HOWTO gives you a 
Let’s Encrypt setup as well as a Fossil server.  Since Thomas doesn’t describe 
how to configure TLS on Apache, I’d say that it’s fair to say that’s one big 
reason why Thomas’ configuration is simpler than mine.

A much smaller part of the delta is plain old CGI vs “fossil server --scgi”, 
which I think is well worth the minor complexity to avoid the CPU and disk hits 
of repeated Fossil launches.
___
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] Setting up an internet Fossil server

[Roy Keene]

You don't lose support for TLS, since Apache supports TLS.  It's just 
running Fossil as a CGI -- this is exactly how ChiselApp works.


On Tue, 27 Feb 2018, Warren Young wrote:


On Feb 26, 2018, at 3:33 PM, Thomas Levine <_...@thomaslevine.com> wrote:


Since it seems that the only dynamic stuff is in PHP and fossil,
I suggest using Apache mod_php and mod_cgi (contrary to Warren's
suggestion), as I think the configuration will be easier.


Of course, but then you lose HTTPS, which is the only reason my configuration 
is difficult at all.  If all you wanted is reverse proxying, you?d do away with 
steps 1-6, simplifying the HOWTO considerably.

I don?t view TLS as optional for password-protected public web resources in 
these post-Firesheep days.

Even if you don?t care about your own Fossil repo?s security, Google has been 
punishing sites that are not available via HTTPS for a couple of years now, 
both through reduced rankings in the search engine and through increasingly 
strident warnings in Chrome.

That?s not speculation, Google?s been announcing these things publicly:

  https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
  https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn

There may come a day when going to an HTTP-only web site will require multiple 
affirmations asymptotically approaching ?Yes, I?m really quite certain I want 
my face eaten by a rabid grue.  Just let me look at this one web site first, 
please.?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
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] Setting up an internet Fossil server

[Warren Young]

On Feb 26, 2018, at 3:33 PM, Thomas Levine <_...@thomaslevine.com> wrote:
> 
> Since it seems that the only dynamic stuff is in PHP and fossil,
> I suggest using Apache mod_php and mod_cgi (contrary to Warren's
> suggestion), as I think the configuration will be easier.

Of course, but then you lose HTTPS, which is the only reason my configuration 
is difficult at all.  If all you wanted is reverse proxying, you’d do away with 
steps 1-6, simplifying the HOWTO considerably.

I don’t view TLS as optional for password-protected public web resources in 
these post-Firesheep days.

Even if you don’t care about your own Fossil repo’s security, Google has been 
punishing sites that are not available via HTTPS for a couple of years now, 
both through reduced rankings in the search engine and through increasingly 
strident warnings in Chrome.

That’s not speculation, Google’s been announcing these things publicly:

   https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html
   https://developers.google.com/web/updates/2016/10/avoid-not-secure-warn

There may come a day when going to an HTTP-only web site will require multiple 
affirmations asymptotically approaching “Yes, I’m really quite certain I want 
my face eaten by a rabid grue.  Just let me look at this one web site first, 
please.”
___
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] Setting up an internet Fossil server

[Thomas Levine]

Since it seems that the only dynamic stuff is in PHP and fossil,
I suggest using Apache mod_php and mod_cgi (contrary to Warren's
suggestion), as I think the configuration will be easier.

If that is an option, you can copy my configuration. I have a file in my
web root called "scm" that says this:

  #!/usr/bin/env fossil
  directory: /home/protected/r
  repolist

That file is marked as a CGI script, as in this template that generates
the htaccess file.
https://thomaslevine.com/scm/dadaportal/artifact?ln=6..8=ddbddcaaac7287d8

The repositories are in /home/protected/r.

It corresponds to this web page.
https://thomaslevine.com/scm

You would of course have to switch the rest of your configuration to
Apache, but that might be very easy.
___
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] Setting up an internet Fossil server

[Warren Young]

On Feb 26, 2018, at 1:31 PM, Scott Doctor  wrote:
> 
> What I want is for fossil to activate when I access a specific directory to 
> use fossil.

That’s step 7.  Only /code gets reverse-proxied to Fossil.  Every other URL is 
served by nginx only.
___
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] Setting up an internet Fossil server

[Scott Robison]

I've done similar work for my own lighttpd based personal server. If you'd
like I can share my config, maybe it would be helpful.

On Feb 26, 2018 1:36 PM, "Roy Keene"  wrote:

> Scott,
>
> Fossil can be run in any URL suffix on an existing domain.  This
> is how, for example ChiselApp.com works -- each user*repo is a different
> URL and they run their own repositories, while the rest of the site runs
> PHP.
>
> Thanks,
> Roy Keene
>
> On Mon, 26 Feb 2018, Scott Doctor wrote:
>
>
>> Going to give this a try. (also busy with other pay-the-bills work so I
>> tend to do this one in my spare (ha) time).
>>
>> The issue I am trying to figure out is that it seems it is an all or
>> nothing setup. Either the website is using fossil as the website or not at
>> all. Most of the website is HTML5 and php pages that have nothing to do
>> with the fossil archive. It is the functionality of the random number
>> generator, api, and website UI I designed that I am packaging up as an open
>> source project. Hence the use of fossil.
>>
>> What I want is for fossil to activate when I access a specific directory
>> to use fossil.
>>
>> https://nousrandom.net/code/
>>
>> But it appears I am going to have to make a sub-domain to do this.
>>
>> I put the fossil program in that folder, and through the command line
>> interface (via putty) created a new archive in that folder. However, when I
>> issue the command
>>
>> fossil server --scgi
>>
>> the program runs in the foreground and the command line control is
>> unusable until I ctrl-c.
>>
>> So I guess I need to create a sub-domain to use fossil.
>>
>> Still have not yet got it to work even as a stand-alone.
>>
>> To be continued...
>>
>>
>> -
>> Scott Doctor
>> sc...@scottdoctor.com
>> -
>>
>> On 2/26/2018 05:17, Warren Young wrote:
>>
>>> On Feb 24, 2018, at 11:57 AM, Scott Doctor 
>>> wrote:
>>>

 Is there a step-by-step how to get fossil to work from an internet page?

>>> I?ve posted this here several times now:
>>>
>>> https://www.mail-archive.com/fossil-users@lists.fossil-scm.o
>>> rg/msg22907.html
>>>
>>> Since you?ve already got Let?s Encrypt working with nginx, you can skip
>>> all of that.  The HOWTO was written before Let?s Encrypt had built-in
>>> support for nginx.
>>>
>>> ___
>>> fossil-users mailing list
>>> fossil-users@lists.fossil-scm.org
>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>>
>>
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
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] Setting up an internet Fossil server

[Roy Keene]

Scott,

	Fossil can be run in any URL suffix on an existing domain.  This 
is how, for example ChiselApp.com works -- each user*repo is a different 
URL and they run their own repositories, while the rest of the site runs 
PHP.


Thanks,
Roy Keene

On Mon, 26 Feb 2018, Scott Doctor wrote:



Going to give this a try. (also busy with other pay-the-bills work so I tend 
to do this one in my spare (ha) time).


The issue I am trying to figure out is that it seems it is an all or nothing 
setup. Either the website is using fossil as the website or not at all. Most 
of the website is HTML5 and php pages that have nothing to do with the fossil 
archive. It is the functionality of the random number generator, api, and 
website UI I designed that I am packaging up as an open source project. Hence 
the use of fossil.


What I want is for fossil to activate when I access a specific directory to 
use fossil.


https://nousrandom.net/code/

But it appears I am going to have to make a sub-domain to do this.

I put the fossil program in that folder, and through the command line 
interface (via putty) created a new archive in that folder. However, when I 
issue the command


fossil server --scgi

the program runs in the foreground and the command line control is unusable 
until I ctrl-c.


So I guess I need to create a sub-domain to use fossil.

Still have not yet got it to work even as a stand-alone.

To be continued...


-
Scott Doctor
sc...@scottdoctor.com
-

On 2/26/2018 05:17, Warren Young wrote:

On Feb 24, 2018, at 11:57 AM, Scott Doctor  wrote:


Is there a step-by-step how to get fossil to work from an internet page?

I?ve posted this here several times now:

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

Since you?ve already got Let?s Encrypt working with nginx, you can skip all 
of that.  The HOWTO was written before Let?s Encrypt had built-in support 
for nginx.


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
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] Setting up an internet Fossil server

[Scott Doctor]

Regarding setting up https in nginx, certbot now supports nginx. 
the letsencrypt website has a link to the certbot page where you 
choose the operating system and server. do a few simple command 
line operations, answer a few questions, wait a few seconds, and 
done.


-
Scott Doctor
sc...@scottdoctor.com
-

On 2/26/2018 05:17, Warren Young wrote:

On Feb 24, 2018, at 11:57 AM, Scott Doctor  wrote:


Is there a step-by-step how to get fossil to work from an internet page?

I’ve posted this here several times now:

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

Since you’ve already got Let’s Encrypt working with nginx, you can skip all of 
that.  The HOWTO was written before Let’s Encrypt had built-in support for 
nginx.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
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] Setting up an internet Fossil server

[Scott Doctor]

Going to give this a try. (also busy with other pay-the-bills 
work so I tend to do this one in my spare (ha) time).


The issue I am trying to figure out is that it seems it is an 
all or nothing setup. Either the website is using fossil as the 
website or not at all. Most of the website is HTML5 and php 
pages that have nothing to do with the fossil archive. It is the 
functionality of the random number generator, api, and website 
UI I designed that I am packaging up as an open source project. 
Hence the use of fossil.


What I want is for fossil to activate when I access a specific 
directory to use fossil.


https://nousrandom.net/code/

But it appears I am going to have to make a sub-domain to do this.

I put the fossil program in that folder, and through the command 
line interface (via putty) created a new archive in that folder. 
However, when I issue the command


fossil server --scgi

the program runs in the foreground and the command line control 
is unusable until I ctrl-c.


So I guess I need to create a sub-domain to use fossil.

Still have not yet got it to work even as a stand-alone.

To be continued...


-
Scott Doctor
sc...@scottdoctor.com
-

On 2/26/2018 05:17, Warren Young wrote:

On Feb 24, 2018, at 11:57 AM, Scott Doctor  wrote:


Is there a step-by-step how to get fossil to work from an internet page?

I’ve posted this here several times now:

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

Since you’ve already got Let’s Encrypt working with nginx, you can skip all of 
that.  The HOWTO was written before Let’s Encrypt had built-in support for 
nginx.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
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] Setting up an internet Fossil server

[Warren Young]

On Feb 24, 2018, at 11:57 AM, Scott Doctor  wrote:
> 
> 
> Is there a step-by-step how to get fossil to work from an internet page?

I’ve posted this here several times now:

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

Since you’ve already got Let’s Encrypt working with nginx, you can skip all of 
that.  The HOWTO was written before Let’s Encrypt had built-in support for 
nginx.

___
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] Setting up an internet Fossil server

[Andy Bradford]

Thus said Scott Doctor on Sat, 24 Feb 2018 10:57:58 -0800:

> I am having trouble getting fossil to work.

What specifically are you having trouble with?

Thanks,

Andy
-- 
TAI64 timestamp: 40005a91c739


___
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] Setting up an internet Fossil server

[Richard Hipp]

On 2/24/18, Scott Doctor  wrote:
> I am trying to setup an internet server for one of my projects
> that I am going to make open source using fossil. I have a new
> Linode server account with a clean install (and fully updated)
> of debian and nginx with letsencrypt https working properly. I
> am having trouble getting fossil to work.
>
> Is there a step-by-step how to get fossil to work from an
> internet page?
> My website I am trying to do this on is:
>
> https://nousrandom.net/

There is no step-by-step guide right now, but it would be great if you
could write one up and contribute it!

Meanwhile, here are some hints:

https://www.fossil-scm.org/fossil/doc/trunk/www/scgi.wiki
https://www.fossil-scm.org/fossil/doc/trunk/www/server.wiki
-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Setting up an internet Fossil server

[Scott Doctor]

I am trying to setup an internet server for one of my projects 
that I am going to make open source using fossil. I have a new 
Linode server account with a clean install (and fully updated) 
of debian and nginx with letsencrypt https working properly. I 
am having trouble getting fossil to work.


Is there a step-by-step how to get fossil to work from an 
internet page?

My website I am trying to do this on is:

https://nousrandom.net/


-- - Scott Doctor sc...@scottdoctor.com 
-


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users