On Aug 26, 2009, at 1:18 PM, James wrote:
> Richard,
> I have a few questions about Fossil, most of which I couldn't find
> an answer for on the website or in the Wiki:
> i) Running a Fossil server, could one have multiple repositories?
> With many different projects and repositories, being able to go
> through all of them at once without having multiple daemons/a
> different webserver running?
There are three ways to set up a Fossil server:
(1) Use the "fossil ui" or "fossil server" commands.
(2) Use the "fossil http" command with inetd or xinetd
(3) Run fossil from a two-line CGI script
With methods (1) and (2) you can only have a single repository per TCP
port. But there is no limit to the number repositories that can be
served with method (3).
See http://www.fossil-scm.org/fossil/doc/tip/www/selfhost.wiki for a
description of how the self-hosting repository for Fossil is set up,
including the exact text of the two-line CGI script used. The server
that hosts fossil also hosts 32 other fossil repositories - all on the
same TCP port.
> ii) When are you going to have an ability to ignore files? How does
> Fossil handle binary files?
What do you mean "ability to ignore files". Fossil will ignore any
file you don't tell it about. I don't understand...
Fossil handles binary files as easily as text files. In fact, fossil
doesn't make a distinction between the two. You will run into
problems if you try to merge branches in a binary file, but otherwise
everything should work just fine.
I personally keep all of my OpenOffice presentations for talks that I
give in a single fossil repository. These are binary files that range
in size from 0.5 to 5.0 megabytes. I develop presentations on my
desktop at my office. Then I "push" the repository to a server. Then
on my laptop, I "pull" the repository and present my slides. If while
on the road I make tweaks to slides (which seems to always happen) I
simple check-in the changes on my laptop while on the road (no
internet connection required) then "push" back my revisions when I
return home.
Fossil is not recommended for versioning CDROM images. But photo
jpegs, office documents, and other kinds of reasonably sized (less
than 10MB) binary files work just fine.
> iii) Could addressing internationalisation of the UI be put into the
> to-do list? Whilst personally this may not seem like of a benefit to
> you, I think down the line if you've given out Fossil so more people
> can help and use it, then it would be a great help.
We are happy to accept patches in this area. Begin a monolingual
English speaker, I'm afraid I won't be of my help.
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
