Creating an EXE installation wizard?

[shreder]

Hello.

Is it possible to create an exe installation wizard for a php script that will automatically upload all files to the ftp server, chmod directories, create a mysql database on cPanel and maybe even configure cronjobs on cpanel?

Thank you.

[devbanana]

Well sure, if you know C# or something of the sort...

Assuming you don't, why not make a PHP script to do all that?

[G.Schuster]

Sury, use NSIS: http://nsis.sourceforge.net
I use it to install a complete Webserver and a PHP app on the clients PC, works like a charm but is hard work until you see first really good looking results.
It's not a click'n'run solution - you'll have to code everything by yourself but there are many classes/extensions that help you.

[triexa]

ionCube has a product - Package Foundry - that does exactly what you want. I have yet to try it but have used software that uses it's installer and it works great.

[ioncube]

Thanks Triexa for the mention of IPF. Looking at the list of requirements from the poster, one feature that isn't in IPF is creation and setup of databases, because this really belongs in the application itself. The rationale for this in IPF, and it would apply to a home-brew solution too, was that first off it's not uncommon for security reasons not to allow remote connections to a database, and if the only way to create the database schemas was remotely then you'd be stuffed if you hit a host that wouldn't allow this. Another reason to consider is that sometime into the use of the installed application, the user may want to roll back for some reason and setup the database again; even though IPF installers remember that an upload was successful and skip the upload stages when rerun, having to go back to the installer to setup the DB again would still be annoying. A further consideration is that whilst installers are great for many users, some users might want to download and install software directly onto their web server, e.g. with wget for a tar.gz. Not only that, they may not even own a Windows machine to be able to run an installer in the first place. So once again, if the only way to setup the database was via the installer, the end user would be stuffed.

So, database setup should be coded into the web application itself. If an installer provides a way to launch a script once the application is installed, then installation can lead seamlessly into the setup of the application, just as it does with traditional local windows apps, and then onto the database setup.