Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » PHP Development Tools (PDT) » 'Ideal' Workflow for PDT with Remote Xdebug-ging, TM/RSE & Version Control ?
'Ideal' Workflow for PDT with Remote Xdebug-ging, TM/RSE & Version Control ? [message #526426] Sat, 10 April 2010 21:58
BenDJFriend
Messages: 4
Registered: April 2010
Junior Member
Hi,

I'm starting to build/deploy and Eclipse-based work environment across local development and remote deployment.

Our setup is fairly straightforward:

Remote web server
----------------------------------
Apache2
PHP 53 via mod_fcgid, with XDebug
accessible via 'anything' SSH pubkey auth'd (ssh, sftp, fuse-ssh, etc).
Source in Bzr repositories

Local workstations
----------------------------------
Eclipse 35 'Galileo' PDT w/ TM (Target Management) & RSE (Remote System Explorer)
local Apache2, PHP53, Xdebug, Bzr, etc -- if/as required

To date, our workflow has been to simply checkout remote source to the local workstations, hack/edit in text editors, then push back to the server -- using Bzr, fwiw. Debugging was done 'manually' via cmd line XDebug in shell sessions (over SSH) at the server itself.

With the introduction of Eclipse/PDT we've "inherited" more flxibility -- and complexity:
(1) we can access the remote server via ssh thru Eclipse, locally via Eclipse to a local fuse+ssh mount, &/or acccess via RCS (bzr) @ filesystem cmd line, &/or via the Eclipse plugin.
(2) we can have project files remain on the remote server, &/or RCS-pull (or simply sync) to local project stores
(3) we can debug fully-remotely, &/or cross-debug via a local apache/php/xdebug install

I.e., endless possibilities ...

I *think* our ideal workflow is:
(1) remote server as RCS repository server
(2) remote server as the only/authoritative Apache/Debug server -- i.e., all live-site debugging occurs only at the server
(3) local access to remote files via SSH-pubkey-auth only, working on local, RCS checked-out stores -- via Eclipse plugin (bzr, e.g.; makes little difference ...) -- serving as local Eclipse project files.

My questions are:

(A) Does this approach make sense, or is it fundamentally challenged/flawed?
(B) Is there a step-by-step tutorial for a process similar to this available? In particular: Galileo/PDT + TM/RSE + Remote XDebug-ging & Local Eclipse PRoject/Workspace-integrated version control ...

Thanks for any comments!

BenDJ
Previous Topic:Autocomplete HTML/CSS
Next Topic:Zend Debugger All in one download PDT NOT WORKING
Goto Forum:
  


Current Time: Fri Apr 26 22:23:09 GMT 2024

Powered by FUDForum. Page generated in 0.03136 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top