Table of contents
- 1. How to start/stop the servers?
- 2. How to change the default URL to root?
- 2.1. Automatic approach
- 2.2. Manual approach
- 3. How to change the WordPress domain name?
- 4. How to create a full backup of WordPress?
- 5. How to upgrade WordPress?
- 6. How to install a plugin on WordPress?
- 7. How to configure the email settings of WordPress?
- 8. How to translate WordPress to my language?
- 9. How to edit the WordPress files?
- 10. How to enable SSL?
- 11. How to debug WordPress errors?
- 12. How to increase the allowed size of the uploaded files?
- 13. How to disable the WordPress wp-cron.php?
- 14. Multisite Support
| How-To Guides How to optimize a default BitNami WordPress install
| Troubleshooting
How to Upgrade Your Amazon Instance
Migration from local installation to the cloud
|
WordPress is a state-of-the-art publishing platform with a focus on aesthetics, web standards, and usability. WordPress is both free and priceless at the same time. The project was started in 2003. Since then it has grown to be the largest self-hosted blogging tool in the world, used on millions of sites and seen by tens of millions of people every day.
Please, take a look to the Quick Start Guide to know the basic use of this Stack.
How to start/stop the servers?
The Stacks include a graphical tool to manage the servers easily. You can find the "manager-windows.exe", "manager-osx" or "manager-linux" tool in your installation directory. Using this tool, you can Start, Stop or Restart the servers and check the log files. You can click on the icon to start it.
On Windows: You can also start the Manager tool from shortcuts: Start -> Program Files -> BitNami Stack -> Manager tool
If you prefer, you can use the "ctlscript.sh" utility from the command line. This script is in the installation directory.

