Massimo Melina
Massimo Melina
please let me know if this fix works for you
you can launch hfs with parameter `--debug` to get more in console. it's not clear "clicking in the admin portal". You don't know what you were clicking? also please clarify...
nope, it should start in about 5 seconds. can you share your configuration? admin-panel > options > config file > export
let me say that you don't need to set same permissions on all sub-folders. you can set those permission on "Machine"
i just noticed that you have "Machine" twice. This is NOT ok. HFS doesn't support this. The admin-panel doesn't allow this, so i assume you got this by editing config.yaml...
this is a cleaner version ```yaml vfs: children: - name: Machine can_see: "*" can_read: "*" can_list: "*" can_upload: "*" can_delete: "*" can_archive: "*" children: - name: Machine1000 children: - source:...
correct, nothing i've said yet solves the problem. i'm still investigating
ok, i've found something useful. You can work around the problem by calling this before launching hfs. > set UV_THREADPOOL_SIZE=32 this is the number of files that nodejs (HFS's base)...
> are displayed as "files" you say "goes online", so are they displayed correctly as folders when they are online from the beginning?
i've been working very hard to mitigate the first problem, the one you solved with UV_THREADPOOL_SIZE. (i've also been off for 2 weeks in the meantime) Future versions should work...