Re: Shopping for a wiki
On 30 Dec 2009 at 20:05, Trent Shipley wrote: > What is a "web" in this context. It sounds like there is an effective > limit of 20,000 pages per named wiki instance (a web), but that the > Foswiki engine can support multiple wikis. A "web" is the top level hierarchial organisation. Each major project would be part of a web - at a minimum, Scifi and Fantasy would be their own webs. The default setup is for the sidebar to link to each web, but i can also be done as a topbar or other configurations. AndrewC ___ http://mccmedia.com/mailman/listinfo/brin-l_mccmedia.com
Re: Shopping for a wiki
Andrew Crystall wrote: > On 29 Dec 2009 at 22:22, Trent Shipley wrote: > > > See above answers. > > There's an effective page limit per-web (20,000), but you are not > limited in the number of webs and users you can create. > > The biggest? Probably Google or Nokia's installs. (Foswiki is the > direct successor of Twiki, having taken along basically all the core > devs except two) > > AndrewC > > ___ > http://mccmedia.com/mailman/listinfo/brin-l_mccmedia.com > > What is a "web" in this context. It sounds like there is an effective limit of 20,000 pages per named wiki instance (a web), but that the Foswiki engine can support multiple wikis. Now we will be extremely lucky to get 20,000 pages, but if we get 20,000 pages we will get way more than 20,000 pages. The customers will want to see a unified image of the site. What happens if we get 60,000 pages? ___ http://mccmedia.com/mailman/listinfo/brin-l_mccmedia.com
Re: Shopping for a wiki
On 29 Dec 2009 at 22:22, Trent Shipley wrote: > The potential participant says he hates MediaWiki because it was > designed with a flat user model. It has no built in hierarchy and we No, I hate it because it's basically the lowest common denomiator of wiki-dom. It does a lot of things, but it's a pain in the ass in some ways for them all. Also, it handles authentication very very badly indeed (and in an extremely blunt manner), and that is going to be necessary. > I have a database background, the news that Foswiki does NOT use a RDBMS > as a back end set off all kinds of alarms. Fos(T)wiki is used in some pretty big corperate installs. The only real kicker is that if you're using a really (50,000 page+) wiki you're going to want to use a search engine and not the inbuilt search. There's an inbuilt cache engine, several additional cache engines avaliable and you can even load-balance if you need to. The cache engine is currently being re-written for the next major release, too. >1. Is Foswiki a good candidate for our encyclopedia project? I'd argue so. >2. How do you store your data? Flat file. >3. Why is your storage as reliable as MySQL? Foswiki is considered *extremely* reliable. It's primary goal is for enterprise usage. >4. How do I back up your wiki? You can do a straight file copy, or generate single backup files using a plugin, of either the entire wiki or of individual webs within it. >6. Can I run 24/7/365? Major (Fortune 500) companies do with Foswiki. >7. Our project leader is not only talented technically, he is a good > marketer. We plan to be _very_ successful. How does Foswiki > scale? What is the biggest Foswiki wiki today? See above answers. There's an effective page limit per-web (20,000), but you are not limited in the number of webs and users you can create. The biggest? Probably Google or Nokia's installs. (Foswiki is the direct successor of Twiki, having taken along basically all the core devs except two) AndrewC ___ http://mccmedia.com/mailman/listinfo/brin-l_mccmedia.com
Shopping for a wiki
I am with a little group of science fiction fans. We are looking at starting a science fiction wiki with synopses, reviews, literary criticism, and above all trivia. We have a big vision for the site since Wikipedia won't let us put our trivia there and it annoys us. So basically the vision is for an encyclopedia, but different content from Wikipedia. The obvious choice is MediaWiki. One potential participant writes, "I hate MediaWiki and will not participate as a technician if you use it." Fine, so we ask him why he doesn't like it and to pick anything he likes as long as it uses either MySQL or Postgresql on the back end. The potential participant says he hates MediaWiki because it was designed with a flat user model. It has no built in hierarchy and we will want hierarchy. He also says he *LOVES* Foswiki. Oh one little thing, it uses a flat file back end, but no worries it will scale. I have a database background, the news that Foswiki does NOT use a RDBMS as a back end set off all kinds of alarms. Nevertheless, Foswiki is a strong candidate to be the engine for our project. - 1. Is Foswiki a good candidate for our encyclopedia project? 2. How do you store your data? 3. Why is your storage as reliable as MySQL? 4. How do I back up your wiki? 5. I think I can extract data from MediaWiki as MySQL SQL scripts that are almost portable. Can I do something similar with Foswiki? 6. Can I run 24/7/365? 7. Our project leader is not only talented technically, he is a good marketer. We plan to be _very_ successful. How does Foswiki scale? What is the biggest Foswiki wiki today? ___ http://mccmedia.com/mailman/listinfo/brin-l_mccmedia.com
