How to open project from the network share

My project is located on \\SERVER2\WWW\prj path.
How can it be opened straight from the network share?
Is impossible to browse network shares in 'Open Project' dialog.

14 comments

Workaround:

Map network share as a disk drive. :)

2

Working directly over mounted networked location is officially unsupported. We will not accept any bug reports.

Use "New project from existing files" wizard to create a local copy and create auto sync.

0

Indeed, at the moment'Create project from existing files' wizard does not accept UNC paths (such as \\server\share): http://youtrack.jetbrains.net/issue/WI-2491. Workaround is similar: map your network folder as local drive.

0

Hey,
What does it mean 'officialy unsupported'? There is demo http://www.jetbrains.com/phpstorm/documentation/index.html

Open code from anywhere, an FTP server, mounted network drive, etc., and start working in no time. Set-up automatic synchronization on files saving.

0

The keyword is "DIRECTLY". Our wizard creates a local copy. Low-latency storage for all project files is a requirement.

All other scenarios might work - and they usualy do most of the time, especially for local networks, but once network experiences any hiccups - you'll get ALL sorts of the problems. And we won't be able to help you at all.

0

I can't find this keyword on the page. You should give more detailed descriptions and hire native speaker to dub demos. Otherwise you look like pushers who don't care about customers.

Easy project configuration — open code from anywhere and start working


There are over 15k files (>1.5k directories) in the project and I can't open even single file because it's stuck on the folder scanning.
1

There's a description that tells you about copying right in on the first wizard page, also clearly visible in video.

We are constantly working on the both quality and features of our product and help materials/demos.

0

Hi Roman,

PhpStorm relies on instant access to all the project/library files to provide high-quality code analysis, completion, navigation etc. This means that these files should be physically located on local machine. When one needs to work with remote files, following scenario is supported: IDE copies all the files from the server (via FTP, SFTP or network share aka mount) to local machine and allows to easily upload changes back to the server (this is what our demo shows - please see the first page of the project creation wizard). At the moment there's a problem that if you have your server accessible by network share, IDE won't accept UNC path (\\myserver\myproject), so first you have to map this path to some local folder (e.g. using 'subst Z: \\myserver\myproject' command on Windows).

By saying that we don't support direct editing of remote files we mean that if you open your Z:\ folder as local project folder IDE may become slow and unresponsive.

Regards,
Kirill

PS Right now it's not possible to work with single file on server without  copying all the project to local machine, please vote for  http://youtrack.jetbrains.net/issue/WI-1398.

0

Have changes been made to the file reading process?  Earlier versions of PHPStorm dealt fine with projects on my mapped drive.  Starting with 2016.1 or so, performance became notably worse.

0

> Have changes been made to the file reading process?

They have. Our indices become more and more complicated, so as local availability of source files becomes more and more important for PhpStorm.
Please consider using Deployment Configurations.

0

I would have thought that the indices could be locally stored to avoid this being a problem. Also technically network storage can have higher performance than local storage especially with the ageing encrypted drive I have now...

I actually find that the indexing on my local storage can intermittently interfere with switching branches. I have an SVN project and when switching branches on a local hard drive occasionally the branch fails to switch citing locking issues. The switch causes PHP Storm to trigger an indexing event, if the indexing event manages to start before the switch completes there appears to be a 50% chance of the switch failing and requiring cleanup. Closing PHP Storm before a switch is the only way to guarantee a successful switch.

If we compare the throughput of my development machine local vs network

sequential read

108 mb/s VS 100mb/s

sequential write

50 mb/s VS 100 mb/s

random read 4k

2 mb/s VS 100 mb/s

random read 4k

1.4 mb/s VS 100 mb/s

Given that the network performance is substantially higher it is strange that I cannot open files via a network store without them closing straight away.

0

> I would have thought that the indices could be locally stored to avoid this being a problem.

They are stored locally.

> I have an SVN project and when switching branches on a local hard drive occasionally the branch fails to switch citing locking issues.

I might be getting you wrong but it's not advised to switch branches while there's indexing going on.

> Given that the network performance is substantially higher it is strange that I cannot open files via a network store without them closing straight away.

That's not only the performance question. It's also about the reliability of the connection & the way IDE interacts with file system.

0

> I might be getting you wrong but it's not advised to switch branches while there's indexing going on.

The switching causes the re-indexing, which in turn causes the switching to fail. i.e. 

1. Switch

2. A few seconds later the re-indexing automatically starts

3. Switch fails

4. Indexing completes.

5. SVN cleanup required

> That's not only the performance question. It's also about the reliability of the connection & the way IDE interacts with file system.

Understand that file watching may be more of an issue, I am unsure why you cannot prevent certain features from operating in this environment rather than prevent even basic editing.

0

I switched to VS Code. It is perfectly fine with editing sources within Samba paths like \\hassio\config

0

Please sign in to leave a comment.