New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Dokuwiki is quite solid, no db required either.
I don't think a documentation system that doesn't use an existing database is going to be lightweight -- it's going to need to implement something to deal with text files and potential consistency issues.
Probably you want something that uses a lightweight database like sqlite. Or just use git or google drive.
vi
google keep note? evernote?
I have been searching for something like this for ages : https://docs.mongodb.com/
https://vuepress.vuejs.org/
https://github.com/mongodb/snooty
https://github.com/mongodb/docs-tools
acme!
(gawd, are you one handsome guy)
I recently setup Bookstack to convert many of my old text docs to something that can be held remotely and better formatted. I like it.
http://raneto.com/
+1 on dokuwiki
+1 for Bookstack
If cloud based is fine, https://archbee.io/team-wiki is running a lifetime deal. I don't know how much they compare to this tho.
what's wrong with good old README.md
Need something local and internal to be honest. Can't afford the things to go kapoot you know.
Absolutely nothing as well as simple.txt but Ineed something more structured.i will try dokuwiki, it looks good and standard. Thank you.
vim
Markdown and without database ofc
https://docusaurus.io/
Atlassian
bookstackapp.com
Self-Hosted, LAMP Stack.
+1 for vuepress as well. Supports markdown and easy to use. Because it just gives static pages, it's pretty "lightweight" I believe.
Dokuwiki is perfect. Style and speed are good. Running from my rPi 2 without a problem.
+1. Not (really) lightweight but it does the job better than anything else I've tried.
I disagree. First issue: why SQL at all? Plus most wikis are simply structured (from a developers POV) and don't have hundreds of thousands of entries.
@LTniger
A bit more information would be useful in order to get sensible advice/suggestions
Chose to use Hesk with private kb. Granted, uses SQL but pretty simple and gets the job done. Plus creates an internal helpdesk for "team"
I was thinking OP wanted a web app where they could edit the documentation from the web app, in which case I'd argue a system that uses a database like sqlite is going to be lighter weight than one that deals with the potential concurrency / consistency issues itself.
But otherwise I think some text files in git or a google drive shared folder would be fine solutions. Or if they do want to view the documentation in a web app, but not necessarily edit it from there, then one of the static site generator.
Agreed they need to give more info.
Edit: see e.g. https://www.dokuwiki.org/devel:locking
Thanks @MikeA BookStack looks gut sir.
Is there a browser plugin version? And I do not mean some w3m extension because something not gobbling up min. 1 GB RAM is neither a modern browser nor a modern editor.
Anyway I'm more interested in how you maintain and nurture your super-beautiful hair.
OK but for simple jobs like a lite wiki using a DB without SQL is fine and even lighter. Depending on the job even directory structure plus a simple small index updater might be good enough.