|
Re: I'm a confused - debugging [message #41932 is a reply to message #41897] |
Thu, 09 August 2007 18:57 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: james.gnr-inc.com
exquisitus wrote:
> Hi
>
> Lets take few things out of the way first :)
>
> I'm using Ubuntu 7.04, Eclipse Europa. I have successfully installed
> Xdebug on my "development" server and Xdebug client in Eclipse.
> Everything seems to be working but...
>
> On my development server I have Apache 2, php 5.2.x and svn repository.
> Now when i check out a project from repository using subclipse and make
> some changes to the php source code how can I debug it?
>
> Logical answer would be to 1. commit changes to svn, 2. export the
> project to the folder when i can access it by apache and test, 3. figure
> out the way to debug the script in the way that client and server
> (apache) know what file I'm debugging....
>
> And that's my question: How should I set up the SVN, Apache, Eclipse to
> work together? Right now i don't see the way. It would be easy it it
> ware only the PHP scripts. Then one would be able to set up the apache
> on the computer he/she is developing on and debug it locally before
> committing. But what about the databases that are needed to ran the
> project (mySQL is also on the development server)?
>
> PS: I don't know why but XDebug and ZendDebbuger work only if I select
> "Break on the first line" and if I don't debugger does not stop on the
> breakpoints :(
Not that I have a normal development setup, but here is how I do it:
I have a production server and a development server out on the internet.
On the development server I have Apache and MySql. I have a 'dev' copy
of the database and Apache setup for of each site that I am on. The url
for the dev sites would be something like james.website.com
In Eclipse I use subclipse to checkout a working copy to my local
workstation. I do my work and use JCraft's sftp plugin to transfer
(export) files to the dev site. I did spend the time to get Xdebug
working on the remote server, but sadly I don't use it :(. Once I am
happy I commit to the repository using subclipse.
Then on the live site I ssh over and update that live 'working copy'.
Again, probably not the normal development environment, but I work from
several computers and it's worked out for me so far.
James
|
|
|
Re: I'm a confused - debugging [message #41963 is a reply to message #41897] |
Thu, 09 August 2007 21:17 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: mshekov.gmx.de
I'd also recommend you to checkout the repository to your local machine,
create new code there and also debug it locally. As that means you'll
also need the developer-environment DB you can either choose to have a
local copy of it (in your local DB) or to setup the dev server DB in a
way that it accepts external connections, this way you keep using just
one database.
|
|
|
Re: I'm a confused - debugging [message #42024 is a reply to message #41932] |
Thu, 09 August 2007 21:56 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Ralph ![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=rzajac%40gmail.com) Messages: 6 Registered: July 2009 |
Junior Member |
|
|
James wrote:
> exquisitus wrote:
>> Hi
>>
>> Lets take few things out of the way first :)
>>
>> I'm using Ubuntu 7.04, Eclipse Europa. I have successfully installed
>> Xdebug on my "development" server and Xdebug client in Eclipse.
>> Everything seems to be working but...
>>
>> On my development server I have Apache 2, php 5.2.x and svn repository.
>> Now when i check out a project from repository using subclipse and make
>> some changes to the php source code how can I debug it?
>>
>> Logical answer would be to 1. commit changes to svn, 2. export the
>> project to the folder when i can access it by apache and test, 3. figure
>> out the way to debug the script in the way that client and server
>> (apache) know what file I'm debugging....
>>
>> And that's my question: How should I set up the SVN, Apache, Eclipse to
>> work together? Right now i don't see the way. It would be easy it it
>> ware only the PHP scripts. Then one would be able to set up the apache
>> on the computer he/she is developing on and debug it locally before
>> committing. But what about the databases that are needed to ran the
>> project (mySQL is also on the development server)?
>>
>> PS: I don't know why but XDebug and ZendDebbuger work only if I select
>> "Break on the first line" and if I don't debugger does not stop on the
>> breakpoints :(
>
>
> Not that I have a normal development setup, but here is how I do it:
>
> I have a production server and a development server out on the internet.
>
> On the development server I have Apache and MySql. I have a 'dev' copy
> of the database and Apache setup for of each site that I am on. The url
> for the dev sites would be something like james.website.com
>
> In Eclipse I use subclipse to checkout a working copy to my local
> workstation. I do my work and use JCraft's sftp plugin to transfer
> (export) files to the dev site. I did spend the time to get Xdebug
> working on the remote server, but sadly I don't use it :(. Once I am
> happy I commit to the repository using subclipse.
>
> Then on the live site I ssh over and update that live 'working copy'.
>
> Again, probably not the normal development environment, but I work from
> several computers and it's worked out for me so far.
>
> James
Hi
Thank you for your response. Your setup is very good if there is one
developer. What if there is lets say 3 or 4 developers that decide to
upload their work to the development server? I think the only way 3 or
more developers can work on the same project is to have them install
apache and php on their machines and share only the development
database. That would mean that they would have to keep their database
connection config files out of the svn. Does anyone have a different idea?
Ralph
|
|
|
Re: I'm a confused - debugging [message #42055 is a reply to message #42024] |
Fri, 10 August 2007 00:12 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: mail.buster.cc
exquisitus wrote:
> James wrote:
> Hi
>
> Thank you for your response. Your setup is very good if there is one
> developer. What if there is lets say 3 or 4 developers that decide to
> upload their work to the development server? I think the only way 3 or
> more developers can work on the same project is to have them install
> apache and php on their machines and share only the development
> database. That would mean that they would have to keep their database
> connection config files out of the svn. Does anyone have a different idea?
>
> Ralph
>
>
Actually we have several developers working on the dev server on the
same site (alan.website.com, bob.website.com). But we each have our own
working copy that we work off of. As well as our own db and apache
vhost. If we make any changes to the db or vhost we commit those to the
repository as a txt or sql file.
For our db setup, we have a user in MySql that has access to all the dev
db's (james_websitecom, alan_websitecom, bob_websitecom). We also use
the same username and pass on the live site so we only have to change
the database name in the dev env. For that we make use of SetEnv in our
apache .conf file for each site and pull that in with php's getenv.
I really don't know how well that would scale beyond the 4 users that we
have, but it does work well for us.
James
|
|
|
Powered by
FUDForum. Page generated in 0.04217 seconds