This old bug bear again. Is there anyway to 'upload' my project to another location on my system without having to run an FTP server? I develop in a subversion repository and I don't want testing to interfere so I can't use the repository - for example config.php would get modified on my test system and I don't want the test settings going into the repository over the clean, default configuration. It seems like a very simple, obvious feature but I can't see any way to do it from within PhpED.

This not a bug because it was never advertized that any uploading other than FTP/SFTP/WEBDAV is supported. Feel free to post your feature request in appropriate section.

OK, that's a no. I didn't know if it was in so I didn't know if it was a feature request.

I'm not sure how your projects/web servers and repository are organized, but I don't see any reason to use upload/publishing in your case. Suppose, you have local web server for your development. In this case you can store your project files directly in its root directory (or one of subdirs) and develop/test all the scripts in place. It's also where you can update repository from.

Well during testing, things get changed - configuration files, uploaded files. Inevitably these get committed to the repository, not a big deal but it's messy. Also incomplete code can be executed as half a function could be written and saved while you go and chase a bug reported in other code, causing all kinds of parse errors and crashes - you'd probably have to save the new work, commit, 'update' to an earlier build and start chasing the bug.

With them separate, I can be sure that the test server usually has executable, usable code on it. Together, parse errors will plague testing. This is especially important if two people are working on it over Windows Networking. We'd have to both edit the same working copy, negating the multi-developer advantages of source control.

I'm not sure I got it right. Do you mean that the repository is commited from something else but your development machine?


Do you mean that you two are working together with files located in the same directory subtree on the server?

The project I have in mind is 1 developer, so in this case no, the development machine is the only one committing unless I do some work on my laptop. My problem is that if I do initial testing on the development machine's working copy, something like a file will be uploaded while testing a file upload system and that will get committed, or the test install would need one config file while the development copy would have the clean, uncustomised version.



Yes, that's exactly what I mean, and what I would be forced to do if I were to do basic testing on the same code as several people are developing - if they can't upload across a network like I want. On larger projects informal testing would be impossible as someone would have a non-parsing script somewhere that only had half a function written.


It occurs to me that I could commit my development and then check out a copy for Apache to test on, but this isn't suitable. My svn server is slow for a start. It would also mean committing, finding you missed a semicolon and having to commit again, which goes against my commit philosophy of only committing when a milestone, however small, is reached.