Phpstorm Remote Host panel - inaccessable files (strikethough-ed)

I want to view my error log on my remote server, but for some reason this and my access log have a line through them and are greyed out.
I can't open them, I can't copy them. They have full permissions.
No other files on my server has a problem, I can't find any documentation on what this means or why.
How can I view these files with phpstorm? Preferrably I'd like to view them and constantly update them so I can keep track of any erros while I test my website remotely.
Shall I just write a php script that grabs the last 1000 or so lines and with ajax reload it every few seconds?

2 comments
Comment actions Permalink

Hi there,

I want to view my error log on my remote server, but for some reason this and my access log have a line through them and are greyed out.
I can't open them, I can't copy them.

TBH I do not know what such styling means. Can you show a screenshot of it and what content menu do you see if right click on such file? How big the file is?

Maybe that file cannot be mapped (remote location cannot be mapped to local hence IDE does not know where to download it)?

Another possible issue -- maybe that file is excluded from transfer operations (check your settings: could be excluded by path or by file name).

Preferrably I'd like to view them and constantly update them so I can keep track of any erros while I test my website remotely.

That's not really possible with PhpStorm -- remote file system does not send "file was modified" notifications like local file system can .. plus it's not trivial task to just download "new" bytes (instead of re-downloading whole file) -- heavily depends on protocol used (e.g. FTP would be the worth to work with with such requirements).

If that file would be local then you could easily use Grep Console plugin to tail such file (display new lines automatically).

Shall I just write a php script that grabs the last 1000 or so lines and with ajax reload it every few seconds?

I'd say it's a very good option.

0
Comment actions Permalink

I found out the problem, the 2 files in question were actually symlinks directing to a part of the filesystem I had no access to.
I can't post a screenshot because the names of the files include the url of my server which is not yet meant for public access.

0

Please sign in to leave a comment.