What is a good piece of software to be able to have a set of files hosted from a localhost on Windows 7?
IIS 7 - really easy to use and it comes with a default website already setup. Just drop your files in and right click the site, then click start.
If you are interested in a LAMP port for Windows (preferring Apache over the built-in IIS) check out XAMPP. It bundles everything you typically need on a web server: Apache web server, MySQL database with web admin UI, PHP and Perl languagues, FTP and mail servers.
There is also WAMP, but I have no experience with that.
I'm using apache. Using apache on windows
You can install it, then install php ect. as you need them...
If you're looking for ASP/ASPX then either use VS internal web server, or IIS.
Assuming that your looking for a PHP/Apache/MySQL environment, I would recommend EasyPHP. It comes with the latest version of PHP, Apache, MySQL, Phpmyadmin and a pretty easy to use admin panel.
easy php is good stuff, my problem with it is that its just toooo slow... but the features are nice, sometimes you'd not mind the slowness because of the features on the Admin Panel that comes with it... But if you're looking for speed... then XAMPP or IIS is the way to go...
if you install them both you gonna need to configure the Apache and give it a port that does not clash with IIS...
Related
This might be a silly question, but I'm new to web-dev, so here it is:
I recently installed MAMP on my windows system [yes, MAMP works on windows too] and it shows Apache and MySQL server to be active, but neither I have installed any of these servers, nor I can find them in "Services" of my system.
So I wanted to ask whether I'll need to explicitly install both of these servers or not.
Also, If there's no need of explicit installation, how does MAMP work ? like, giving access to both these servers without actually installing them ? [A brief explanation would be enough]
T.I.A.
They come with MAMP. You can access phpMyAdmin under the Tools menu in the page that automatically opens up when you start MAMP, for me it is http://localhost/MAMP/?language=English
I'm extremely new to building websites. I'm attempting to create a website using Joomla (and a Joomla template) and plan to use a webhost, bluehost.com. Do I still need to download XAMPP if I'm using bluehost? What's the point or use of XAMPP?
No, you don't need it. The likes of Xampp and Wamp are offline development environments that allow you to develop on your computer/localhost. So rather than making any changes to a live website that might result in the site breaking, you can simply take a backup, set it up on your localhost and testing your changes there. Be sure that you configure your localhost to use the same server settings as your live host as there might be some potential differences that may prevent things from working.
Seeing as you're new to web development, my advice would be to set up a local environment using either Xampp or Wamp, build your site on there, then move it to your live host when you feel ready to.
Charette,
Just have Bluehost install joomla for you. Install the free Akeeba backup yourself, and then start playing around with the demo content.
http://www.bluehost.com/joomla
Ask specific questions in the joomla forum:
http://forum.joomla.org/
Have fun
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.
Good evening everyone, I been workin' on Ubuntu server, and I work from a remote pc that uses Windows XP Pro and ubuntu 9.10 too...ok the thing is...I installed joomla 1.5 last version on the ubuntu server from my pc and everything was good until I had to fill the ftp information, never found the connection path so I installed without it...now I have my joomla but I want to install some extensions and here's the problem, with the FTP Filezilla runin' on windows I connect perfectly with the server as with SSH in Ubuntu, but when I try to fill the FTP information on joomla, it doesnt recognizes the path, any idea about it?...
If it's 1.5, you really don't need the FTP in the Joomla configuration set.
Try this: disable FTP in Joomla. (Global Configuration / Server)
Then try to install a component / module / plugin / whatever.
It's a bit counterintuitive, but will most likely work - or at least it does in my experience. Joomla's file system can manage files for you... it's that whole content management system thing.
If you're dead set on enabling FTP, then check the Global Configuration, and see what the :Path to Temp-folder: is set to. In 1and1's case, it'll be something like:
/homepages/26/d264424517/htdocs/english/tmp
Strip the 'tmp' and you'll see where '/english' would be the root path for the FTP setting, but again you most likely don't need it.
Please read the FTP Layer hints on the Joomla! forum. The info here had helped me resolved similar problems in the past.
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.