| PDT, Subclipse, Multiple Servers [message #65471] |
Thu, 31 January 2008 16:07  |
Eclipse User |
|
|
|
Originally posted by: modeps.gmail.com
I've got three environments setup for development of my PHP app.
Here's how I do things currently:
1) Synchronize with my head revision from the SVN server to my local hard
drive copy (with Subclipse)
2) Make changes to my local copy (Eclipse PDT), upload those to the test
environment (Normal SFTP Prog).
3) Once changes are tested and working, I'll commit my changes to the SVN
repository (with Subclipse) and then upload those changes manually to the
production environment (Normal SFTP Prog).
I'd like to, if possible, remove the manual process of uploading files to
the test/prod environments with my normal SFTP app, and do it all through
Eclipse to avoid potentially missing files in the manual process (as
Eclipse is nice enough to flag items that change for me)
Basically I'd like something like this:
1) Synchronize with my head revision from the SVN server to test
environment (with Subclipse)
2) Make changes on the test environment (with Eclipse PDT)
3) Once tested and working, Commit my changes to the SVN repository and
also upload them to the production environment (Maybe a combo of Subclipse
/ Other Plugin)
I'd rather not install apache/mysql/php on my local machine for testing,
as there are multiple developers working on separate files and everyone
would need their own instance. Any ideas, recommendations, or solutions?
|
|
|
| Re: PDT, Subclipse, Multiple Servers [message #65636 is a reply to message #65471] |
Wed, 06 February 2008 04:27  |
| Eclipse User |
|
|
|
try Ant 's FTP, SCP Tasks and SVNAnt for SVN Support
James Hunter schrieb:
> I've got three environments setup for development of my PHP app.
>
> Here's how I do things currently:
> 1) Synchronize with my head revision from the SVN server to my local
> hard drive copy (with Subclipse)
> 2) Make changes to my local copy (Eclipse PDT), upload those to the test
> environment (Normal SFTP Prog).
> 3) Once changes are tested and working, I'll commit my changes to the
> SVN repository (with Subclipse) and then upload those changes manually
> to the production environment (Normal SFTP Prog).
>
> I'd like to, if possible, remove the manual process of uploading files
> to the test/prod environments with my normal SFTP app, and do it all
> through Eclipse to avoid potentially missing files in the manual process
> (as Eclipse is nice enough to flag items that change for me)
>
> Basically I'd like something like this:
>
> 1) Synchronize with my head revision from the SVN server to test
> environment (with Subclipse)
> 2) Make changes on the test environment (with Eclipse PDT)
> 3) Once tested and working, Commit my changes to the SVN repository and
> also upload them to the production environment (Maybe a combo of
> Subclipse / Other Plugin)
>
> I'd rather not install apache/mysql/php on my local machine for testing,
> as there are multiple developers working on separate files and everyone
> would need their own instance. Any ideas, recommendations, or solutions?
|
|
|
| Re: PDT, Subclipse, Multiple Servers [message #65701 is a reply to message #65636] |
Thu, 07 February 2008 04:45 |
| Eclipse User |
|
|
|
ivo bathke a écrit :
> try Ant 's FTP, SCP Tasks and SVNAnt for SVN Support
>
>
> James Hunter schrieb:
>> I've got three environments setup for development of my PHP app.
>>
>> Here's how I do things currently:
>> 1) Synchronize with my head revision from the SVN server to my local
>> hard drive copy (with Subclipse)
>> 2) Make changes to my local copy (Eclipse PDT), upload those to the
>> test environment (Normal SFTP Prog).
>> 3) Once changes are tested and working, I'll commit my changes to the
>> SVN repository (with Subclipse) and then upload those changes manually
>> to the production environment (Normal SFTP Prog).
>>
>> I'd like to, if possible, remove the manual process of uploading files
>> to the test/prod environments with my normal SFTP app, and do it all
>> through Eclipse to avoid potentially missing files in the manual
>> process (as Eclipse is nice enough to flag items that change for me)
>>
>> Basically I'd like something like this:
>>
>> 1) Synchronize with my head revision from the SVN server to test
>> environment (with Subclipse)
>> 2) Make changes on the test environment (with Eclipse PDT)
>> 3) Once tested and working, Commit my changes to the SVN repository
>> and also upload them to the production environment (Maybe a combo of
>> Subclipse / Other Plugin)
>>
>> I'd rather not install apache/mysql/php on my local machine for
>> testing, as there are multiple developers working on separate files
>> and everyone would need their own instance. Any ideas,
>> recommendations, or solutions?
Subclipse + Mylyn are also a really nice combo for SVN and project
management, as both will interact with svn and a Trac or Bugzilla. Each
ticket will be linked to a commit and vice-versa.
And subclipse is far the best from my point of view for eclipse : a nice
interface, similar to tortoise svn that everybody alerady knows...
If I was facing the same situation as you, I would mount a webdav or
network folder or any kind of solution like this that your environment
can give. Then I will work directly on the distant server. You can also
play with branches in svn to synchronize your local system with svn.
Finally you can also use something better than svn that can work
distributely.
There is no point about coding in local and sending in and back via FTP
from my point of view.
|
|
|
Powered by
FUDForum. Page generated in 0.06393 seconds
Home