Can Abyss have/use a document root on a network (NAS) drive?

JMMotyer

Hello, folks,
I have Abyss X2 running on a Windows 10 Hyper-V VM, with about 10 hosts. All has been running great that way for many years.
Due to limited drive space of the VM (because of many thousands of images on certain hosts), I was thinking about & trying to have some of those hosts located on a NAS. I've mapped a drive ( N: ) over to the folder (share) on the NAS where I would like to have those hosts, and I can reach that folder fine from Windows itself, but it seems that Abyss is only able to see actual (physical) local drives for document roots. If I manually enter in the document root, such as N:\foldername, Abyss tells me "Directory not found".
Is there perhaps another way that I am unaware of, whereby an Abyss host can have a document root on a network drive (i.e. NAS)?
Thanks in advance & have yourselves a great day.
Regards,
John

Horizon

Hello,
Network shares aren't real Drive objects in Windows.
Real drives have a PhysicalDrive object such as:
\\.\PhysicalDrive0, \\.\PhysicalDrive1, etc.
One way to proxify Abyss Web Server access to a remote share (here NAS) is to use either:
- NetDrive
- WebDrive
- ExpanDrive
- AirLiveDrive
- CyberDuck
- Mountain Duck
- Eltima CloudMounter
Some are free, some commercial, and not all are priced the same way.
These software can create a 'local drive' that appears local but their drivers actually do FTP, SFTP, SMB, DropBox, Google Drive, etc...
Although there softwares are still not creating real drives (e.g. \\.\PhysicalDrive) these will however actually work.
If any problem, you could also create a junction between a local folder and your 'local drive':
https://learn.microsoft.com/en-us/sysinternals/downloads/junction

JMMotyer

Horizon wrote
If any problem, you could also create a junction between a local folder and your 'local drive':
https://learn.microsoft.com/en-us/sysinternals/downloads/junction

I was just reading about Junction, and there's a note on that page that says

Windows does not support junctions to directories on remote shares.

But those Junctions in Windows... they're the same a symbolic links in Linux that I've used in the past a few years ago, when I had my websites hosted externally by company.
When I have some time, I will check out the other options that you mention.
Thanks for taking the time to reply to me with your suggestions.

pkSML

There's more than one way to skin a cat, so to speak... Perhaps you could run a web server on the NAS itself. Many NASs these days seem to cover their bases for accessibility (web, FTP, etc.). Then you could reverse proxy the "/" folder to the NAS web server. And give Abyss a "dummy" root folder.