NuSphere Forums Forum Index
NuSphere Forums
Reply to topic
Project properties, FTP account settings and remote sync


Joined: 30 Jun 2006
Posts: 2
Reply with quote
Hello phpEd experts!

I am evaluating PhpED 4.6 and have looked through the forums and read the help, but I have not been successful with properly configuring the FTP/remote sync feature. The debugger (the main feature I am evaluating) is great! Anyway, I have the following setup:

    * local Apache/PHP (XAMPP) on Windows XP
    * multiple local projects each with different remote websites
    * using Run Mode w/ 3rd party web server (http://localhost/A/www)

I do not really want to install/configure multiple Apache instances for each project, so I use a pseudo-web-context approach. In other words, project A has a local root URL of http://localhost/A, which is mapped to the Apache <DocumentRoot>/A. <DocumentRoot> would be something like c:\xampp\htdocs. Project B would have a local root URL of http://localhost/B, etc. To make things a bit more interesting, one project's FTP account puts me into a parent folder that has only a 'www' subfolder, which is the remote URL root. The 'www' is only visible from the root FTP folder and is aliased to the remote URL of '/', so the following is true:

Remote URL of http://mywebserver/ is mapped to the FTP folder of 'www' which is mapped to a remote physical folder of something like X:\Some\Path\To\RemoteSiteAlias.

I have tried several combinations for configuring the Remote URL to include www (or not), and same with the FTP root directory. I am not clear if the Publishing folder value is my problem because I don't have access to the physical folder structure - it is aliased on a Windows box, which I have no control over. Please, no snide comments about using a Windows box as the web server - it's out of my control Crying or Very sad I get sync failure messages indicating bad paths, too many www's or not enough and can't seem to get all these mappings to line up. I even added my own 'www' subfolder (http://localhost/A/www maps to c:\xampp\htdocs\A\www) to see if I could line things up better. I am unclear why/how to create additional mappings to get this to work. Any hints for this kind of setup would be appreciated.

Best regards
View user's profileFind all posts by RemoSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 8340
Reply with quote
Quote:
I do not really want to install/configure multiple Apache instances for each project

You may setup multiple apache virtaul hosts. Each on a separated hostname, defined in hosts file as an alias for 127.0.0.1.
It will be just one instance (two apache processes as usual).

Anyway, local debugging does not require any FTP or remote directories.

If you want to publish your files to remote host, just specify FTP account and top publishing directory. URL is not required for this.
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 30 Jun 2006
Posts: 2
Reply with quote
Thanks for the quick answer. I understand I don't need FTP for local debugging, but I do want to take advantage of syncing the actual (remote) site with my local site.

When you say "just specify FTP account and top publishing directory..." If my project has only the 'www' subfolder with everything underneath it and the FTP account has only a 'www' folder (an alias for the physical web root directory), what should the value be for the "top publishing directory?" In the help, it says it should be the physical directory, which implies something like X:\Some\Path\To\RemoteSite for a windows server, but the FTP server seems to want only FTP path values - e.g. '/' or '/www'...

BTW, I can FTP using other FTP clients without issue. I'd just like to be able to stay within the IDE as much as possible.

And, thanks for the reminder about Apache and VirtualHost entries - I've just been lazy, I guess.
View user's profileFind all posts by RemoSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 8340
Reply with quote
Quote:
it says it should be the physical directory

Top publishing directory is always relative to the FTP root which does not always corresponds to the physical file system root.
In other words, take a file in the project root, say index.php. If should be transferred into /www/index.php, then /www is what you need to set in the Top publishing directory.

Quote:
And, thanks for the reminder about Apache and VirtualHost entries - I've just been lazy, I guess

I already posted similar suggestion with more details in this forum.
View user's profileFind all posts by dmitriSend private messageVisit poster's website
Project properties, FTP account settings and remote sync
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 5 Hours  
Page 1 of 1  

  
  
 Reply to topic