I saw a thread for hosting recommendations but I’d like to hear some recommendations for hosts that allow access to httpd.conf (I guess the only way to do this is VPS or Dedicated server?)
My goal is to utilize the contexts in ModX Revo to manage multiple subdomains and possibly multiple domains from within one manager. I was reading the Revo docs and it says that I need to modify httpd conf in order to do this.
I currently have accounts with Bluehost and 1and1. I like Bluehost, but if I’m understanding the docs correctly I can’t setup multiple subdomains under one install with this hosting company since they won’t let me access httpd.conf.
Does anyone have recommendations for the best way to accomplish my goal of finding a host that will allow me to use the context option in Revo for multiple subdomains? Or is there a way to manage multiple subdomains with contexts without modifying httpd.conf?
-matt
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
I haven’t tried to install Revo with multiple subdomains yet, but I wouldn’t think that you should need to modify the httpd.conf file to do this (as long as your host allows you to setup subdomains mapped to subfolders or something similar). Maybe someone Revo-savvy can provide a definitive answer.
OpenGeek will have to give the definitive answer here, but I would think editing .htaccess would be enough, which Bluehost definitely allows.
OR you can do it via CPanel by pointing a domain to a directory, then utilizing the same name in Revo to serve the coming requests.
I havent done it myself, but I think its possible, even in a shared host.
Quote from: BobRay at Sep 16, 2009, 01:57 AM
OpenGeek will have to give the definitive answer here, but I would think editing .htaccess would be enough, which Bluehost definitely allows.
Bob, I checked with OpenGeek and here is his response:
The docs are not accurate then; you can set up contexts and switch to different ones using a plugin OnWebPagePrerender or by modifying your index.php. I’ve described this in the forums, but I’ll have to search for the thread. Please bump the thread if you don’t mind and keep the conversation public.
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
Ok - I finally figured out where I was misunderstanding the docs. On the Revo Docs page where it explains how to create a context for a subdomain it also gives instructions for how to create the subdomain itself. This is what was confusing me. I already had the subdomain created and I thought the Apache instructions had something to do specifically with the contexts when in fact the Apache instructions were only related to creating the domain.
So I simply followed the docs and skipped the Apache instructions (since my subdomain was already setup) and my site works great.
There is one other issue I’m still trying to figure out though. How to use assets from the main site so I don’t have to duplicate images, css files etc.
As it is now, /assets points to subdomain_folder/assets instead of main_modx_folder/assets. Any suggestions?
-matt
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
Quote from: mattcdavis1 at Sep 18, 2009, 06:16 PMThere is one other issue I’m still trying to figure out though. How to use assets from the main site so I don’t have to duplicate images, css files etc.
As it is now, /assets points to subdomain_folder/assets instead of main_modx_folder/assets. Any suggestions?
How about just deleting subdomain_folder/assets and making it a symbolic link to main_modx_folder/assets (assuming you’re on Linux)?
Quote from: ZAP at Sep 18, 2009, 07:14 PM
Quote from: mattcdavis1 at Sep 18, 2009, 06:16 PMThere is one other issue I’m still trying to figure out though. How to use assets from the main site so I don’t have to duplicate images, css files etc.
As it is now, /assets points to subdomain_folder/assets instead of main_modx_folder/assets. Any suggestions?
How about just deleting subdomain_folder/assets and making it a symbolic link to main_modx_folder/assets (assuming you’re on Linux)?
ZAP - I tried implementing your solution but I’m not a really savvy linux guy so I think I did something wrong. Here’s a screencast of what I did (about 2 minutes long) perhaps you can see where I made a mistake?
http://screenr.com/P47
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
Quote from: mattcdavis1 at Sep 18, 2009, 08:20 PM
Quote from: ZAP at Sep 18, 2009, 07:14 PM
Quote from: mattcdavis1 at Sep 18, 2009, 06:16 PMThere is one other issue I’m still trying to figure out though. How to use assets from the main site so I don’t have to duplicate images, css files etc.
As it is now, /assets points to subdomain_folder/assets instead of main_modx_folder/assets. Any suggestions?
How about just deleting subdomain_folder/assets and making it a symbolic link to main_modx_folder/assets (assuming you’re on Linux)?
ZAP - I tried implementing your solution but I’m not a really savvy linux guy so I think I did something wrong. Here’s a screencast of what I did (about 2 minutes long) perhaps you can see where I made a mistake? http://screenr.com/P47
It looks to me as if you just confused your web root and your shell root. By that I mean that /some_dir/assets/ would start at the public HTML root from within a web page, but usually in the terminal you can access your entire user directory. That means that in the shell you might be creating symlinks below your public HTML directory altogether (probably in the root of the server actually, since you seem to have superuser privileges and I don’t know why you’d need those to perform this command unless you were in fact creating them outside of your user directory).
Use the pwd command first to find out the proper full path from within the shell, and then make sure that you use that when you create your symlink.
Quote from: ZAP at Sep 18, 2009, 08:40 PM
It looks to me as if you just confused your web root and your shell root. By that I mean that /some_dir/assets/ would start at the public HTML root from within a web page, but usually in the terminal you can access your entire user directory. That means that in the shell you might be creating symlinks below your public HTML directory altogether (probably in the root of the server actually, since you seem to have superuser privileges and I don’t know why you’d need those to perform this command unless you were in fact creating them outside of your user directory).
Use the pwd command first to find out the proper full path from within the shell, and then make sure that you use that when you create your symlink.
Dude - you rock! That is so freakin’ cool. It’s working great. Thanks!
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
