EDIT 8\/10\/09: I’ve been told on the ale.org list that ubuntu’s wordpress package has an older version of wordpress and has not been updated recently. So for now I’ll recommend NOT yet using apt to manage your wordpress install.<\/p>\n
otherroute.net<\/strong> is back online.\u00a0 And after doing some work getting a lot of different settings right, I realized that it could have been much easier.<\/p>\n Yup, that’s all it takes.<\/p>\n My last webserver was an Xbox that ran Debian.\u00a0 To set that up, I found all the source files I needed, configured and patched things, compiled and installed.\u00a0 It was a familiar exercise of trying to compile only to find what’s missing, downloading more compressed tar files, and trying to compile everything again.\u00a0 An afternoon or two later and I had a moderately working Apache webserver to host my personal website, projects for school, and other things that wanted to run on Linux.\u00a0 And then I learned about apt<\/em>, which makes life easier by doing all those things for you.\u00a0 A single command and you’ve got Apache running.<\/p>\n I wanted to avoid that unnecessary work this time around when getting WordPress running on my new dedicated Ubuntu machine.\u00a0 I was able to make good use of apt<\/em>.\u00a0 It found Apache2 for me and installed it.\u00a0 It found PHP and MySQL and installed them too.\u00a0 And then I went off configuring things.\u00a0 I made a database user and databases.\u00a0 I worked on the \/var\/www folder tree where I had put WordPress, setting permissions so that Apache could do everything it needed but nothing more.\u00a0 I turned on Apache’s mod-rewrite when the usual WordPress URL formatting wouldn’t work, and then turned on an Apache permission for the site when mod-rewrite still wasn’t working.\u00a0 Before calling everything complete, I wrote a script that would download WordPress’ latest.tar.gz and update the site.\u00a0 And then I found that apt<\/em> could have done all that and the updates would have been integrated in my usual system update process.<\/p>\n I had again wasted a couple afternoons configuring things that I could have just had the system do for me.\u00a0 I hadn’t thought about a different way to do things at the time.\u00a0 I knew how to do get the job done, so I started working the way I knew how.\u00a0 Almost exactly like last time, after I was done I found that someone had provided me with a much easier way to get things started and in the future keep them up to date.\u00a0 This time around, I thought I knew the tools available to me, but my knowledge was dated and the end result was the same as last.<\/p>\n But now I’ve got a new strategy that I learned from this exercise that I didn’t learn before.\u00a0 Before doing things that I know how to do, I need to reevaluate that my known way is the best way.\u00a0 Things change too quick, and nothing from a few years ago should be applied to technology today.\u00a0 Sure, knowing the hard way by hand, like configuring WordPress or compiling Apache, helps in understanding what’s going on, but there’s better, popular and well-known ways to get that done.\u00a0 And check apt<\/em> for everything, even webapps.<\/p>\n","protected":false},"excerpt":{"rendered":" EDIT 8\/10\/09: I’ve been told on the ale.org list that ubuntu’s wordpress package has an older version of wordpress and has not been updated recently. So for now I’ll recommend NOT yet using apt to manage your wordpress install. otherroute.net …<\/p>\nsudo apt-get install wordpress<\/code><\/p>\n