7 ms·
It seems somewhat ironic that a "simpler" tool that lets something else "do the heavy lifting", needs a Postgres database, whereas gollum just uses the file sys
by stephenr 10y ago
It seems somewhat ironic that a "simpler" tool that lets something else "do the heavy lifting", needs a Postgres database, whereas gollum just uses the file system (holding a git repo)
- y4m4b4 10y agoGollum is a great project and it is really nice to see great supportive community around it. Doctor only solves a niche problem of serving existing content, aggregating it and managing it using github.com directly. Postgres is generally for the CRUD in grouping, aggregating/associating and customization. Do you have any better suggestion? Feel free to play with it and give us your feedback.
- stephenr 10y agoServing markdown content isn't a niche, within the set of what gollum does. I honestly don't understand what "aggregating/associating" you're talking about, that isn't possible in a regular markdown wiki (eg using gollum, but also several other md based wiki tools). As for suggestions - if your tool is specifically aiming to be lightweight, use a lightweight db, like SQLite.
- y4m4b4 10y agoGreat to know, we explored sqlite didn't serve our purpose earlier. Feel free to open a bug and we will evaluate it.