On Sun, Nov 13, 2011 at 6:39 AM, ST <smn...@gmail.com> wrote: > Hi, > > I'm new to fossil and have several questions: > > 1) how do I open new tickets on fossil-scm.org? I didn't see something > like "new ticket" on the web UI... >
Anonymous ticketing was turned off because it was being flooded with support requests, rather than actual bug reports. For example, if it had been turned on, you probably would have written a bug report for this very question, wouldn't you? We prefer to reserve tickets for reporting actual malfunctions, and so on fossil-scm.org, we require a username/password in order to write a new ticket. That goes a long way toward keeping down the noise. It has been suggested that we create a "hold for moderation" system for tickets, such that anonymous tickets can be input, but do not actually go into the system until approved by a registered user. That would allow random passers-by on the internet to write tickets, but would also let us filter the tickets to keep real bug reports and discard support requests, "test tickets", and spam. I'll probably add a moderator system at some point, when I get a chance, if somebody else doesn't volunteer to do it first. But it isn't available right this moment. Sorry. > > 2) why do I have to do this > http://www.fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki > manually? Shouldn't this be there out of the box? It's kind of basic > functionality that one finds in any ticket tracking app... > It is there out-of-the-box. The page above merely shows you how to modify the default setup, in case you want to do something a little different from what the out-of-the-box configuration does. > > 3) as far as I understand if one accidentally starts fossil > server/fossil ui - it will provide insecure access to the repository > even if one had configured inetd/stunnel/fossil to use SSL, right? Is > there a way to avoid such situations and force fossil to always use SSL? > "fossil ui" binds to 127.0.0.1 only, so it is not accessible from other machines on the network. If you do "fossil server" then your repository will be accessible remotely (on port 8080 by default) but people still need to know user names and passwords in order to log in. But it seems rather difficult to "accidently" run "fossil server", no? How do you accidentally start a server? > > 4) what happens if one autosync/pull/push from a remote repository, does > it also expose the local repository as in 3) ? > If you "fossil push" then information is transferred from the local repo to the remote repo. That's what "fossil push" is suppose to do. Fossil push/pull/sync does not activate the server mode, if that is what you are asking. > > thank you very much, > ST > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- 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
