I would like to be able to use the OpenShift Wordpress Example to host a wordpress blog for an organization. What I want to do is have it setup like this:
http://www.example.com => a simple index.html with a few links for the organization. Sort of a landing page. This will not be part of the wordpress blog at all.
http://www.example.com/blog => the wordpress blog.
The trouble I've had is trying to get wordpress to be served up from a subdirectory rather than a subdomain or the root domain. I've tried the directions given from Codex. Restarting the server gives me a the following error whenever I move the wordpress install to a /blog subdirectory:
Pushing to ##.....
remote: Stopping PHP cartridge
remote: Waiting for stop to finish
remote: Stopping MySQL cartridge
remote: Building PHP cartridge
remote: Starting application website
remote: Starting MySQL cartridge
remote: Database already configured.
remote: Starting PHP cartridge
remote: Syntax error on line 2 of /var/lib/openshift/523540c05973ca9f4e000418/php/configuration/etc/conf.d/openshift.conf:
remote: DocumentRoot must be a directory
remote: An error occurred executing 'gear postreceive' (exit code: 1)
remote: Error message: Failed to execute: 'control start' for /var/lib/openshift/523540c05973ca9f4e000418/php
remote:
remote: For more details about the problem, try running the command again with the '--trace' option.
To ssh://....
fcd93d5..480ca5d master -> master
updating local tracking ref 'refs/remotes/origin/master'
Completed successfully
I'm not sure what to do to fix this.... Is there anyway I could fix this setup? Or is there a way that I could leave the setup as is but setup my DNS records to have the blog served up from a /blog subdirectory?
I have limited experience here so I'm taking blind stabs in the dark and it's not working too well...
I am able to make it live on a subdomain, but I'd rather not do that because my organization's website lives on a subdomain anyway so it would be like: http://blog.sub.example.com and that's just a lot of dots... Thanks for any pointers!
deployfile to point resources to the new directory. It seemed to be the only place that referenced the $OPENSHIFT_REPO_DIR where it mattered in this context. - kentcdodds