Discussion:
getting Fossil running on a shared host
(too old to reply)
Chad Perrin
2012-10-28 16:52:46 UTC
Permalink
I have some need for Fossil on a shared host. My first pass at trying to
get it running a month or two ago, following the directions in the online
documentation for Fossil SCM, met with failure. Before I give it another
try, I thought it might make sense to ask for tips here.

The shared hosting provider in question is Bluehost. Are there some tips
and caveats that anyone can offer me for how to handle Bluehost in
particular to get Fossil running? I'll need the ability to push and pull
via HTTPS at least (both authenticated and "anonymous" pull access),
preferably also SSH, and of course the usual web access stuff as well
(wiki, issue tracker, source code browsing).
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
David Given
2012-10-28 18:56:28 UTC
Permalink
Post by Chad Perrin
Are there some tips
and caveats that anyone can offer me for how to handle Bluehost in
particular to get Fossil running?
The magic phrase to look for is 'custom CGI script'. Fossil as a server
works via CGI, so if Bluehost let you write your own CGI scripts then
Fossil will work. And if that works, everything should work.

SSL is a bit more complicated, but only because SSL with HTTP is
complicated --- each site with SSL must have its own IP address, so if
your site shares an IP with other people life can be awkward. But that's
all the job of the HTTP server and nothing to do with Fossil, so if your
site supports SSL at all it should Just Work.
--
┌───  ───── http://www.cowlark.com ─────
│ "Of course, on a sufficiently small planet, 40 km/hr is, in fact,
│ sufficient to punt the elastic spherical cow into low orbit." ---
│ Brooks Moses on r.a.sf.c
Nolan Darilek
2012-10-28 19:02:57 UTC
Permalink
Post by David Given
SSL is a bit more complicated, but only because SSL with HTTP is
complicated --- each site with SSL must have its own IP address, so if
your site shares an IP with other people life can be awkward. But
that's all the job of the HTTP server and nothing to do with Fossil,
so if your site supports SSL at all it should Just Work.
Read about SNI, which allows multiple SSL certs on a single IP and is
supported in all modern browsers.
David Given
2012-10-28 19:45:05 UTC
Permalink
On 28/10/12 19:02, Nolan Darilek wrote:
[...]
Post by Nolan Darilek
Read about SNI, which allows multiple SSL certs on a single IP and is
supported in all modern browsers.
That's totally new to me --- glad they finally sorted that out. Thanks!
--
┌───  ───── http://www.cowlark.com ─────
│ "Of course, on a sufficiently small planet, 40 km/hr is, in fact,
│ sufficient to punt the elastic spherical cow into low orbit." ---
│ Brooks Moses on r.a.sf.c
Chad Perrin
2012-10-30 01:35:44 UTC
Permalink
Post by David Given
Post by Chad Perrin
Are there some tips
and caveats that anyone can offer me for how to handle Bluehost in
particular to get Fossil running?
The magic phrase to look for is 'custom CGI script'. Fossil as a server
works via CGI, so if Bluehost let you write your own CGI scripts then
Fossil will work. And if that works, everything should work.
Those would be the instructions I followed. As mentioned elsewhere in
answer to my question, though, the solution apparently involves compiling
a 64b version of Fossil for use on the shared hosting provider.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
John Found
2012-10-28 19:20:07 UTC
Permalink
The big problem with bluehost is that their servers
run 64bit Linux, but the 32bit compatibility libraries are not installed.
I faced this problem, when trying to install my CMS which is written
in 32bit assembly language. (Now it runs OK: http://fresh.flatassembler.net )
Anyway, you probably need to compile fossil for 64bit or at least statically linked -
I am not sure how, because I don't know C/C++, but fossil ELF executable must not use
any shared libraries.

Of course you need to set properly .htaccess files as well in order to properly execute cgi scripts.

On Sun, 28 Oct 2012 10:52:46 -0600
Post by Chad Perrin
I have some need for Fossil on a shared host. My first pass at trying to
get it running a month or two ago, following the directions in the online
documentation for Fossil SCM, met with failure. Before I give it another
try, I thought it might make sense to ask for tips here.
The shared hosting provider in question is Bluehost. Are there some tips
and caveats that anyone can offer me for how to handle Bluehost in
particular to get Fossil running? I'll need the ability to push and pull
via HTTPS at least (both authenticated and "anonymous" pull access),
preferably also SSH, and of course the usual web access stuff as well
(wiki, issue tracker, source code browsing).
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
John Found
http://asm32.hopto.org
Chris Peachment
2012-10-28 20:05:11 UTC
Permalink
I've just this moment faced this problem. The Linux executable
available from www.fossil-scm.org does not run on Bluehost and
reports an error unable to find libz.so.1

As John Found says, it is a problem related to the 64 bit
environment and missing 32 bit libraries.

My solution was to work at the command line shell on my Bluehost
server to download the source using wget and then to use the
configure command:

./configure --with-openssl=none

because I do not use ssl.

This was followed by:

make

and then a copy of the fossil executable into a local bin directory
that is no my bash path.

I also had to run fossil rebuild on the repositories to have the
top line menu behave.
Post by John Found
The big problem with bluehost is that their servers
run 64bit Linux, but the 32bit compatibility libraries are not installed.
I faced this problem, when trying to install my CMS which is written
in 32bit assembly language. (Now it runs OK: http://fresh.flatassembler.net )
Anyway, you probably need to compile fossil for 64bit or at least statically linked -
I am not sure how, because I don't know C/C++, but fossil ELF executable must not use
any shared libraries.
Of course you need to set properly .htaccess files as well in order to properly execute cgi scripts.
On Sun, 28 Oct 2012 10:52:46 -0600
Post by Chad Perrin
I have some need for Fossil on a shared host. My first pass at trying to
get it running a month or two ago, following the directions in the online
documentation for Fossil SCM, met with failure. Before I give it another
try, I thought it might make sense to ask for tips here.
The shared hosting provider in question is Bluehost. Are there some tips
and caveats that anyone can offer me for how to handle Bluehost in
particular to get Fossil running? I'll need the ability to push and pull
via HTTPS at least (both authenticated and "anonymous" pull access),
preferably also SSH, and of course the usual web access stuff as well
(wiki, issue tracker, source code browsing).
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Chad Perrin
2012-10-30 01:38:16 UTC
Permalink
Post by Chris Peachment
I've just this moment faced this problem. The Linux executable
available from www.fossil-scm.org does not run on Bluehost and
reports an error unable to find libz.so.1
As John Found says, it is a problem related to the 64 bit
environment and missing 32 bit libraries.
Thanks to both of you for bringing the lack of 32b libs to my attention.
Hopefully it'll all work when I try compiling from source.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
Continue reading on narkive:
Loading...