Ah, so you are seeing the same “No database found in…” error that I got. Glad to know it wasn’t just me!
It looks like a random build error. I tried rebuilding the 2.1.0.5 without any changes, and here the file was included.
The fix for now is that the release build process checks for a few known files and aborts if any of them are missing.
The folder HOME is usually something like /home/username, so if you set HOME Duplicati will make the .config/Duplicati under that.
It should certainly not create a folder under the current working dir?
That would be a new behavior. I have seen in the past that it sometimes returns /, causing it to use /Duplicati.
This has been fixed in the later builds:
It does check specifically for using just “Duplicati” as a relative path, so it sounds plausible that it happens.
It is the intention that “most specific wins”, so if both are set, HOME is general for lots of applications, where DUPLICATI__SERVER_DATAFOLDER is very Duplicati specific.
If you find that this is not the case, let me know, and I will fix it.