This page is about the current and future of Fedwiki servers. The current reference implementation in Node can be found here on gitbub 
Goals
Federated wiki's single-page application reads page content from many sources and writes updates to a few. Read-write server backends are maintained in ruby (sinatra) and node (express). Read-only servers have been realized with static files and cgi scripts. Encouraging experiments have exploited exotic service architectures such as CCNx content-addressable networks.
Structure
The Fedwiki Server is made up of a wiki-node-server module and a bunch of Plugins (packaged as individual Node Modules.
The following options are worth looking into further:
Alongside creating native Android and iOS Wiki App in LiveCode we will look to engage a community in creating a test server in Livecode.
Such a server provides pages without taking responsibility for the client-side ... Federated wiki servers provide additional endpoints used by the client-sideÊ...
Here we list the minimum requirements for a Fedwiki Server:
Batch scripts can convert static content into federated wiki compatible json and serve it with apache.
Here we make a start to document the creation of a minimal Fedwiki Server that provides a minimal but fully specified REST API for both existing clients and future mobile clients.
See also.
THe aim of a future hosting infrastructure for Fedwiki Server software should separate concerns:
Assuming you are using the install from the One Line Installation Script then the logs will be in:
The server that delivers the client-side javascript that starts you browsing the federated wiki is called the Origin Server. It's special.
*Much of the content here is also applicable when installing Federated Wiki on other ... We will use this `wiki` account to run our Federated Wiki server later. help.