DOCSLIB.ORG

Lightweight Wikis Without Databases QUICKIE WIKIS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lightweight Wikis Without Databases QUICKIE WIKIS COVER STORY Lean Wikis Lightweight wikis without databases QUICKIE WIKIS If you are thinking about starting a wiki, and you don’t want the over- head of a full-scale, database-driven system, try these light and lean wiki wonders. BY FRANK WIEDUWILT ikis are at the center of the a wiki is only feasible if it uses flat files hits. However, if you’re thinking about world we know as Web 2.0. In to store content. getting started with your own wiki and Wjust a few short years, the wiki Luckily, a number of smaller and sim- you don’t need the horsepower of a has become one of the most popular pler wikis are also available for Linux high-end, database-driven system, a lean tools on the Internet, thanks to a few users. These lean wikis have some re- wiki may be exactly what you need. very high profile projects and many strictions of course: projects should not smaller sites that are helping millions of have more than a few hundred articles. The Candidates users communicate and stay organized. If the number of pages keeps growing, We will be looking at five wikis, Wikep- The wiki’s open approach, where any- you can can expect major performance age, PWP, MoinMoin, PmWiki, and one can post and edit, makes it the per- fect counterpart for another famous tool For Bigger Projects of the new Internet known as the blog. The wikis discussed in this article are not suitable for large-scale projects with several Wikis offer an easy and intuitive means thousand pages. If you expect a large volume of content, and would appreciate more for collecting and editing content. sophisticated user management features, you need a wiki with database support. If you are planning a large wiki with Mediawiki: Definitely the most popular wiki of them all, and the platform for the Wikipe- hundreds of users and thousands of dia online encyclopedia and its local derivatives. Mediawiki [2] uses MySQL as its data- pages, you’ll need a full-featured, data- base back-end. base driven wiki tool such as Mediawiki. Wikka Wiki: This project [3] also uses MySQL to store text. The software is also extensi- But a community the size of the Wikipe- ble by means of plugins, and this makes it suitable for projects where the scope is not dia [1] community is atypical. For more known right from the outset. moderate tasks, a full-fledged wiki sys- ErfurtWiki: This wiki [4] supports various databases, and can even use flat files as its tem with an underlying database may back-end. The advantage is that you can use plugins, skins, and extension modules to have more disadvantages than benefits. modify the wiki’s look and feel to match your requirements. Installing and managing the wiki is just The Wikimatrix [5] page lists a number of wikis with and without database back-ends, too complicated. And for free webspace, describing each system’s capabilities in a comprehensive overview. where a database may not be available, 30 ISSUE 73 DECEMBER 2006 WWW.LINUX - MAGAZINE.COM Lean Wikis COVER STORY Dokuwiki, all of which are under active community development. All of these projects promise simple installation, even for non-DBAs. In the simplest of cases, you just need to unpack the source code archive on the web server to run the wiki. Some systems support a customized look and feel based on tem- plates, macros, or plugin-based exten- sions. Access controls are an important issue. If you are looking to create a wiki for public access, the danger is that un- friendly web users or robots might stum- ble across your page and misuse it for propaganda or ads. The Tipiwiki [6] homepage is just one example of wiki misuse. In August 2006, the wiki was more or less completely inundates with ad links, leaving the pages unusable ex- Figure 1: The simple structure of Wikepage lends itself to quick deployment, though the cept for the welcome page. general lack of documentation slows down the creative process. While wikis like Mediawiki have so- phisticated user management facilities In Wiki mode, editing is open to any page to get the wiki up and running. You that rely on a database back-end and user. In Personal mode, users need to can use any text editor to modify the allow administrators to define distinct supply a password before editing a page. configuration. PWP uses CSS to format user groups with distinct privileges, the The password applies to all pages, how- screen output, and this makes it highly smaller wikis often have nothing of the ever, and there is no support for distinct customizable. kind. The wiki dialect used for markups user privileges. PWP does not support user manage- for tagging or linking is also an impor- The formating options range from var- ment, although the developers do pro- tant aspect. If you need to move to a ious text markups, through lists, to sim- vide password protection for a few large system some time later, it would be ple tables. The developers also let you functions, such as exporting wiki pages nice to know whether you can do so integrate images into wiki pages. The to static HTML. Lars Ackermann, PWP’s without having to redo the formating. wiki dialect differs considerably from author, recommends using the web that of Mediawiki; you can expect diffi- server’s access controls and restricting Wikepage culties with the process of exporting access to the wiki via the .htaccess file. The motto of the Wikepage [7] wiki is content to another wiki. PWP supports a variety of formating “unpack and go.” The package weighs in Unfortunately, Wikepage does not give options: text markups, indentation, ta- at just 38 Kbytes, and its author, Sefer users much in the line of howtos or bles, and images. Before you can use an Bora Lisesivdin, explains the reason for manuals: neither the homepage nor the image file, you first have to upload it to a the small size: in the good old days of source code archive provide descriptions special Uploaded Files area of the wiki. the Commodore 64, developers just had of the markups or a guide to creating The software will then let you link to the 38911 bytes of user space to work with, your own themes. image from any wiki page. The Uploaded but they still managed to come up with Files area can also store files in other for- functional programs. He promises to PWP mats for public access by any wiki user. keep the Wikepage to less than 38911 PWP [9] stores wiki pages in flat files The wiki has a version control system bytes, although he is working on a plu- and requires a web server with PHP ver- in which it stores all previous revisions gin interface. sion 4.2 or newer. If you are using PHP5, of the wiki pages. A diff tool shows the Wikepage is based on the Tipiwiki [6] the software requires PHP4 compatibility differences between two versions of a code and requires a web server running mode. Again, the basic configuration is page. A full text search against all the PHP 5.1.4 or better. To install the wiki, easily done with PWP: just unpack the pages in the wiki, including text pages you just unpack the program archive, source code archive and open the index uploaded to Uploaded Files, gives users and you’re up and running. Wikepage searching ability. supports themes, and you can even GLOSSARY PWP will generate reports for wiki change the interface language by copy- .htaccess: The .htaccess file gives pages. You can choose between hierar- ing a language file to the wiki’s root di- administrators the ability to control chical lists, tables, indexes of keywords, rectory. access to data on a web server. You'll or lists with the title and teaser for each Themes let you change the look, and find several tutorials on .htaccess files wiki page. PWP can create calendars at there are a number of examples that you on the web (e.g., http://httpd.apache. the push of a button with a page for can use for your experiments at [8]. org/docs/1.3/howto/htaccess.html). each month and an overview of the WWW.LINUX - MAGAZINE.COM ISSUE 73 DECEMBER 2006 31 COVER STORY Lean Wikis lists, and icons. MoinMoin also supports tables. MoinMoin is the only test candi- date to have a WYSIWYG style editor for composing wiki pages. The wiki also supports subpages. One thing worthy of note is that the system supports text en- tries in DocBook syntax and can even export wiki pages to DocBook. MoinMoin stores previous versions of a text as backups. The version control system supports access to the last 100 versions, and URLs let you access older versions. You can diff two versions and display the most recent edits. MoinMoin also provides an RSS feed of the latest edits. The developers give users powerful searching abilities that support page title or full-text searches, multiple operator-linked search keys, and Boolean expressions. The wiki also generate indexes of titles, words, and Figure 2: MoinMoin lets you track recent changes. categories. The selection of help texts and tutori- whole year. In a style similar to Medi- store texts. Macros and themes let you als is exemplary, with comprehensive, awiki, PWP generates a table of contents customize the look; the MoinMoin easy to understand howtos for any de- from primary and secondary headings at homepage has a collection of ready-to- ployment scenario.
Load more

