Re: [fossil-users] Providing fossil as a vcs, wiki or blog for 'users'
On Nov 13, 2011, at 10:33 PM, Julian Fagir wrote: For people who dislike fossil as a wiki or vcs, there are still other solutions, but they're not automated, so that wouldn't stop me. So, my question: Do you think fossil is appropriate? As a vcs yes. The ticketing system needs some setup to fit my taste, but that's not hard. But, sadly, the wiki is way too simplistic to be practical. But this probably will be resolved one day. As I said, I'm relatively new to fossil, and may not have tried out all features. Would you have security concerns about that? Nope, Fossil is not dangerous to the machine it runs on. You can put it into chroot to feel extra safe in case of security breach. And do you have any suggestions what might help me with that? Are there standard settings you would suggest? Look into WAL mode for the database. Kind regards, Remigiusz Modrzejewski ___ 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] Providing fossil as a vcs, wiki or blog for 'users'
On Wed, Nov 16, 2011 at 12:29 PM, Remigiusz Modrzejewski l...@maxnet.org.pl wrote: As a vcs yes. The ticketing system needs some setup to fit my taste, but that's not hard. But, sadly, the wiki is way too simplistic to be practical. But this probably will be resolved one day. Actually the JSON API is far enough along that a completely custom wiki could be based on it, using one's own custom wiki syntax, provided a client-side renderer is available for it. The user management and wiki APIs are feature-complete enough to support this, and implementing a proof-of-concept for this is on my (long) list of TODOs for the JSON API. The only (IMO) significantly missing feature in this area is the ability to get historical versions of the wiki pages - currently we only serve the latest version in the JSON API (fixing that is of course also on the TODO list). As I said, I'm relatively new to fossil, and may not have tried out all features. Would you have security concerns about that? Nope, Fossil is not dangerous to the machine it runs on. You can put it into chroot to feel extra safe in case of security breach. i'll second that heartily. Fossil requires no special privileges, and can run as an arbitrary unprivileged user provided that user has access to the repo file and the dir containing it. -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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] Providing fossil as a vcs, wiki or blog for 'users'
On Nov 16, 2011, at 4:11 PM, Stephan Beal wrote: As a vcs yes. The ticketing system needs some setup to fit my taste, but that's not hard. But, sadly, the wiki is way too simplistic to be practical. But this probably will be resolved one day. Actually the JSON API is far enough along that a completely custom wiki could be based on it, using one's own custom wiki syntax, provided a client-side renderer is available for it. The user management and wiki APIs are feature-complete enough to support this, and implementing a proof-of-concept for this is on my (long) list of TODOs for the JSON API. The only (IMO) significantly missing feature in this area is the ability to get historical versions of the wiki pages - currently we only serve the latest version in the JSON API (fixing that is of course also on the TODO list). Actually, I'm not sure if that's that good idea. This way you can bring client incompatibility, unless you mean writing in a better markup, but saving (and loading from) the plain Fossil thingy. It surely can be done, just is not as trivial as we'd like it to be. Kind regards, Remigiusz Modrzejewski ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] A little self-promotion
Hi all, Just been preparing a project site based on fossil and wonder why fossil is by default so humble to not include a link to its web site in the footer. Basically, I'd change this: div class=footer Fossil version $release_version $manifest_version $manifest_date /div /body/html to: div class=footer a style=color:white;text-decoration:none href=http://fossil-scm.org; target=_blankFossil/a version $release_version $manifest_version $manifest_date /div /body/html or perhaps some version that uses CSS. It shouldn't hurt anyone and even make life a little bit easier for users, I believe. Best, Jacek ___ 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] A little self-promotion
On Wed, Nov 16, 2011 at 4:15 PM, Jacek Cała jacek.c...@gmail.com wrote: and wonder why fossil is by default so humble to not include a link to its web site in the footer. Maybe to encourage users to contact their project leader first? In my team, I've been handling the questions. ___ 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] A little self-promotion
On 11/16/11 4:11 PM, Ron Wilson wrote: On Wed, Nov 16, 2011 at 4:15 PM, Jacek Całajacek.c...@gmail.com wrote: and wonder why fossil is by default so humble to not include a link to its web site in the footer. Maybe to encourage users to contact their project leader first? In my team, I've been handling the questions. For public-facing repos, this is a great idea. It's like how Wordpress has its link at the bottom of the default theme, a cheap and easy way to bring more people to the project. I'm not sure if anyone would actually be confused about whose project it is, just by the presence of that link. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Nested check-outs
Howdy! Is there a document that describes the best practices for a project that involves components from multiple fossil repositories? For example, suppose I've got an infrastructure library that is in its own fossil repository. And I've got an application that uses that infrastructure library. With Subversion, I'd do an svn:external to pull the infrastructure library into my working area as a subdirectory. Is there an equivalent way to do this with fossil that won't get me into trouble? Thanks very much! Will Mr. Will Duquette, OP will -at- wjduquette dot com http://foothills.wjduquette.com/blog ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
