Post #443,571
10/21/23 9:22:40 AM
10/21/23 9:22:40 AM
|
Thinking about DokuWiki...
We run a locked-down version of MS Teams at work. Originally it came with a (limited, brain-dead) Wiki functionality that we've used for easily editable documentation, notes, etc., not a lot but it's been useful. Of course, it's impossible to print a page from the Wiki (without doing a screen capture), no export, cut-and-paste into Word kinda works with a lot of manual intervention, etc., etc. The usual MS annoyances. So, of course, it is going to be ripped out by the powers that be. :-/ I'm thinking about putting DokuWiki on a new NAS so that we have control over it. I like the idea of the stuff being stored in text files. And it seems simple enough. All access will be internal or via VPN through our (very strong) firewall. https://download.dokuwiki.org/ - I would grab the version with the mini-web-sever ("on a stick"). Any other Wikis that I should investigate instead? Tips, cautions, etc.? Thanks. Cheers, Scott.
|
Post #443,572
10/21/23 10:49:13 AM
10/21/23 10:49:13 AM
|
A couple of concerns
The lockdown of Teams implies the existence of a security group. Any idea what their tolerance is for plugging unknown equipment annex a web server into the production network?
The "on a stick" web server is intended for a single user. The backend seems to be SQLite. The current version does support concurrent thread writes, but I suspect performance may heavily depend on how the web server handles write requests.
The microApache webserver is a stripped down Apache homebrewed by the DocuWiki crew. The Github page has little practical information regarding its configuration, but the project it is based on (abandoned ~2011) came with a warning that the security configuration might be too lax beyond the single user scenario (i.e. it was set up to make it easy to get things going.) If confidentiality across the enterprise is a concern, that may need tightening down regardless of concern #1.
|
Post #443,573
10/21/23 11:48:37 AM
10/21/23 11:48:37 AM
|
Thanks muchly.
|
Post #443,575
10/21/23 6:18:51 PM
10/21/23 6:18:51 PM
|
onenote too expensive? last team I was on used it extensively
"Science is the belief in the ignorance of the experts" – Richard Feynman
|
Post #443,576
10/21/23 6:44:54 PM
10/21/23 6:44:54 PM
|
I think they want us to move to that. I know nothing about it - just thinking about options.
I really, really hate putting stuff "in the cloud" and not being able to get it out again in a format that I can easily use. MS still messing around with the features of our version of Teams and Sharepoint and all the rest (and the bazillion logins with different timeouts) is extremely annoying.
I guess I should be happy though that IBM didn't win the OS and browser wars, though, amirite??!
Thanks.
Cheers,
Scott.
|
Post #443,577
10/21/23 6:56:30 PM
10/21/23 6:56:30 PM
|
onenote is text format
used it for howto's engineering notes configurations etc. search friendly unlike sharepoint "Science is the belief in the ignorance of the experts" – Richard Feynman
|
Post #443,578
10/21/23 9:46:13 PM
10/21/23 9:46:13 PM
|
Re: onenote is text format
|
Post #443,580
10/21/23 9:52:32 PM
10/21/23 9:52:32 PM
|
Teams search is garbage
|
Post #443,581
10/23/23 3:02:06 AM
10/23/23 3:02:06 AM
|
Tsk, tsk. You still trust shit like that to stay as-is?
You thought Micorosoft had given up on Embrace-Extend-Extinguish?!? I really wouldn't have thought you, of all people, were that naïve.
Personally, I avoid both as best I can. Which is getting ever harder, as the large(-ish) corps I've worked for recently increasingly tend to use... Whichever one of them it is for their intranet, and the other for... Fuck knows what, centralised document storage or shared editable docs or something (as kind of a Confluence competitor?). I can't quite tell them apart -- and I'm not sure whether that's because I am conflating them, or because Micorosoft is. --
Christian R. Conrad
The Man Who Apparently Still Knows Fucking EverythingMail: Same username as at the top left of this post, at iki.fi
|
Post #443,579
10/21/23 9:52:24 PM
10/21/23 9:52:24 PM
|
z/OS is pretty stable ;-)
|
Post #443,582
10/23/23 3:13:51 AM
10/23/23 3:13:51 AM
|
Pretty much out of left-field, but... TiddlyWiki?
At least last I used it (for a one-man documentation attemmpt), it was built entirely into the HTML file you're reading / editing: All the Wiki functionality was JavaScript, stored within the actual content page itself. Works great for single-person use, dunno about many. Guess it depends on the size of your team. Also, not sure if it's changed: The current Web page talks about "TiddlyDesktop is an app for working with TiddlyWiki files..." and "Don't attempt to use the browser File/Save menu option to save changes (it doesn't work)" -- which AFAICR used to be exactly the way to do it. And I can't recall there being any app at all. So Idunno... But if you want to spend some time looking into it: https://en.wikipedia.org/wiki/TiddlyWikihttps://tiddlywiki.com/--
Christian R. Conrad
The Man Who Apparently Still Knows Fucking EverythingMail: Same username as at the top left of this post, at iki.fi
|
Post #443,798
12/25/23 8:18:15 PM
12/25/23 8:18:15 PM
|
Thanks for the pointer.
I looked at it a little, and thought about it a little.
I've come to realize that I'm too late in my career to be working on things like this. If the youngsters want this type of thing, they're going to have to take the lead on it. Nobody's been screaming about replacement functionality yet.
It took a few months, but the "export your wiki to OneNote" thing finally appeared for us. In the meantime I just copied and pasted the existing wiki stuff into a Word document.
My J is retiring at the end of the month. I'm going to stick it out for a while, we'll have to see how it goes...
Thanks again.
Cheers,
Scott.
|
