I've been using WAMP to work with PHP. These days after joining PHP mailing list from php.org, I want to have a try on EasyPHP. Though I'm not confident to get on alone with EasyPHP :)
So my question is can WAMP and EasyPHP be installed the same time on Windows7 (or Ubuntu OS)?
Yes, they can. You might take a performance hit from running both OSes at once (which you can do using a VM), but as long as you don't try to make them share resources (e.g. ports and config files), they won't even know the other exists.
Related
Recently lost my hard drive where I had WAMP installed and Imagick working.
Someone else did that part for me way back.
Reinstalling Win7 and getting everything working again = nightmare.
So I installed the latest version of WAMP - NO Imagick.
3 days of trying all the solutions on this site (and some others - sorry) and got nowhere.
Does anyone know of a "one shot" installation that will work out the box?
Maybe a fork of one of them - I looked but found nothing
Or maybe I should install Ubuntu onto an old PC and use that as a web server on my home LAN?
Seriously - they are depreciating the GD library some time soon and Imagick is apparently the successor but no-one supports Imagick natively.
Jumping through all sorts of hoops is no guarantee that it will work either as I have painfully found out.
Thanks in advance people.
WAMP and XAMPP are not up to speed with the transition from the soon to be removed GD library to the ImageMagic library and it would seem that neither are planning to bring their products up to date any time soon.
That leaves many users with a major problem as most web site developers need to be able to manipulate images at some time or another during their work.
For users who are not at a reasonably high level of expertize as far as messing around in the guts of the (in my case, Windows) operating systems, this is a nightmare and can be downright dangerous.
I did find what seemed to be a viable alternative in WampDeveloper Pro but unless you specifically go looking for it, their website is very hush-hush about the fact that its going to cost you over $125 to get it working.
You only find out about this at the first run after installing.
So my options are the following:
Put one of the Ubuntu distributions on a VM
or
Find an old drive, install it into your PC and make the PC dual boot using a Ubuntu distribution.
The second option will "ease" me into converting from Microsoft based OS reliance to a Linux based OS however if that does not work out, I do have the option to create an Ubuntu VM under the Windows system (I have used VM for a while under Windows) and use that in place of the other Windows based web server alternatives.
Either way I will be able to carry on servicing my clients and making a living without spending money or having a stroke due to pure frustration.
I may regret this decision BUT I may start wondering to myself "Now why did you wait so long?"
I have vagrant installed on my Windows 7 machine, currently it has an installation hooked up with VirtualBox & a CentoOS install.
While it everything does work, and the server is all configured and the PHP is running ok it really does seem to crawl. I currently have a development version of Magento on here and it is much much slower than I would expect. Occassionally some pages (the checkout ones) can take up-to 2 minutes to process and bring the user to the next page, obviously this makes development very frustrating and slow.
Can anyone suggest any ideas on the best way to optimise my vagrant box?
p.s i've not set this up myself so i am not fully aware of all its configs/settings etc...
Magento has a lot of files, and Virtualbox file share mechanism between Linux and Windows is very slow. Workaround is to use samba saerver on guest and mount it on host.
I have a big problem with my FileZilla on my current Ubuntu 12.10 installation so its unusable. First of all some facts:
FileZilla works with my Router/WLan etc. setup on windows perfectly.
It even worked on Ubuntu before upgrading (allthough I'm not sure if it affects at first 12.04 or 12.10)
So the Problem I guess is related to my Ubuntu
The problems are the following:
it's slow
I often have connection timeouts while transfering a couple of files or often when changing directories
often files get transferred without their contents
furthermore if bigger uploads timeout or stop I cannot determine what has allready been uploaded because it does not seem to follow any order subdirectorywise.
I'm kind of a Linux beginner too so I have no idea what I can do about this. Hopefully anybody can help.
It seems that I encountered the same problem with you. It's all right using FileZilla on Windows, but unstable on Ubuntu. Frequent timeout after MSLD command occurred.
I solved the problem by using the ftp command instead. It's built-in and rather simple. You could also check if the ftp connection is OK in Ubuntu with this tool. If it is, then it might be something wrong with FileZilla. (I guess)
I wrote an article about this: http://pengwenqiang.wordpress.com/2013/11/07/the-usage-of-the-basic-ftp-command-in-linux/
Hope it helps.
I am totally new to programming and to some new technologies. Right now I am using WAMP on my Windows Vista. For me, using WAMP is very convenient because I am gonna install once and no need for complicated configuration.
I was OK with it until someone told me that it's not good to use WAMP, EasyPHP, XAMPP, and MAMP because if one of the components such as MySQL crashes it won't work anymore. He said that it's best to install them separately and do a pain in the ass configure later.
Please advice.
For development and small low volume sites WAMP is just fine!.
If you are not reasonably experienced with installing configuring Apache, php and whatever SQL you are using then a WAMP package is still the better option as a suboptimal configuration is better than a broken one.
Once you are deploying to production and need to deal with larger transaction volumes and security issues then you should really install the components separately and custom configure for your particular needs.
However realistically if you get as far as a small/medium volume production application it will probably be deployed on a rented application infrastructure where all this will be done for you.
So yes stick with WAMP. Time is better spent getting your App right than learning the esoteric settings in the various config files.
WAMP has a clear goal: to provide a usable PHP environment directly out of the box. 0 configuration needed. 0 knowledge needed. You click and it works. If you are a newcomer, this is an obvious choice.
Configuring complex software like Apache and PHP is really difficult for a newcomer. If you're not actually going to use WAMP in a production environment, there is no reason you would have to touch the default configuration.
Making a separate installation for each of those components just doesn't make sense if you're discovering programming. When you're more experienced, you'll certainly enjoy editing obscure configuration files on a distant machine.
My advice is to go for WAMP on your development PC.
I don't think that the 'crash argument' is valid. It makes no difference if you install a bundle or single component - the problem is find the cause and to fix it. The bundles are designed for an easy start, the price to pay is that the configuration isn't meant for production use. I would prefer to learn using a local bundle and apply my knowledge/skills when I configure a production server (without any pain, because then I can).
WAMP--Windows Apache MySQL PHP
XAMPP--X(Multi OS) Apache MySQL PHP Perl
Wamp is better for newbies, To install, customize easily and learn the basic things in user friendly. Mainly on enabling the dll's in wamp is more easy than Xampp. But it will create many problems as kind of, when we restart the server it may not restarted properly and you need to do additional thing as restart your system or need to re-install wamp. The main drawback is, it support Windows Alone. Normally nowadays everyone prefer to go with Linux server as it have more security purpose. Hence if u develop using wamp, its useless for Linux Production Environment.
So i would suggest Xampp and its also a developer's choice.
It have more features than Wamp,
they are:
Tomcat
Perl
Supports Multi-OS
Filezilla FTP
PHP4
PHP5
It is better to restart the server separately for MySQL, Apache, Mercury, FTP.
For enabling the dll's in Xampp is not a hard task for developer and its a stable server.
If you want to develop against WordPress (i.e., have a local instance running on your machine so you can develop themes, get blogs and sites laid out, etc.) and you're running Windows on your development machine with IIS and SQL Server already installed, what's the best way to do it?
I found a method online which sets up a little "mini" server on Windows running instances of Apache and MySQL but they didn't advise using it on a machine with IIS already installed. Obviously one could install Apache and MySQL and do it that way but given what Windows affords you (i.e., methods of running PHP in IIS - I think Windows Server 2008 is even optimized for this), is that the best way? Are there ways to run WordPress with SQL Server as the backend? (I wouldn't think so but I thought I'd throw that out there).
And are there methods differing on the version of Windows (i.e., XP, Vista, Vista64)
I run XAMPP on a thumbdrive and install WordPress (usually multiple instances of it) on there. Then I start up XAMPP when I'm going to work on Wordpress development.
EDIT: this setup does require that IIS be stopped when the XAMPP server is running (or some byzantine configuration magic that I've never bothered to figure out. Since most of my personal needs for local IIS development are handled by the Visual Studio built-in instance of IIS, which can run side-by-side with XAMPP, I rarely have bother with anything else, but that probably won't work for everyone.
Install PHP, run Wordpress in IIS. Install MySQL which can be run side-by-side with MSSQL. The only thing you'll miss using IIS over Apache is mod_rewrite for prettier URLs.
Avoid running IIS and Apache on the same machine if at all possible. IIS likes to bind to all available IPs blocking Apache from binding to an IP, which you can get around if necessary, but it's not immediately clear what's happening.
I've been running this setup for years.
Since you are interested in developing for Wordpress I strongly suggest you use the most common WP setup: Apache, PHP and MySQL.
You can run Apache and IIS at the same time (I have IIS listening on port 81 and Apache on 80) or you can run only one at a time (create 2 bat files to start/stop the servers using the net start/stop command).
You can use IIS, PHP, MySQL to run Wordpress but there are some subtle differences that can drive you crazy or cause problems when you deploy on Apache.
You can certainly run IIS and Apache on the same box. We do it currently with Documentum/Apache and IIS on the same server. Just pick a range of addresses for one web server - 808x for Apache for example.
You should also consider using Thinstall from VMWare where you can virutalize an entire application - registry, .Net and all - distribute as a single .EXE. We do this now for packaging applications that don't play well together. You might want to virtualize Wordpress/Appache/MySql and set an IP (808x) for that configuration. This way you can move this to any server with IIS and it'll play well with different configurations.