svn, netbean and codeigniter

blackhorse

I am trying to find out a best approach.

Here is our team and environment

1) small php developers team, 2-4 programmers per project.

2) use netbean ide.
3) use codeigniter framework. (which frameworks shouldn't make any difference, but just in case)
4) svn.

So here is what we should have.

1) Subversion Repository.
2) Every developer has working directory on his PC.
3) Web Site is on remote server.

So it will work like this

1) In the beginning every Developer check out and create a working directory.
2) Create Netbean project based on the working directory.
3) Set the run configuration, run as remote web site, remote site is on a dev sever, or run as a local web site

4) So every developers will svn update first and then work on the working directory (netbean project) on his local pc.
5) Then run, netbean will upload the files to the remote web site and run.
6) Commit to the Repository when it is done.

So far is it ok? Any advices?

My question is how should the developer or team update the production site given the above environment? Which approach will be smooth, efficient and with less errors.

The production site is not so crucial, every developer has the rights to upload to and run the production site too.

blackhorse

An easy approach is the

Product site will be another working copy of the repository. But no body actually directly work on this working copy. It only get updates from the repository.

What approach you guys use in simple php projects? Use svn seriously or "quick, dirty but work well", just back up once a while

sneakyimp

I'm not super familiar with Netbean, but I have worked on a similar setup using Eclipse -- which has a PHP 'Perspective' and also an SVN client. We'd simply save files on local machine and they'd run in locally installed web browser. On commit into SVN, we'd have auto-commit script that would publish them to a development server where we could see them run on the server.

In the end we'd run svn co to populate the live site with the code directly from SVN.

For backups, the server (repository and all) was continuously backed up by a special solution offered by our hosting provider.

blackhorse

For the web sites, there are some information such as physical path, or the domain name? How do you set up the development server and production sever, so every line of codes work on dev and you will be sure it work on production too. and you just need to svn the dev to production?

physical path issue may be easy to handle, just set up the physical path as the same in dev and production? or there are better ways?

But how about domain name?

such as the production site may be http://www.mysite.com on the production server. And on the dev sever, how do you set up the dev server, and http://www.mysite.com on dev server points to the dev server not the production sever? Somehow set up dns service on the dev server to solve this problem?

If everything to the producion is through svn. How about if you have huge files, like huge videos files, you can still use svn to get them to the repository and from repository to the production?

Thanks!

sneakyimp

it simply isn't possible as far as i know to have the dev site and the live one be identical. i think the trick is to isolate the differences in as few files as possible and don't put those files in SVN.

I would not put huge files in SVN. SVN repositories can be quite unstable sometimes. And those big files probably don't change much so version control isn't really critical.