Thank you both for your responses!
No, this is not the optimal arrangement. I am working on the road from my
laptop. I VPN into my home network. Rather than mirror the code locally on
my laptop, install apache on the poor little thing, and then deal with
merging the codebases, I am using my main devel machine as a remote host and
working from it using RSE. This is slower than local development by a long
shot, but faster than manually ftping everything to the remote server. Thus,
there is no local mirror for me to commit to the repo, which is on another
machine hosting SourceForge for project managment. Eclipse created project
files locally when I created a new project to do said development. These are
the local files I referred to in my previous post. Using a local mirror of
the codebase was one of the options I had looked at, but is essentially a
waste of time, and defeats the purpose of using RSE. I was looking for a way
not to do that. Looks like I came up short.
I am unclear about how subclipse handles remote repos. I understand that svn
is just a version management system. However, Subclipse supports remote SVN
repos. Presumably, when a commit is performed, the newest version of the
updated files are uploaded to the server where the repo is hosted. If this
is the case, then some sort of ftp must be used. Does Subclipse do this
itself, or must I then manually upload the files to the appropriate
directories?
Thanks again for your help!
Paul Pcoder wrote:
>
> On Fri, Mar 21, 2008 at 3:03 PM, ckoning <info_at_brahmacomp.com> wrote:
>
>
>> files are to be committed. I can commit all the local files, but the
>> remote
>> files are not given as an option for commitment. Is there a way to tell
>> Subclipse to commit the remote files as well? I would really like not to
>> have to SSH into the server and svn from the terminal.
>
> I think you don't understand. To begin with, svn isn't a file transfer
> manager. Secondly, I don't think you'd really want to have a working
> copy on the server.
>
> I do php work as well. I use svn to work locally, doing php coding, using
> a local copy of apache on my box. I commit my files to the repository.
> Then I collect my files using an archiver (being sure to NOT include the
> .svn folders) and I transfer that to my live site using SFTP or something
> similar. Alternatively, I could do a svn export of my working copy, and
> transfer that to my live site.
>
> The point is that I can't imagine why you'd want a mirror of your working
> copy on your server. That would be like buying a piece of software,
> installing it on a machine, and then finding all sorts of .svn folders
> everywhere in the installation directory.
>
>
> regards
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>
>
>
--
View this message in context: http://www.nabble.com/Subclipse%2C-SVN-and-Remote-Host-tp16209470p16211331.html
Sent from the subclipse - users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-03-22 00:49:57 CET