On OS X: You can start the Manager tool from the installation directory or you can use the "ctlscript.sh" utility from a Terminal.
host:~ user$ cd /Applications/application-version host:~ user$ ./ctlscript.sh start
On Linux:
$ cd ~/applicaton-version $ ./ctlscript.sh start
How to change the default URL to root?
Automatic approach
The Virtual Appliances, BitNami Cloud Hosting and AMI images ship a tool called "updateip". Using this tool you be able to configure the URL automatically. It includes a new option to remove the "/wordpress" prefix from the URL. If you want to modify that you can run the following command:
$ sudo /opt/bitnami/apps/wordpress/updateip --appurl /
Now you will be able to access to the WordPress application at http://YOUR_DOMAIN instead of http://YOUR_DOMAIN/wordpress.
On Windows:
This tool is also included for Windows. You can open the "Use BitNami WordPress Stack" command prompt from the Windows shortcuts and run the following comand:
> cd apps\wordpress > updateip.exe --base_directory "C:\Program Files\BitNami WordPress Stack" --appurl /
Manual approach
1) An easy approach to have your application in the root URL is to uncomment the following lines in your application configuration file /installdir/apps/wordpress/conf/wordpress.conf. This approach only changes the initial page of your application, not the internal urls, all the links point to "http://yourdomain/wordpress". If you do not see these lines you can add them at the end of the file. Note that "wordpress" could be wordpress, joomla, drupal, etc.
# Uncomment the following lines to see your application in the root # of your URL. This is not compatible with more than one application. RewriteEngine On RewriteRule ^/$ /wordpress/ [PT]
Using this configuration and restarting the Apache server you can see your initial page of your application in the root URL.
2) Another option is to configure your application to run in the root URL directly. The details are described below (if you have already configured the application using the first method, note that you have to revert the change before continuing with this approach).
If you want to change the default URL from http://your_domain/wordpress to http://your_domain, you should add a "DocumentRoot" entry in your application conf file. Edit the /installdir/apps/wordpress/conf/wordpress.conf file to add this line and commenting the "Alias" entries.
wordpress.conf file content:
DocumentRoot "/installdir/apps/wordpress/htdocs" # Alias /wordpress/ "/installdir/apps/wordpress/htdocs/" # Alias /wordpress "/installdir/apps/wordpress/htdocs" (..)
Some applications also require changes in their configuration files or in the database.
If you want to change the default URL from http://your_domain/wordpress to http://your_domain, you should add a "DocumentRoot" entry in your application conf file. Edit the /opt/bitnami/apps/wordpress/conf/wordpress.conf file to add this line and commenting the "Alias" entries. You can use the "nano" editor:
$ sudo nano /opt/bitnami/apps/wordpress/conf/wordpress.conf
wordpress.conf file content:
DocumentRoot "/opt/bitnami/apps/wordpress/htdocs" # Alias /wordpress/ "/installdir/apps/wordpress/htdocs/" # Alias /wordpress "/installdir/apps/wordpress/htdocs" (...)
Some applications also require changes in their configuration files or in the database.
If you want to change the default URL from http://your_domain/wordpress to http://your_domain, you should add a "DocumentRoot" entry in your application conf file. Edit the /opt/bitnami/apps/wordpress/conf/wordpress.conf file to add this line and commenting the "Alias" entries. You can use the "nano" command line editor or you can also edit this file from your favorite FTP program.
$ sudo nano /opt/bitnami/apps/wordpress/conf/wordpress.conf
wordpress.conf file content:
DocumentRoot "/opt/bitnami/apps/wordpress/htdocs" # Alias /wordpress/ "/installdir/apps/wordpress/htdocs/" # Alias /wordpress "/installdir/apps/wordpress/htdocs" (...)
Some applications also require changes in their configuration files or in the database.
It is also necessary to modify the RewriteBase option to remove the "/wordpress" prefix in the /installdir/apps/wordpress/conf/wordpress.conf file:
<Directory "...">
...
RewriteBase /
RewriteRule . /index.php [L]
...
</Directory>
Don't forget to restart apache after this changes have been done.
| In previous WordPress versions ( < 3.3.1-5 ), it is necessary to update the domain name in the database. If you have changed the URL or the domain, you should update the database using the following command. Note that this command changes the URL to "http://YOUR_DOMAIN/". $ mysql -u root -p -e "USE bitnami_wordpress; UPDATE wp_options SET option_value='http://YOUR_DOMAIN/' WHERE option_name='siteurl' OR option_name='home';"
The "updateip" tool updates the IP automatically during the boot. You can also update it manually. $ sudo /opt/bitnami/apps/wordpress/updateip --machine_hostname NEW_DOMAIN
If you have configured Wordpress to use an static domain name or IP, you should remove or rename the "/opt/bitnami/apps/wordpress/updateip" to disable it. |
How to change the WordPress domain name?
If you are using a WordPress version higher than 3.3.1-5 version, you only have to specify your domain name in the installdir/apps/wordpress/htdocs/wp-config.php file. You can replace the following lines with your domain name:
define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/wordpress');
define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST'] . '/wordpress');
with
define('WP_SITEURL', 'http://example.com/wordpress');
define('WP_HOME', 'http://example.com/wordpress');
If you have previously removed the "/wordpress" prefix from the URL, do not specify it.
| In previous WordPress versions (< 3.3.1-5), it is necessary to update the domain name in the database. Check /Applications/BitNami_Wordpress/Troubleshooting_WordPress#WordPress_can_not_load_images_or_CSS to know how to configure it. |
How to create a full backup of WordPress?
Because BitNami stacks are self-contained, the simplest option for performing your backups is to copy or compress the BitNami Stack installation directory. To do so in a safe manner, you will need to stop all servers, so this method may not be appropriate if you have people accessing the application continously.
On Linux and OS X:
$ cd installdir $ ./ctlscript.sh stop $ cp -r installdir application-backup
Or you can create a tarball:
$ tar -czvf application-backup.tar.gz installdir
Or a zip file:
$ zip -r application-backup.zip installdir/*
To restore this backup you only need to uncompress the backup in the same location. It is important to use the same path that was used when the stack was originally installed.
For example if you have a backup in a Red Hat machine, you can copy it to an Ubuntu Linux machine (a different distro!) in the same location. Then start the servers and that’s all.
$ cd installdir $ ./ctlscript.sh start
You just need to be carefull to keep the same permissions for the files and folders. If you installed as root make sure that in the new machine you copy the files also as root. And this case, if you are also moving MySQL or PostgreSQL, you will need to create those users in the new machine (if they don't exist yet).
On Windows:
On Windows, you should follow the same process. Stop the servers using the shortcuts and copy the whole installation directory. To restore the system, copy the directory to a different Windows machine in the same location and follow these steps from a command prompt:
$ cd installdir $ serviceinstall.bat INSTALL
You can access your BitNami Application at the usual URL.
If you want to create only a database backup, check the following link for MySQL /Components/MySQL#How_to_create_a_database_backup or for PostgreSQL
/Components/PostgreSQL#How_to_create_a_database_backup.3fHow to upgrade WordPress?
It is strongly recommended that you create a backup before starting the update process. If you have important data, it is advisable that you create and try to restore a backup to ensure that everything works properly.
There are two different ways to upgrade your application.
- If you want to upgrade the application and all Stack components PHP, Ruby, MySQL, Apache… You can follow the steps described at How to upgrade the full Stack migrating the data?
- In case you only want to upgrade the application code without modifying any other Stack components, you should follow the guide which is in the application page itself.
In the Wordpress case, you can update Wordpress easily from the Administration panel.
How to install a plugin on WordPress?
You can install any plugin or theme from the Wordpress administration panel. If you are using the Installer, it is necessary to specify your FTP credentials. For Virtual Appliances and AMIs FTP is pre-configured and you do not have to specify them.

- If you are using the Native Stack, you can install plugins, themes or updates if you select "development" mode during the installation. If you selected "production" mode it is necessary to install a FTP server in your machine to be able to install modules from the admin panel.
How to configure the email settings of WordPress?
You can install or enable the "WP Mail SMTP" from the WordPress administration page. Once you installed it you can configure the SMTP settings of your email provider in the Settings panel. For instance, you can use a GMail account settings to send emails from the Wordpress application.

- If you are using the Native Stack or BitNami Cloud Hosting, you can configure the email settings during the WordPress deployment.
How to translate WordPress to my language?
BitNami WordPress has already installed English and Spanish translations currently and we will work for adding more languages. If you want to change the Wordpress language, you can follow these steps:
- Download the translation files for your language from http://codex.wordpress.org/WordPress_in_Your_Language
- Once you have downloaded the files, you have to get the .po and .mo files and copy them into the installdir/apps/wordpress/wp-content/languages folder.
- Edit the installdir/apps/wordpress/wp-config.php file and edit the following line specifying your language code. For example: define('WPLANG', 'es_ES');
- Restart the Apache server and that's all.
How to edit the WordPress files?
For security reasons, WordPress files are not editable from the WordPress application itself. If you are using a Virtual Machine or a Cloud Image, we would suggest to use a FTP client to edit the files remotely.
Another option is to change the permissions to be able to edit from the WordPress application temporary. Note that this configuration is not secure so please revert it after editing the files temporarily:
$ sudo chown daemon:daemon /opt/bitnami/apps/wordpress/htdocs
To revert this change you can run the following command:
$ sudo chown bitnami:daemon /opt/bitnami/apps/wordpress/htdocs
How to enable SSL?
You can see how to configure Apache to enable SSL connections at How to enable SSL to access through https?
How to debug WordPress errors?
Once Apache starts, it will create two log files, the access_log and the error_log /installdir/apache2/logs directory. You can change these files to see the exact error in the application.
The main MySQL log file is created at /installdir/mysql/data/mysqld.log file.
How to increase the allowed size of the uploaded files?
You can modify the following option in the php.ini file to increase the allowed size for uploads:
; Maximum size of POST data that PHP will accept. post_max_size = 16M ... ; Maximum allowed size for uploaded files. upload_max_filesize = 16M
How to disable the WordPress wp-cron.php?
The wp-cron.php script will run once a user visits your site. If you get a lot of traffic, this could be a problem. This cron task is really necessary when you make updates in the blog. You can move this cron script to a system cron task to help in lowering your resource usage on the server.
Disable the wp-cron in /installdir/apps/wordpress/htdocs/wp-config.php file. It is important the location, you can add it just before the database settings.
define('DISABLE_WP_CRON', true);
Then add the cron task process in the system. For example, this cron task will run the wp-cron.php process every hour. You can add it using the following command:
$ sudo crontab -e 0 */1 * * * daemon cd /opt/bitnami/apps/wordpress/htdocs && /opt/bitnami/php/bin/php -q wp-cron.php



Comments