New folder structure about mycorrhiza HOT 8 CLOSED

Why would we go for one-wiki-one-folder structure?

• It boils things down to just a single one-liner for your new wiki (when #55 will be done): mycorrhiza cool-wiki
• Now there's no confusion between a default configuration and a non-existent configuration—it's either there (and that's good) or it's not (and we just populate it using a setup wizard).
• It's a foundation for supporting different storages. Now we can have wiki.git, wiki.db or something else right inside the wiki directory.

How could we go about it?

@bouncepaw suggested a nice file structure, and with my suggestion applied it becomes this:

cool-wiki/
|- wiki.git/ # Git repository
|- config.ini
|- registered-users.json
|- fixed-users.json
|- cache/
   |- tokens.json
   |- rendered-hyphae/
   |- resized-media/

Why is this good?

• Now we can run multiple wikis from the same user, and they'll not conflict with each other.
• This structure makes it much easier to manage the wiki for administrators. All files are placed inside this folder and not scattered across your home directory.

Why is this bad?
I dunno, can't think of anything.

from mycorrhiza.

I've written https://github.com/bouncepaw/mycorrhiza/blob/f61a4c1168375a364834c5c4644bfc9655a94277/files/Structure.md for developers' pleasure

from mycorrhiza.

@bouncepaw cool ideas, i just want to remind about plugins that can be changed without recompiling and that can depend on wiki. Such as js-only plugins

from mycorrhiza.

It's a foundation for supporting different storages.

That's where dynamic hyphae will be stored, cool. wiki.dynamic or something.

Why is this bad?

The only downside is that it's a breaking change. Good news: full compatibility between versions was never really promised!

So, what do others think?

from mycorrhiza.

So, what do others think?

I don't very like such folder-in-folder structure, even in my programming projects. But this is not an objective reason :) Pros looks tasty. Also, maybe mycorrhiza can use sqlite db for cache (tokens, pre-renders etc)

from mycorrhiza.

maybe mycorrhiza can use sqlite db for cache (tokens, pre-renders etc)

It can and it may happen like that one day. Not anytime soon though...

from mycorrhiza.

cool

from mycorrhiza.

Implemented in 1.2

from mycorrhiza.