This isn't so much a php design question as it is a development environment design question.
Right now I have a development server and a live server. What I do is mount the development server as a ssh drive then do all the development on the development server and whatnot then, whenever I feel the changes (usually really small) are stable enough to be live, I just rsync to push the new changes to the live site and thats that. The obvious problem with this though is that I can't roll back really quickly if something screws up on the live server and of course I can go back in time and check out deleted files or what have you. Basically, no version control, just 1 version being used.
Now everyone says to use subversion of course so I have been trying to get that going but I can't think of how to setup my situation. I would like to use eclipse because of its easy to use subversion plugin but there are problems with this. I can't have my workspace on a remote server, only on my local machine but I want to have the development on the development server since the setup is exactly the same as the live server.
So my question is, what would be the best setup to keep version control AND have a proper development cycle?
[56k Warning] Development environment with version control
Moderator: General Moderators
- inghamn
- Forum Contributor
- Posts: 174
- Joined: Mon Apr 16, 2007 10:33 am
- Location: Bloomington, IN, USA
Re: Development environment with version control
I work in a locally checkout out sandbox, and copy each file across to a dev web server as I edit them. I keep the two dolphin windows side by side in a tree view, so I can quickly copy whatever files I need.
I commit once I got a working changeset, which keeps my subversion log relatively close to a "What's new". Kdesvn is the bomb, by the way.
Ecilpse really doesn't offer me anything either, since I work on remote servers using local sandboxes. These days I've been using a lot of Komodo Edit. I'd like to go back to Kate, but KDE 4's got this bug, you see....it's annoying
I commit once I got a working changeset, which keeps my subversion log relatively close to a "What's new". Kdesvn is the bomb, by the way.
Ecilpse really doesn't offer me anything either, since I work on remote servers using local sandboxes. These days I've been using a lot of Komodo Edit. I'd like to go back to Kate, but KDE 4's got this bug, you see....it's annoying
- Attachments
-
- screen.jpg (201.96 KiB) Viewed 634 times
Re: Development environment with version control
Coda for the Mac is a one-window editor with a built in SVN client AND a built in terminal. Also the PHP manual comes with it, but that's not really a make-or-break feature.
http://www.panic.com/coda
http://www.panic.com/coda