Survival guide to LAMP: Rushing forward

I have put aside all efforts in regards to my bookbinding work, and all photography, and other writing about hikes or cats or life in miniature, in order to focus on finishing the LAMP series as quickly as possible. (Other than those efforts that pay the bills, of course.)

As I work on the next installment, a couple of caveats:

First, I’m going to be editing the last essay and removing the reference to using install-config.php for WordPress, replacing it with instructions on editing the configuration file. I had forgotten that to run install-config.php requires that the directory is writable, and this makes this choice the more complex installation routine to follow rather than the least.

Second, there seems to be confusion that one can’t charge for open source software. As I mentioned earlier in Spin City, you can charge, but you need to carefully set expectations for people using your software. Matt at WordPress has said they won’t charge, but even if they do, we can copy the software and go our own way if we wish–it’s open source. Dean Allen at Textpattern is contemplating charging for the commercial uses of his product, but he’s setting expectations at the start for this direction.

Software and ‘gotcha!’ don’t go together well.

Third, I will be talking about Textpattern and how to use it and demonstrate moving a Movable Type weblog to the product, and altering the templates, but I won’t be making any modifications to the underlying code for this product. Again, it is a single developer product, and not the one I’ve chosen for my own weblog. I’m reserving actual code changes to my work with WordPress, only.

As I continue writing on LAMP, I wouldn’t mind some feedback from people as to what they want to hear about in these essays. Consider this thread an open thread on this topic.

Print Friendly, PDF & Email