General discussion


Favorite tools for LAMP development?

By RexWorld ·
So I've been dragged somewhat reluctantly back into the software development world, working on a PHP interface that lets users search our content database stored in MySQL. Basically there's nobody else available to work on this, so I'm jumping in to help out even though I kinda suck as a programmer.

This is my first experience in the LAMP world (Linux, Apache, MySQL, PHP). My last official job as a software engineer involved JSP and Java connecting to Sybase. For that we used primarily Eclipse, plus a little Sybase command-line shell that I'd access thru my Linux shell account.

For this LAMP work I'm using a weird mix of open source, free, and commercial software. For the PHP code I'm editing in Dreamweaver, mostly because I use it for a few other projects so rather than fire up both Dreamweaver and Eclipse I just edit the PHP code in Dreamweaver.

Unfortunately I can't get WebDAV working right so I'm editing the PHP file locally, then I use WinSCP to copy the file up to the Apache docroot. And when I have to run test queries in the MySQL database I've been using SQLyog.

Are there better options to replace some of the tools I already am using? And what other tools have you found useful when working in this LAMP world?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Personally I use

by Jaqui In reply to Favorite tools for LAMP d ...

screem and glimmer and kdevelop for php scripting.
for most scripting actually.

to run mass query tests on a database I usually use phpmyadmin or phppgadmin [ nice clean web interface to control both engines, and will manage all aspects of a database.] both available through

i only use linux so I have no windows tools suggestions. :)

Collapse -

An old Dinosaur, I am

by joe In reply to Favorite tools for LAMP d ...

I use vi(m) for all the scripting, coding, typing of any kind. As for sql testing I use either the command line interface or, if the web interface is finished, I'll do it through there.

You know, it takes me longer to write code, even html, using anything that is smart enough to help you. Back when I learned all this stuff none of those tools existed so now I just hack by hand and use what library of files I've got handy to cut'n'paste bit of code together.

Collapse -

We don't need no IDE

by Lawrence0 In reply to Favorite tools for LAMP d ...

I'm using Quanta Plus on Linux for Web stuff, but only because it handles ftp nicely. Most IDEs seem to get in the way.

When I switch to windows for testing with IE, I just use wordPad or its equivalent. (Notepad doesn't handle Unix end lines.) I use basic DOS ftp or a free graphical ftp app depending on which box I'm using to load the fixes to the server.

I use telnet to get to the database's mySQL interface for maintenance and testing SQL.

IDEs always seem to get in the way.

Collapse -

Mac OSX, Eclipse, PHPEclipse, PHPMyAdmin

by Taggalucci In reply to Favorite tools for LAMP d ...

PHPMyAdmin is great for managing MySQL. You need to have PHP and Apache installed for this.

Eclipse with the PHPEclipse Plugin is an excellent PHP IDE. Eclipse has numerous useful features and there are many useful plugins available for it which will support LAMP development.

You should try to get WebDAV or FTP working, as this ensures the IDE is useful, and not an inconvenience when editing and pushing to the server when testing the changes you make to the code. Check the permissions for the directory in which you are trying to write to on the destination server.

Integrate Eclipse with CVS to get version control (though Eclipse has some level of history storage).

Use an Apple Mac. OSX lends itself to being a fantastic test bed and, IMHO, a superior platform. Being BSD-based, you can install all the packages required for LAMP and there are some great Carbon (OSX UI) configuration Apps for managing MySQL and Apache. I have the entire production environment (including a Windows 2003 Server with Visual Studio .net emulated in Virtual PC) replicated on an Apple G4 PowerBook. This means that I can develop and test on the move and only some environment variables need to change (which can be set by Apache Env Vars) between environments.

Related Discussions

Related Forums