Closed MuhannadYT closed 8 months ago
hey @MuhannadYT can you share your version?
droppy -v
0.2.8
Same thing happens for me on Linux (Ubuntu 22.04) using Node 18 - regardless of the -c
and -f
options I use, it will use ~/.droppy/
.
Is this the issue? When parsing the arguments, it doesn't seem to specify that configdir
or filesdir
are even valid options?
Perhaps not - it looks like it should just pass through options as they are given if not declared.
Confirmed that the arguments are passed through verbatim by adding some console.log
statements:
root@droppy:~# /usr/bin/droppy -c /mnt/nfs/server/droppy/config -f /mnt/nfs/server/droppy/files
{
_: [],
color: false,
d: false,
daemon: false,
dev: false,
c: '/mnt/nfs/server/droppy/config',
f: '/mnt/nfs/server/droppy/files'
}
/mnt/nfs/server/droppy/config
/mnt/nfs/server/droppy/files
Further, it looks like paths.get
is called before paths.seed
:
root@droppy:~# /usr/bin/droppy -c /mnt/nfs/server/droppy/config -f /mnt/nfs/server/droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.get
/root/.droppy/config
/root/.droppy/files
paths.seed
/mnt/nfs/server/droppy/config
/mnt/nfs/server/droppy/files
Is it really just that paths.get()
is called on the server start and not refreshed after .seed()
is called?
When I enter
droppy start -c D:\droppy\config -f D:\droppy\files
for example, droppy launches inC:\Users\[username]\.droppy