TUTORIAL: Developing Locally on WordPress with Remote Database Over SSH

Today, I went about setting up a local WordPress install for some development I am doing at work. The problem that existed is that I didn’t want to bring the database from the existing development server site into my local MySQL instance. It’s far too big. I figured this could be done via an SSH tunnel and so, I set abut trying to figure it out. The situation worked flawlessly and so, for your sake (and for myself for the future), I give you the steps.

Setting up the SSH Tunnel

I run a local MySQL server and that runs on the standard MySQL port 3306. So as these things go, I can’t bind anything else to port 3306 locally. I have to use an alternate port number. I chose 5555, but you can use whatever you want.

The command to run in a Terminal window is:

ssh -N -L 5555:127.0.0.1:3306 remoteuser@remotedomain.com -vv

A little bit about what this means.

the -N flag means that when connecting via SSH, we are not going to execute any commands. This is necessary for tunnelling as, we literally, will not execute any commands on the remote server. Therefore, we won’t get a command prompt.

the -L flag tells SSH that we are going to port forward. The following portion, 5555:127.0.0.1:3306 combined with the -L flag means, literally, forward all traffic on localhost (127.0.0.1) connecting on port 5555 to the remote server’s port 3306 (standard MySQL listening port).

The remote server and ssh connection is handled by remoteuser@remotedomain.com. This seems obvious, but just in case. You may be prompted to enter your SSH password.

The final part can be omitted, but I like to keep it there so I know what’s happening. The -vv flag tells the SSH daemon to be extra verbose about what is happening with the connection. It’s sort of a good way to debug if you need to, and to know that the port forwarding is actually taking place.

Configuring WordPress to use the Tunnel

Now that we have a successful SSH tunnel, you have to configure WordPress to use it. In the wp-config.php file, simply modify the DB_HOST constant to read:

1
define( 'DB_HOST', '127.0.0.1:5555' );

You need to add two more variables, though, to override WordPress’ existing siteurl and home options to allow you to work with the localhost domain, instead of redirecting to the remotedomain.com that is configured in WordPress.

1
2
3
define( 'WP_HOME', 'http://localhost' );

define( 'WP_SITEURL', 'http://localhost' );

BOOM!

With these configurations in place, loading up WordPress should now load in the database content from the remote host and you can get to work on local development. Word to the wise… don’t close the terminal window with the tunnel or the tunnel will be severed. If you have to minimize it so it’s not annoying you, go for it… just don’t close it.

TECHcocktail DC – The DC Tech Scene is definitely back

I have seen my share of networking events. Back during the dotcom era it was full of open bars and crazy companies with the latest software to change your life in some way. Then it was all about buying stuff on the web or a portal for something or another.

After the bubble burst most people were just trying to hold on and all that you had a choice between in the DC area were NVTC (Northern VA Tech Council) and Potomac Officer Club events. NVTC was very government focused and who mostly showed up were service providers (I have the 100′s of insurance and lawyer business cards to prove it). POC events were big events with well known people but not alot of good networking.

One good networking event I liked was the Tech Prayer breakfast but that was only once a year. What most of us were left with was going to conferences, usually not here, to get our networking on and find fellow entrepreneurs and real innovative thinkers.

Lately, there has been a change in the winds here in the DC area. With events like PodCampDC and Social Media Club’s events we are starting to see our cutting edge tech scene finally re-emerge. Last Thursday night it was totally confirmed with the TECH Cocktail DC event. It was held at MCCXXIII (1223) in DC. A swanky place that is over-priced for my usual weekend partying but this event had cheap drinks (thank you drink tickets) and about 300 people.

Below is a picture of the scene at the height of the evening.

200804271640.jpg

While there have been many events that have drawn 400 people, this was different. Almost everyone was doing something startup related that was really cutting edge. There were social media people there (Technosailor and me included), innovative startups and actual investors looking to network.

There were also a great group of sponsors with great products to demo. Here is a great list from Jimmy over at EastCoastBlogging:

AwayFind – a product aimed at helping combat the email problem by letting your contacts get in touch with you via an online form.

iGala – a digital photo frame with a touchscreen interface that connects directly to Flickr and Gmail to stream photos to the frame like a slideshow.

Loladex – offers local recommendations from your trusted network of Facebook friends.

Odeo – launched a new beta verision which offers both search and personalized content (audio and video) recommendations.

Voxant – a free licensed content offering for publishers which offers a pageview based revenue share to anyone that embeds the content on a their site.

WhyGoSolo – a new social networking site aimed at helping you to create spontaneous new connections so, as its name implies, you won’t go solo any longer.

A huge amount of thanks go out to Frank Gruber and Eric Olson who do the TECH Cocktails around the country and they need to do it more than once a year here.

The vibe around this region is changing and since we will never will be Silicon Valley and never want to be, it is fantastic to see that there is a refreshed ecosystem of entrepreneurship here in the region.

Photo courtesy of jgarber

Editor’s Note: Some comments don’t seem to apply to this post as viewers of a show I was on were instructed to leave comments on this blog to get an invite to BrightKite. These comments will be approved but do not necessarily go with this post. Sorry!