So the idea here is to see if we can get DreamFactory to fulfil the basic Fedwiki Server Requirements, which essentially means serving json files, a favicon and a sitemap via HTTP GET.
# To do - [x] Add Favicon route to Nginx - [x] Point domains to IP adress (Trevor's droplet) - [x] Add CORS Headers for Wiki - [ ] DreamFactory IPFS Service - [ ] Add Let's Encrypt certificate - [ ] Proxy Livecode Server behind Nginx - [ ] DreamWiki using Dockers - [ ] Explore DreamFactory Security
The core url's that DreamFactory must respond to in order to display wiki content (ie json files) are:
http://example.com/(slug).json http://example.com/favicon.png
In addition, if the site is to be searchable and display links to newer, or later pages etc Dreamfactory must also serve a json sitemap under the following url:
http://example.com/system/sitemap.json
# Loading wiki client
The above functionality will provide a readable wiki, that can full participate in the federation - all though it will not load the javascript wiki client when visiting the TLD for the first time.
Therefore someone wanting to view the wiki content must first visit another wiki first to load the wiki client. from there on in, the wiki client will fetch json files using CORS based HTTP GET requests to whichever server it needs (for example the DreamFactory Wiki server.
Issue: It may not be possible to turn off all authentication for HTTP GET requests without simply getting Nginx to redirect. An api-key may be required in the url - see dreamfactory.com
DreamFacory Wiki Research
Below are a collection of links imported from OneTab. You can view these links here - one-tab.com:
# Plugins
Non core wiki plugins would not be rendered with this setup however. This may not be a problem. However adding the functionality to serve the javascript needed for the wiki client to render paragraph items using a plugin is not much harder to achieve - see Fedwiki Server Requirements.
# Authoring wiki pages
It is not proposed that the DreamFactory Wiki would allow the current fedwiki client to author wiki content. It would be a Read-only Wiki as far as the fedwiki client was concerned.
Suggestion:
It would be nice if the current wiki client was enhanced to display this in the browser - that is distinguish between read-only and writeable wiki's.
This functionality could have other uses. It would also allow the possibility of creating a link to alternative authoring platforms if they were available. DreamFactory Wiki for instance could offer it's own REST based authoring interface.
# See also - Alternative Wiki View - Nginx - DevOps - Custom CSS