Test Wordpress offline?

[ACTIONpack]

I'm learning how to use Wordpress and don't want it on the servers just yet. It's going to be a custom design blog and will like to see how it runs before uploading to the servers. Also, the website is not finish yet so can't test it just yet on a server site.

[Depicus]

I do it all the time, are you on Mac or PC ?

Basically you just need Apache and MySQL or even IIS - but probably best to try and mirror what the server has.

I just put an entry in my host file, say depicus.local and point to 127.0.0.1 then set up apache to point a virtual server to a folder in my docs and away you go.

[Copernic Reporter]

http://bitnami.org/stack/wordpress

http://www.instantwp.com/

http://wordpress-portable.webnode.com/

http://www.apachefri...g/en/xampp.html

http://www.wampserver.com/en/

[the better twin]

Just install Xampp. Copy the wordpress files to the htdocs folder. set up the database with phpmyadmin and away you go.

Like so : http://webdesignerwall.com/tutorials/installing-wordpress-locally

[ACTIONpack]

Thanks, I'm on my Windows 7 machine but when I go into work, I will be on a MAC.

[-Alex-]

Install XAMPP on your PC, allow Apache to be world-viewable (not only from localhost), and hit 192.168.x.x on your Mac.

[threetonesun]

  On 11/06/2012 at 08:21, ACTIONpack said:

Thanks, I'm on my Windows 7 machine but when I go into work, I will be on a MAC.

If you're on a Mac, use MAMP.

It's also a good idea to have a test site served somewhere just so you can check for compatibility purposes.

[farmeunit]

  On 11/06/2012 at 07:44, ACTIONpack said:

I'm learning how to use Wordpress and don't want it on the servers just yet. It's going to be a custom design blog and will like to see how it runs before uploading to the servers. Also, the website is not finish yet so can't test it just yet on a server site.

You can also upload to a subdirectory of your webhost, then move to where you want later. It just a matter of changing a few config files.

[PNWDweller]

Like others have said - either develop it on your local machine on your network, or dev it on a hosting server.

I have at least two sites on TLD's that are not indexed or known by search engines. When building sites, it is not longer "Build it and they will come." People will probably never see it or know it exists if you put it on your hosting account and put a no follow, no index directive in the robots file.

What I do a mix of things myself - put on my own server (I have a VPS), and poison my DNS to make my machine think it is a fully qualified domain name. OR, I have two spare boxes, so I will also if need be, place a server on a spare box and then point to it using dyndns or the equivalent.

If you are wanting to test from both home/work, a dynamic DNS will make your life easier. Else, on a hosted server, knowing the ip/~username combo (If cPanel), for testing.