On Wed, Nov 16, 2011 at 12:29 PM, Remigiusz Modrzejewski <[email protected] > 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 [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
