Project root aenea.json not optional about aenea HOT 3 OPEN

I don't have a strong opinion which is correct. I lean toward print a warning and continue. It should be "optional", but given nearly everyone will need to change at least one thing I don't want it to fail silently to reduce pain for new users.

from aenea.

Well, I guess the confusing part is they're the same exact file if you've just copied the example. I actually made the early mistake of setting project_root in the Natlink copy, but not changing it in the one in my aenea installation, and then nothing worked because my project_root value changed to an invalid path. Seeing they're virtually the same file, I decided to just delete the one in my aenea project and manage it entirely from the Natlink directory. Is this "wrong"?

I like the flexibility in having both. But in practice I'll probably only use one, in which case, making the other file truly optional would be a valid thing to do. Or I'll have a file in the Natlink directory that only sets the project_root and one in the aenea directory that sets everything except the project_root.

I realize you haven't written the docs on this yet. When you do, some guidance would be helpful. Because right now it does seem like just duplicating the files in both places.

from aenea.

I think it should work for both cases. People working locally will likely want to manage their project from Windows and possibly base Aenea in MacroSystem. People (me) who are mostly remote want to manage Aenea from a dir on linux mounted in the VM as a different folder. I have 2 aenea.json; the one in MacroSystem just points to my E drive and sets nothing else.

from aenea.