WordPress – Serve WordPress from root of site on Bitnami EC2 Ubuntu image

apache-2.2Wordpress

Running Bitnami's Ubuntu WordPress Image on Amazon EC2. By default the WordPress install is at /wordpress and there is a static index.html file in the root. How do I configure Apache and WordPress to serve from the root instead of /wordpress?

I have tried the instructions on this page: http://digitivity.org/10/how-to-serve-your-wordpress-blog-from-the-root-directory-if-its-installed-in-a-subdirectory without success.

I have tried changing the document root to the folder serving the wordpress content, but that just breaks WordPress.

I know I am missing something simple, but not sure what. Any help would be appreciated.

Best Answer

Try the following:

First of all Log in the wordpress admin panel and change in the “settings” panel the URL.
Stop Apache server: sudo /opt/bitnami/ctlscript.sh stop apache
Edit the following lines in the /opt/bitnami/apache2/conf/httpd.conf file:

...

DocumentRoot "/opt/bitnami/apps/wordpress/htdocs"

...

Directory "/opt/bitnami/apps/wordpress/htdocs"

...

# Include "/opt/bitnami/apps/wordpress/conf/wordpress.conf"

...

Start the server: sudo /opt/bitnami/ctlscript.sh start apache

if you are having trouble saving your changes due to permission problems, use:

:w !sudo tee %

Related Solutions

Configure Apache + Passenger to serve static files from different directory

Problem was a school boy mod_rewrite error - in order for the RewriteRule to be run both the RewriteCond statements above need to be satisfied, which of course they never will be. This was my fault for copying this from a negative condition test and not realising they would have to be separated. Although annoying that I need two RewriteRule statements, this works perfectly:

  RewriteCond /home/user/public_html%{REQUEST_URI} -f
  RewriteRule ^ /home/user/public_html%{REQUEST_URI} [L]
  RewriteCond /home/user/public_html%{REQUEST_URI} -d
  RewriteRule ^ /home/user/public_html%{REQUEST_URI} [L]

How to serve 410 from Apache rather than a 404

    Redirect gone /path/to/resource

Is the correct way to do it. If that's causing errors for you, make sure you have mod_alias loaded in the server.

Best Answer

Related Solutions

Configure Apache + Passenger to serve static files from different directory

How to serve 410 from Apache rather than a 404

Related Topic