What Are You Using? - Cerntalized Place for Creating, Storing, Accessing and Displaying Network/Systems Documentation
-
@RamblingBiped That looks pretty interesting. It runs its own web server then? Is it database based or file system based?
-
@scottalanmiller said:
We use Sharepoint. On Sharepoint we use the wiki, database list and OneNote functionalities to do this.
We have used in the past and I highly recommend MediaWiki (or similar) as well.
Same story here, except mediawiki
-
@scottalanmiller said:
@RamblingBiped That looks pretty interesting. It runs its own web server then? Is it database based or file system based?
Looks like it's JSON.
-
@johnhooks said:
@scottalanmiller said:
@RamblingBiped That looks pretty interesting. It runs its own web server then? Is it database based or file system based?
Looks like it's JSON.
JSON wouldn't be a viable option
But that link points to them being files, so filesystem based. JSON is used as the configuration format on the config file.
-
@scottalanmiller said:
@johnhooks said:
@scottalanmiller said:
@RamblingBiped That looks pretty interesting. It runs its own web server then? Is it database based or file system based?
Looks like it's JSON.
JSON wouldn't be a viable option
But that link points to them being files, so filesystem based. JSON is used as the configuration format on the config file.
Ah I read through quickly and it looked like the tidllerfiles were only JSON. It looks like they can be either JSON, HTML, .tid, or .tiddler ( which is a weird mix of <div> and not).
-
@scottalanmiller said:
@RamblingBiped That looks pretty interesting. It runs its own web server then? Is it database based or file system based?
I'm pretty sure it is file based. The portability, security, and flexibility to use wiki-text or strait HTML/CSS is what I like about it. No frills light-weight place to store documentation. The file lives in a single infrastructure documentation directory and all of the files/images/media I associate with any specific document is contained in and referenced from sub-directories within the documentation directory. Anytime you update or change anything within the wiki a new file is generated and you'll either need to copy over the existing file in your documentation directory, or move it to a new directory. If you combined it with some type of version control (GIT/SVN/Mercurila/etc...)you could easily maintain and track changes to documentation overtime. I don't personally do this because I'm the primary (only) user of this specific wiki so i don't necessarily need it. However, if I had more than one person accessing/updating it I would probably have it living in a repository to track changes.
-
A lot like pmWiki, we used that for a while. How is the user management in it?
-
That this runs on Node.js is a nice sign.
-
@scottalanmiller said:
A lot like pmWiki, we used that for a while. How is the user management in it?
The version I am using has no user management. It is encrypted and password protected, but there is no user component. That isn't saying someone hasn't written a user management plug-in of some sort.
-
@scottalanmiller And a quick google shows it is so: http://www.minormania.com/tiddlylock/tiddlylock.html
-
That's locking, which is good, but what about authentication and authorization?
-
@scottalanmiller Yeah, not sure it has that much complexity built-in currently.
-
They tout is as more of a replacement for OneNote rather than a replacement for MediaWiki, which is great for a single user, but for a team something more robust is necessary.
-
Or at very list, single editor. Could be many readers.
-
@scottalanmiller said:
Or at very list, single editor. Could be many readers.
I've been using it for a little over a year now and it has worked great for my purposes. For a one person shop I think it is ideal.
