Way to define a custom root dir

[edenworky]

For my use case, my project dir contains all sorts of things, and I keep all my notes in a notes dir inside of that. Does Emanote have a way of supporting this? Right now my index.md is in ./notes/index.md and everything works well except that all my notes have an extra hierarchy which is less than desirable. Could we have in index.yaml some setting emanote.notesDir which defaults to .?

With your blessing and a bit of orientation I'd love to submit a PR.

[srid]

This could be solved indirectly using #228 perhaps?

[edenworky]

Hmm not really. With all my notes under ./notes, that means all my links, link uptrees etc all have a dangling notes/ prefix. What I want is a way for my ./notes to be "treated as" root insofar as e.g. ./notes/index.md to be treated as ./index.md and be accessible at <ROOT_HOST>/ rather than have to go through <ROOT_HOST>/notes/, and for the link uptree to not have a notes node prepended everywhere, unless I misunderstand an .ignore file wouldn't help

[srid]

Ah, I see. But what if put your index.yaml inside of notes/ directory and ran Emanote like this:

cd ./notes && emanote run

?

I'm just trying to see if we really need this feature in Emanote.

[edenworky]

Hi, yes, that does technically work. However, it can't seem to find even the favicon if it's in ./static instead of ./notes/static (which is less than desirable), which makes me think it also won't be able to embed files from outside its own dir. We could solve this by supporting paths starting with ../ but that seems messier, and I'm worried the current approach wouldn't play nice with e.g. zk (which I'm still setting up for myself).

My current setup as per your recommendation is workable enough so I defer to your judgement insofar as what if at all the issue should be.