wget https://www.wikifeat.com/api/v1/wikis/686243fa4392400aad390cc59fa0987b/files/222361ead18c40e880b57d386c5a563e/content?attName=wikifeat_0.2.0-alpha.Linux-x86_64.tar.gz | tar xvz

--2015-11-25 21:48:09--  https://www.wikifeat.com/api/v1/wikis/686243fa4392400aad390cc59fa0987b/files/222361ead18c40e880b57d386c5a563e/content?attName=wikifeat_0.2.0-alpha.Linux-x86_64.tar.gz
Resolving www.wikifeat.com (www.wikifeat.com)... 104.131.164.61
Connecting to www.wikifeat.com (www.wikifeat.com)|104.131.164.61|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20040381 (19M) [binary/octet-stream]
Saving to: ‘content?attName=wikifeat_0.2.0-alpha.Linux-x86_64.tar.gz.1’

content?attName=wikifeat_0.2.0-alpha.Linux-x 100%[=============================================================================================>]  19.11M  1.72MB/s   in 14s    

2015-11-25 21:48:24 (1.33 MB/s) - ‘content?attName=wikifeat_0.2.0-alpha.Linux-x86_64.tar.gz.1’ saved [20040381/20040381]


gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now

The Wikifeat web client currently uses the showdown markdown editor (used on Stack Exchange, etc.). This was quick to integrate and provided some improvement over a plain HTML textarea. There are a few issues with it, however, that may warrant replacement (or a fork):

~~1. The preview pane uses it's own markdown parser, which behaves slightly differently (it apparently implements a slightly different dialect of Markdown) from the Commonmark parser on the backend, which can cause published results to not match the live preview.~~ Brought in commonmark.js to render markdown in the preview pane.

1. The 'insert image' button takes a url. When attaching an image which is already on the wikifeat site (in the 'files' section), this is inconvenient. Implementing a nice image browser/selector would be the preferred solution.
2. A method to insert 'download' links for files on the wikifeat system would be highly desirable here.
3. The preview pane doesn't render plugins

The User settings menu item does nothing. Allow users to edit their profiles (contact info, etc). As part of the user profile, implement user pictures/avatars. Consider implementing Gravatar support as well.

Also, the various username links that currently lead nowhere should display user profiles.

Right now, wikifeat-config loads the configuration parameters from the config.ini file into etcd and then terminates. Need an actual config REST service so that certain configuration parameters may be queried. Eventually this config service could be extended to allow on-the-fly config changes.

Travis CI continues to produce inconsistent results. The occasional network timeout causing failed unit tests seems to be the main issue (Usually retrying a build corrects this, when that particular Travis feature happens to be working). Adding copious sleep/wait statements and extending the length of http.Client timeouts has helped some, but the issue persists.

It may be necessary to find an alternative CI. I am tempted to just setup a Jenkins instance on a VPS somewhere.

This is necessary to allow for adding custom authentication modules (LDAP, etc.). Will need to stop using the CouchDB Session API as it is not flexible enough, and implement Session management outside of CouchDB.

The solution to allowing external authentication methods appears to be a combination of handling session management in the middleware (rather than letting CouchDB do this for us), and using CouchDB's Proxy Authentication feature.

Authorization will still take place in CouchDB using CouchDB's role based access (read, write, admin). Thus, an entry in the '_users' database will still need to be created (and synced) for users authenticating against external services (LDAP).

Allow users to specify the content of a meta-description tag in the frontend config.ini. Right now the only way to accomplish this is to manually add a meta-description tag to the index.html file in the web app.

While the browser back button works for navigating within the application, it's a real pain to back out of the web application altogether. I believe this problem is being caused by the 'home page' being pushed to the Backbone.history after the application has loaded.

While working on the API documentation, I noticed a couple of inconsistencies in some of the JSON data structures. For example, "created_at" vs "createdAt", etc. Minor stuff.

Better to fix sooner rather than later.

In the file manager view, when not logged in (guest mode), file download links are not displayed correctly. If you have a link, it works (i.e., the links on the wikifeat.com 'Downloads' page work just fine), this affects the file manager view specifically.

In the Wikis menu in the sidebar, wikis with guest access disabled will appear in the listing when using Wikifeat in guest mode. Even though the guest cannot access these wikis, it would be best if they were not able to see them.

Simple fix, this.

Fetching Configuration from http://localhost:2379 2020/07/24 11:31:19 Error getting key DbAddr: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key DbPort: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key UseSSL: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key DbAdminUser: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key DbAdminPassword: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key DbTimeout: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key MainDb: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key LogFile: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key MaxSize: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key MaxBackups: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key MaxAge: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key EntryTTL: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key CacheRefreshInterval: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key WebAppDir: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key PluginDir: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key Homepage: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key Authenticator: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key SessionTimeout: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key PersistentSessions: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key AllowGuest: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key AllowNewUserRegistration: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. 2020/07/24 11:31:19 Error getting key MinPasswordLength: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint. [Poetry.plugin] name=Poetry author=Wikifeat stylesheet=style/poetry.css version=1.0 pluginDir=plugins/poetry mainScript=poetry-plugin.js enabled=false [OpenLayers.plugin] name=OpenLayers author=Wikifeat stylesheet=style/ol.css version=1.0 pluginDir=plugins/ol mainScript=ol-plugin.js enabled=false 2020/07/24 11:31:19 Initializing Database Connection client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint.

When a Wikifeat system is backed by multiple instances of CouchDB, the possibility of conflicting document versions exist. CouchDB "resolves" this upon replication by storing both versions on each node, and just 'picking' a winner to present in response to a read request (supposedly this is a deterministic process so the same winner is consistently returned on all nodes).

Need to allow users (those with write access to a particular wiki, anyway) to participate in resolving conflicts (i.e., merging the conflicting versions into a 'new' one). CouchDB does allow you to query for conflicting document versions on a read, which will be helpful.

The solution should go something like this:

1. In the UI, place an 'alert' box at the top of a document if an unresolved conflict exists (Possibly limit this to users with 'write' access) along with a clickable 'resolve now' link.
2. When clicked, the UI presents a 'merge' view containing a side-by-side diff of the two versions (similar to the merge tools in many SCM GUI tools).
3. The user merges the two documents and saves the result
4. The old versions are added to the history, with the new 'merged' version becoming the current document revision.
5. User rejoices.

Two parts to this:

1.) Generate thumbnails for images as they're uploaded. 2.) Implement a thumbnail gallery in the "Insert Image" dialog in the page editor.