In the SF Wiki Helper script git diff
is used to determine what you have changed in comparison to the current on-line content of your wiki. In order to be able to do so, the contents of your master
branche (or any other name you use for your default branch) should match exactly the current on-line content of your wiki.
With the following commands you can list all relevant changes to files in your working directory compared to the master
branch:... read more
When you query a wiki page with the Allura REST API, you receive a JSON representation of the requested page. To parse JSON from a shell I could find two good alternatives: jq
and the Python json
library.
I did some initial tests and I found a problem with jq
getting the markdown text. The default output looked OK, but the raw output, that I actually needed, looked like gibberish. With Python I immediately got the right output, so I decided to stick with Python.... read more
I like to document my work well. SourceForge in itself is already a CMS, so for my pet projects I do not see the need to set up another CMS on its hosting platform Project Web. Thus for documentation I just use the wiki tool. It is not very fancy, but it serves its purpose and doesn't distract me from writing my documentation.
But I have been struggling how to work on documentation that cannot be published yet because, for example, it is about features that have not been released yet. In the beginning I stored my changes in the history of the pages and restored them when they needed to be published. I actually made lists to keep track and not to forget to publish something.... read more