Add .emanoteignore

[srid]

Like .gitignore but for ignoring files.

Effectively allows overriding the hardcoded paths here: https://github.com/srid/emanote/blob/b3ced121059bb7a688c890f3ee489a9713191132/src/Emanote/Source/Pattern.hs#L34-L40

[atomicbird]

My main use for this would be to have Emanote ignore Obsidian template files. There are probably other uses, of course.

[JMLegere]

This would help a lot in only publishing certain folders (i.e. I do not want my Daily Journals published)

[srid]

Note that when a file is ignored in .emanoteignore, it would be excluded in both static site generation and the live-server view. So, @JMLegere, if you ignore your daily journals in .emanoteignore, they shouldn't appear in the live-server either. This may not be what you intended.

[JMLegere]

That is my intention. I work daily in my notes and link from my journals to my permanent notes, but want to only have my permanent notes visible in emanote.

Am I understanding this use case correctly?

[srid]

I work daily in my notes and link from my journals to my permanent notes, but want to only have my permanent notes visible in emanote.

You can achieve this differently.

$ ls 
./daily/2022-04-24.md
./permanent/foo.md
...

Basically, run emanote -L $(pwd)/permanent gen /tmp/output to generate static site for the permanent notes, but emanote -L ./. to start a live server that also includes your daily notes. I use this pattern on my private notebook, where srid.ca lives in a subdirectory (and published on its own, without including my private notes).

[JMLegere]

I work daily in my notes and link from my journals to my permanent notes, but want to only have my permanent notes visible in emanote.

You can achieve this differently.

$ ls 
./daily/2022-04-24.md
./permanent/foo.md
...

Basically, run emanote -L $(pwd)/permanent gen /tmp/output to generate static site for the permanent notes, but emanote -L ./. to start a live server that also includes your daily notes. I use this pattern on my private notebook, where srid.ca lives in a subdirectory (and published on its own, without including my private notes).

This workaround is a possible solution for my use case, thank you!

[peri4n]

This would greatly improve my setup. I use the entire remark ecosystem thus I have a node_modules folder sitting in my root folder.

[srid]

This should probably be done in https://github.com/srid/unionmount - then Emanote can inherit it automatically.