Just a discussion on what people at home use for their developmental codes!

I currently use xammp, the lite version.

I find it very frustrating to keep uploading files (I don't like built in FTP) everytime I change a code, I just want to be able to change 1 thing and have it live when I'm developing something…

I'm a PHP/MySQL Developer, and unlike HTML, I have to upload the file everytime to view it online! xammp just makes my life so much easier!

LAMPP on a VMWare workstation. If there is an absolute need to do it remotely I use Nusphere PHPed Ctl+Shft+S lets you save and upload instantaneously much like working locally.

Cheers.

Like many probably, I have a localhost set up as well. Fooled around with xamp and a number of other "wamp" installers, before just getting down to the nitty-gritty and doing it myself. Don't get me wrong, there's nothing wrong with xamp, well besides the fact when you want to change some setting and have 4 php.ini files to choose from (of which only 1 will make the actual change!).

What IDE do you use for coding? Some of them have the option to automatically update the file via FTP when you save it. I've never personally used this option but it is available.

XAMPP or custom installation of Apache, MySQL and PHP work very nicely. I normally use Dreamweaver's Code View and do my previewing in the browser (Firefox, Internet Explorer) :).

I use dreamweaver when setting my div's up… other than that I use notepad. Dreamweaver has a built in FTP uploader, so when you save it uploads. But I'm not to keen on that :)

xammp is nice though!

Apache, Mysql5, PHP5 on localhost, all installed manually. PSPad for editing files. Manually upload any file.

Manually upload? Wouldn't you just put it in your 'root' directory of your localhost, that way when you do hit save it would basically be like auto uploading?

Just curious…

Manually upload? Wouldn't you just put it in your 'root' directory of your localhost, that way when you do hit save it would basically be like auto uploading?

Just curious…

This is not ideal, when you save a page you do not want immediately to be uploaded on the production server (it would be slow, the page may contain errors etc.). It would be better to commit all changes in the end.

The auto-upload thing would work great for static websites. But when you build dynamic sites there will be some files that are different in localhost and in production. You will not want this files to be uploaded (so the software must have exclude filters etc.).


Generally, when I have to do updates on some sites, the number of scripts is low, so I keep track what I have changed and then manually upload them with ftp.

I am using PSPad for editing the scripts, but I do not like the way it handles projects.

I use old box setup with linux / mysql / apache that is used as dev server. All projects on it are located in work/ directory which is exported via NFS to my linux desktop and via Samba for my wife's windows desktop.

I use LAMP on a local server; makes development easier.

xampp before, now abyss.

I use WAMP server
it's good and easy to use

A different approach
Work PC setup same software as production server, Centos-mysql-apache-perl etc.
and same configuration, such as Apache DocumentRoot, users path and so

When we have a new customer
we manually add CustomerDomain.loc to hosts
modify the vHosts accordingly.
In this way we can test everything locally (http:/www.CustomerDomain.loc).
Upload when we are sure that everything is working without any errors in the error.logs
We dont have to worry if it will work on our production server.
As a policy we never use auto-upload.
We manually upload the files (gFTP) and preserve the files timestamp

We use Blue Fish , Komode IDE and even HomeSite (with wine) for codding

Although the initial setup looks complicated and time consuming, in the end it pays off.
as we locally have exactly the same files/configs as on the server (except DB passwords)
We can do/view any changes locally without having to do any changes to the configuration.
If the customers finds any bugs/problems we can replicate it locally and solve it.