Aren’t you being excessively picky ? In my home’s wifi connection I cannot notice any lag at all. Only difference is a much lower sustained throughput (e.g. copying large amounts of data).

That mostly applies to general php. I’m also interested in WordPress templates, since this still needs a lot of work as you can see. But useful nonetheless. I also use git for a lot of things. Quite useful.

@Diogo Gomes

Laziness is good. It makes you rest.
cakePHP ? Will have a look. Thanks.

@Nuno Inacio

Option 2 takes more time because I have my desktop customized for development, but not the server. By the way, I use gvim for most of my editing/coding, so it implies ssh -X. Connection is over 802.11g, so its not very responsive. Wifi sucks.

Have to give django a change… let’s see.

@all

I’ve been cutting down on the laziness. I’m always going about with my GTD. Will give more info on that later.

PS: I like blogs.

Master plan: start planet HNG :>

Option 2 – “Too much work to get into a usable state.” – what do you mean by that ?

Option 3 – “Take advantage of your desktop/development environment.” – if you install vim on your server, you’ll have a complete dev environment

More seriously, I think 2 and 3 are more or less equivalent. In 2 you have to fuss about with X, in 3 you have to fuss with sshfs. Sluggishness will be similar.

I believe it all boils down to how slow the connection is. If it were good enough I would use option 2 (or 3 – matter of taste). If not I would go for 1.

BTW: I know you know Python. How about giving Django a try ?

I think option 3 is the best as long as you have two instances of your project (say: default + devel) because when you are finnish you just need to rename

BTW: have you tried moving your PHP projects to cakePHP ? It makes your life much easier

As for the workflow, if you develop locally you can use a SCM like git or svn and perform commits/chekouts in a dev branch. You can also deploy through ftp if you are into that. But since all development is local in practice the server side testing will only be integration testing.

In the remote development universe, you can use a separate installation for dev purposes only. Keep in mind here that i do not know the inner working os a WordPress install or how easy is to support multiple sites/blogs in it.

My workflow is simple. Light weight server, a development database (copy of the original), git for versioning and a separate copy of the site (usually in my user directory and not in the root of the server)

Hope it helps.