Recommended publications
  • Ispconfig Documentation Ispconfig Documentation I
    ISPConfig Documentation ISPConfig Documentation I Table of Contents General...............................................................................................................................................1 1 What is ISPConfig?...............................................................................................................1 2 Terms and structure of the manual.......................................................................................1 3 Installation/Upgrade/Deinstallation.......................................................................................1 3.1 Installation....................................................................................................................1 3.2 Upgrade.......................................................................................................................1 3.3 Deinstallation................................................................................................................2 4 Login and Logout..................................................................................................................2 I Administrator Manual......................................................................................................................3 1 General.................................................................................................................................3 1.1 Login and Password.....................................................................................................3 1.2 ISPConfig Interface
    [Show full text]
  • Installation Guide
    install_guide.book Page i Monday, May 11, 2015 8:48 PM Installation Guide Installation Guide Schrödinger Software Release 2015-2 Schrödinger Press install_guide.book Page ii Monday, May 11, 2015 8:48 PM Installation Guide Copyright © 2015 Schrödinger, LLC. All rights reserved. While care has been taken in the preparation of this publication, Schrödinger assumes no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. Canvas, CombiGlide, ConfGen, Epik, Glide, Impact, Jaguar, Liaison, LigPrep, Maestro, Phase, Prime, PrimeX, QikProp, QikFit, QikSim, QSite, SiteMap, Strike, and WaterMap are trademarks of Schrödinger, LLC. Schrödinger, BioLuminate, and MacroModel are registered trademarks of Schrödinger, LLC. MCPRO is a trademark of William L. Jorgensen. DESMOND is a trademark of D. E. Shaw Research, LLC. Desmond is used with the permission of D. E. Shaw Research. All rights reserved. This publication may contain the trademarks of other companies. Schrödinger software includes software and libraries provided by third parties. For details of the copyrights, and terms and conditions associated with such included third party software, use your browser to open third_party_legal.html, which is in the docs folder of your Schrödinger software installation. This publication may refer to other third party software not included in or with Schrödinger software ("such other third party software"), and provide links to third party Web sites ("linked sites"). References to such other third party software or linked sites do not constitute an endorsement by Schrödinger, LLC or its affiliates. Use of such other third party software and linked sites may be subject to third party license agreements and fees.
    [Show full text]
  • Ispconfig 3 Manual]
    [ISPConfig 3 Manual] ISPConfig 3 Manual Version 1.0 for ISPConfig 3.0.3 Author: Falko Timme <[email protected]> Last edited 09/30/2010 1 The ISPConfig 3 manual is protected by copyright. No part of the manual may be reproduced, adapted, translated, or made available to a third party in any form by any process (electronic or otherwise) without the written specific consent of projektfarm GmbH. You may keep backup copies of the manual in digital or printed form for your personal use. All rights reserved. This copy was issued to: Thomas CARTER - [email protected] - Date: 2010-11-20 [ISPConfig 3 Manual] ISPConfig 3 is an open source hosting control panel for Linux and is capable of managing multiple servers from one control panel. ISPConfig 3 is licensed under BSD license. Managed Services and Features • Manage one or more servers from one control panel (multiserver management) • Different permission levels (administrators, resellers and clients) + email user level provided by a roundcube plugin for ISPConfig • Httpd (virtual hosts, domain- and IP-based) • FTP, SFTP, SCP • WebDAV • DNS (A, AAAA, ALIAS, CNAME, HINFO, MX, NS, PTR, RP, SRV, TXT records) • POP3, IMAP • Email autoresponder • Server-based mail filtering • Advanced email spamfilter and antivirus filter • MySQL client-databases • Webalizer and/or AWStats statistics • Harddisk quota • Mail quota • Traffic limits and statistics • IP addresses 2 The ISPConfig 3 manual is protected by copyright. No part of the manual may be reproduced, adapted, translated, or made available to a third party in any form by any process (electronic or otherwise) without the written specific consent of projektfarm GmbH.
    [Show full text]
  • Internet Domain Name System
    IINNTTEERRNNEETT DDOOMMAAIINN NNAAMMEE SSYYSSTTEEMM http://www.tutorialspoint.com/internet_technologies/internet_domain_name_system.htm Copyright © tutorialspoint.com Overview When DNS was not into existence, one had to download a Host file containing host names and their corresponding IP address. But with increase in number of hosts of internet, the size of host file also increased. This resulted in increased traffic on downloading this file. To solve this problem the DNS system was introduced. Domain Name System helps to resolve the host name to an address. It uses a hierarchical naming scheme and distributed database of IP addresses and associated names IP Address IP address is a unique logical address assigned to a machine over the network. An IP address exhibits the following properties: IP address is the unique address assigned to each host present on Internet. IP address is 32 bits 4bytes long. IP address consists of two components: network component and host component. Each of the 4 bytes is represented by a number from 0 to 255, separated with dots. For example 137.170.4.124 IP address is 32-bit number while on the other hand domain names are easy to remember names. For example, when we enter an email address we always enter a symbolic string such as [email protected]. Uniform Resource Locator URL Uniform Resource Locator URL refers to a web address which uniquely identifies a document over the internet. This document can be a web page, image, audio, video or anything else present on the web. For example, www.tutorialspoint.com/internet_technology/index.html is an URL to the index.html which is stored on tutorialspoint web server under internet_technology directory.
    [Show full text]
  • Assignment of Master's Thesis
    ASSIGNMENT OF MASTER’S THESIS Title: Git-based Wiki System Student: Bc. Jaroslav Šmolík Supervisor: Ing. Jakub Jirůtka Study Programme: Informatics Study Branch: Web and Software Engineering Department: Department of Software Engineering Validity: Until the end of summer semester 2018/19 Instructions The goal of this thesis is to create a wiki system suitable for community (software) projects, focused on technically oriented users. The system must meet the following requirements: • All data is stored in a Git repository. • System provides access control. • System supports AsciiDoc and Markdown, it is extensible for other markup languages. • Full-featured user access via Git and CLI is provided. • System includes a web interface for wiki browsing and management. Its editor works with raw markup and offers syntax highlighting, live preview and interactive UI for selected elements (e.g. image insertion). Proceed in the following manner: 1. Compare and analyse the most popular F/OSS wiki systems with regard to the given criteria. 2. Design the system, perform usability testing. 3. Implement the system in JavaScript. Source code must be reasonably documented and covered with automatic tests. 4. Create a user manual and deployment instructions. References Will be provided by the supervisor. Ing. Michal Valenta, Ph.D. doc. RNDr. Ing. Marcel Jiřina, Ph.D. Head of Department Dean Prague January 3, 2018 Czech Technical University in Prague Faculty of Information Technology Department of Software Engineering Master’s thesis Git-based Wiki System Bc. Jaroslav Šmolík Supervisor: Ing. Jakub Jirůtka 10th May 2018 Acknowledgements I would like to thank my supervisor Ing. Jakub Jirutka for his everlasting interest in the thesis, his punctual constructive feedback and for guiding me, when I found myself in the need for the words of wisdom and experience.
    [Show full text]
  • Analyzing and Visualizing the Semantic Coverage of Wikipedia and Its Authors
    Holloway, Todd, Božicevic, Miran and Börner, Katy. (2007) Analyzing and Visualizing the Semantic Coverage of Wikipedia and Its Authors. Complexity, Special issue on Understanding Complex Systems. Vol. 12(3), pp. 30-40. Also available as cs.IR/0512085. Analyzing and Vis ualizing the S emantic C overage of Wikipedia and Its Authors Todd Holloway Indiana University Department of C omputer S cience 150 S . W oodlawn Ave. Lindley Hall 215 Bloomington, IN 47405, US A P hone: (812) 219-2815 E mail: tohollow@ cs.indiana.edu Miran Božievi Wikipedia Networks Team Multimedia Institute (http://www.mi2.hr) Preradovieva 18 HR-10000 Zagreb Croatia Email: [email protected] Katy Börner* Indiana University, SLIS 10th Street & Jordan Avenue Main Library 019 Bloomington, IN 47405, USA Phone: (812) 855-3256 Fax: -6166 E-mail: [email protected] WWW: http://ella.slis.indiana.edu/~katy * To whom all correspondence and proofs are to be addressed. Keywords Network analysis, link analysis, information visualization Number of text pages: 20 Number of figures: 6 Number of tables: 3 1. Introduction ................................................................................................................................................................3 1.1 Wiki Technology and Wikipedia............................................................................................................................3 1.2 Accuracy, Bias and Persistence ...........................................................................................................................4
    [Show full text]
  • Wikis with Moinmoin Wiki Creative Group Writing
    KNOW HOW MoinMoin Wiki Building wikis with MoinMoin Wiki Creative Group Writing The members of a project team can profit from collecting their ideas, or any loose ends, in a central repository. Wikis are tailor-made for this task. BY HEIKE JURZIK ay before content manage- ment systems started to Wappear for website manage- ment, Wikis provided a kind of “open door” to HTML pages, allowing any visi- tor to click and edit the HTML content. Wiki is the abbreviation for WikiWiki- Web – “wiki wiki” is derived from Hawaiian and means “quick” or “quickly”. And the open authoring sys- restored at any time, should a page be MySQL, Oracle, or PostgreSQL. The soft- tem certainly is quick. The MoinMoin deleted or damaged by mistake. Also, ware then uses this data to create the Wiki engine is one of the better-known wikis allow you to assign special access public HTML pages. implementations of this technology. controls that can restrict editing to regis- Besides taking a look at the original Users can click to launch the embed- tered users, if required. wiki, you might like to visit what is cur- ded editor and access the content and The first wiki website was published rently the biggest wiki on the Web, the structure of the page they want to mod- by Ward Cunningham in 1995, and it is Wikipedia [3], which offers innumerable ify. Typically, an Edit link is provided to still online [1]. At the time, Cunningham articles on pages in multiple languages. make things easier. wrote an email message saying that he It is an example of how well information In contrast to “real” HTML, which had programmed a new kind of database can be organized with a wiki.
    [Show full text]
  • A Wiki-Based Authoring Tool for Collaborative Development of Multimedial Documents
    MEDIA2MULT – A WIKI-BASED AUTHORING TOOL FOR COLLABORATIVE DEVELOPMENT OF MULTIMEDIAL DOCUMENTS Author Name * Affiliation * Address * Author Name * Affiliation * Address * * Only for Final Camera-Ready Submission ABSTRACT media2mult is an extension for PmWiki developed at our university. It provides functionality for embedding various media files and script languages in wiki pages. Furthermore media2mult comes with a cross media publishing component that allows to convert arbitrary wiki page sequences to print-oriented formats like PDF. This article gives an overview over the offered extensions, their functionality and implementation concepts. KEYWORDS wiki, multimedia, cross-media-publishing, authoring tool, XML 1. INTRODUCTION At least since the founding of the free web encyclopedia Wikipedia and its increasing popularity wiki web , wiki-wiki or just wiki are widely known terms in context of Web 2.0. However, their exact meaning often remains unclear. Sometimes wiki and Wikipedia are actually used synonymously. The crucial functionality of every wiki system is the possibility to edit wiki web pages directly inside a browser by entering an easy to learn markup language. Thus, manual uploads of previously edited HTML files are superfluous here. The user doesn't even have to know anything about HTML or external HTML editors. The browser- and server-based concept makes it possible that several authors can edit and revise common documents without the necessity of exchanging independently written and updated versions. Because most wiki systems offer an integrated version management system, authors can easily merge their changes and revert selected passages to former stages. Thus, accidentally or deliberately applied changes of protected or publicly accessible wiki pages can be taken back in a second.
    [Show full text]
  • Developing a Web 2.0-Based System with User-Authored Content for Community Use and Teacher Education
    Education Tech Research Dev DOI 10.1007/s11423-009-9141-x RESEARCH Developing a Web 2.0-based system with user-authored content for community use and teacher education Lauren Cifuentes • Amy Sharp • Sanser Bulu • Mike Benz • Laura M. Stough Ó Association for Educational Communications and Technology 2009 Abstract We report on an investigation into the design, development, implementation, and evaluation of an informational and instructional Website in order to generate guide- lines for instructional designers of read/write Web environments. We describe the process of design and development research, the problem addressed, the theory-based solution, and the evaluation and testing of that solution. Based on our experience, we then identify sixteen guidelines for future designers and developers of read/write Web-based learning environments. The study demonstrates how read/write Web technologies can be used to address general problems that have intrinsic societal importance; examines implementation of a read/write technology in a real-life context, thereby testing distributed cognitions learning theory; informs the design of similar environments; and provides grounded theory for the design and development of read/write Web learning environments. Keywords Design and development research Á Read/write Web Á Web 2.0 Á Distributed cognitions Á Social constructivism The emergence of read/write Web (Web 2.0) technologies such as wikis, Weblogs, Real Simple Syndication, Webcasts, and interactive photo galleries, has empowered users to actively contribute to the content of the Internet. By 2003, 44% of adult Internet users had participated in the interactive capabilities of the Internet by posting in at least one read/ write Web environment (Lenhart et al.
    [Show full text]
  • Wikis in Libraries Matthew M
    Wikis in Libraries Matthew M. Bejune Wikis have recently been adopted to support a variety of a type of Web site that allows the visitors to add, collaborative activities within libraries. This article and remove, edit, and change some content, typically with­ out the need for registration. It also allows for linking its companion wiki, LibraryWikis (http://librarywikis. among any number of pages. This ease of interaction pbwiki.com/), seek to document the phenomenon of wikis and operation makes a wiki an effective tool for mass in libraries. This subject is considered within the frame- collaborative authoring. work of computer-supported cooperative work (CSCW). Wikis have been around since the mid­1990s, though it The author identified thirty-three library wikis and is only recently that they have become ubiquitous. In 1995, Ward Cunningham launched the first wiki, WikiWikiWeb developed a classification schema with four categories: (1) (http://c2.com/cgi/wiki), which is still active today, to collaboration among libraries (45.7 percent); (2) collabo- facilitate the exchange of ideas among computer program­ ration among library staff (31.4 percent); (3) collabora- mers (Wikipedia 2007b). The launch of WikiWikiWeb was tion among library staff and patrons (14.3 percent); and a departure from the existing model of Web communica­ tion ,where there was a clear divide between authors and (4) collaboration among patrons (8.6 percent). Examples readers. WikiWikiWeb elevated the status of readers, if of library wikis are presented within the article, as is a they so chose, to that of content writers and editors. This discussion for why wikis are primarily utilized within model proved popular, and the wiki technology used on categories I and II and not within categories III and IV.
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Research Article Constrained Wiki: the Wikiway to Validating Content
    Hindawi Publishing Corporation Advances in Human-Computer Interaction Volume 2012, Article ID 893575, 19 pages doi:10.1155/2012/893575 Research Article Constrained Wiki: The WikiWay to Validating Content Angelo Di Iorio,1 Francesco Draicchio,1 Fabio Vitali,1 and Stefano Zacchiroli2 1 Department of Computer Science, University of Bologna, Mura Anteo Zamboni 7, 40127 Bologna, Italy 2 Universit´e Paris Diderot, Sorbonne Paris Cit´e, PPS, UMR 7126, CNRS, F-75205 Paris, France Correspondence should be addressed to Angelo Di Iorio, [email protected] Received 9 June 2011; Revised 20 December 2011; Accepted 3 January 2012 Academic Editor: Kerstin S. Eklundh Copyright © 2012 Angelo Di Iorio et al. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. The “WikiWay” is the open editing philosophy of wikis meant to foster open collaboration and continuous improvement of their content. Just like other online communities, wikis often introduce and enforce conventions, constraints, and rules for their content, but do so in a considerably softer way, expecting authors to deliver content that satisfies the conventions and the constraints, or, failing that, having volunteers of the community, the WikiGnomes, fix others’ content accordingly. Constrained wikis is our generic framework for wikis to implement validators of community-specific constraints and conventions that preserve the WikiWay and their open collaboration features. To this end, specific requirements need to be observed by validators and a specific software architecture can be used for their implementation, that is, as independent functions (implemented as internal modules or external services) used in a nonintrusive way.
    [Show full text]