Back in March, I posted an item about Bitnami WordPress, which dealt with the Bitnami stack for WordPress up to version 3.9.0 of WordPress. Since then, Bitnami has made an improvement in the installation, although it comes with one new drawback.
With the earlier (WordPress 3.9.0) version of Bitnami WordPress, the install had to be in the Applications folder (Mac OS X). Now, you can choose where you want Bitnami to install WordPress (version 4.0.1). This helps keep the clutter in your Applications folder to a minimum.
The trade-off is that before, you could have separate accounts on your computer, and each account would have its own WordPress files under Bitnami. With the new version of the installer, every account on your computer sees the same WordPress install, and thus, the same files. If you need separate WordPress installs for separate accounts, you have a couple of options:
- You can install Bitnami WordPress on removable drives (including USB drives), one for each instance you need. At least on my system, though, WordPress does not run very fast off of a USB drive.
- Instead of installing the Bitnami Stack for WordPress, install the Bitnami MAMP Stack as a starting point. This will allow you to install as many instances of WordPress as Bitnami modules as you need.
- Install WordPress Multisite. Setting up WordPress Multisite used to be a truly awful experience. However, it’s gotten better in general, and in specific when using Bitnami, as there is a separate Bitnami WordPress Multisite installer. This is the preferred — A.K.A. WordPress — way of doing things. The “gotcha” here is that you can’t be running the built-in Apache already (which I manage using VirtualHostX), because Multisite needs to be able to bind to Apache port 80.
However you decide to set it up, Bitnami stack for WordPress still offers the best way to develop locally.