[Radiant] htaccess
Hi,
I have been trying to set up htaccess in a certain way for some time now. Is
the following possible?
Given:
Radiant installation: /rails/radiant/NAME
domain: website.com
Subdomain set up to point to NAME: NAME.website.com symlinked to
/rails/radiant/NAME (index.html removed from the subdomain's folder)
Type in NAME.website.com and you go to the Rails/Radiant app, and all the
internal links work properly.
type in website.com/NAME, and you get the app, but it has lost its styling
and Rails/Radiant cannot resolve the links.
type in www.website.com/NAME and you get the public_html directory listing.
What I'd like to be able to do is have www.website.com redirect to the
application at the subdomain NAME.
Here are my htaccess rewrite lines. Like I said, they handle the
subdomain-to-app mapping. I'd like to link www to the app or, in other
words, make the subdomain the 'default' and behave like it is sitting in the
public_html folder. My understanding is that this is possible and quite
common, but I can't find documentation that explains this common
functionality.
.htaccess==
RewriteRule ^$ index.html [QSA]
RewriteRule ^([^.]+)$ $1.html [QSA]
RewriteCond %{REQUEST_FILENAME} !-f
#RewriteRule ^images/.*.(jpg|gif|png|bmp)$ /blank.$1 [NC,L]
#RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
setEnv RAILS_ENV production
RewriteCond %{HTTP_HOST} ^www.website.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.NAME.website.com$ [OR]
RewriteCond %{HTTP_HOST} ^name.website.com$
RewriteRule ^/?$ http\:\/\/website\.com\/NAME\/ [R=301,L]
Feel free to point out my flawed logic or obvious mistakes. It seems to me
that this should be a simple thing to do.
Thanks,
=tom
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org
[Radiant] Capistrano, old release directories and cache
Hi Folks, We are testing our application and I am delighted with how much we were able to put together in a short time. Radiant is really working for us. I just tracked down some strange behavior and am hoping that this is something that folks have encountered before and can help me understand. We use a series of tools to manage our deploys into our target environments, amongst them Capistrano. Cap, as I¹m sure you are aware, creates new directories in the releases folder and updates the symbolic link ³current² to point to the newest release. I just encountered a problem in QA where a controller in the current directory was getting an instance of a model in one of the older release directories. It was clearly apparent because the paths are visible in the stack trace. Because of that, I moved the older directory and did a number of page refreshes to get the current content displayed correctly. What puzzles me the most is that with each install (the ³stuck² version was a few installations back), the mongrel processes are killed, pids are cleaned up, and the processes are re-started. Of course, one aspect of Capistrano is that there is a shared tmp directory between all releases. I checked to see if there were any files sitting in the tmp directory though and all directories and sub directories were empty. Has anyone encountered something like this before? Thanks so much for your time. - Peter ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Has Anyone Fixed Twitter/Mailer Extensions Conflict?
I'm still on 0.8.1. I wonder if that is why it won't work for me. Unfortunately, I can't spare the time to updgrade my server to 0.9 and solve this problem right now. Thanks, John :-) ~ Alexis = On Feb 9, 2010, at 11:48 PM, John Polling wrote: Hi Alexis, I've just finished a site using both extensions and there was no problem at all. I was using Radiant 0.9 and I did tweak the Twitter extension to use the user timeline rather than the search. Not certain if that matters though Regards John Polling twitter: @pollingj On 10 Feb 2010, at 06:15, Alexis Masters alexismast...@gmail.com wrote: Hello All :-) I am working on some sites that require BOTH the Twitter and the Mailer extensions. I ran into an error, and in searching the list for that error, leaned that these two extensions didn't work together as of May 2009. Has anyone managed to get these working together or am I sunk??? ~ Alexis = Alexis Masters, author http://www.alexismasters.com 510 234-0027 On Feb 9, 2010, at 12:57 PM, banane wrote: Relax, Anton. I simply wrote that b/c Sean said others on the list might know the SQL method. On Tue, Feb 9, 2010 at 10:38 AM, Anton Aylward anton.aylw...@rogers.com wrote: banane said the following on 02/09/2010 12:34 PM: In pure SQL it would be: [snip] BTDT. Deperately want to avoid going back! I'm not well versed enough in Rails to know how to do this, ha! Isn't there a sql option in ActiveRecord where you can just push in db- sql and not worry about Rails doing the joins? The whole point was to use the rails _console_ and use the object-relational mapping. If I wanted a SQL solution I wouldn't have asked in a Ruby/Rails/Radiant forum :-) I like the idea of constructs such as Page.find(:all. :conditions .).name as an extrapolation of Page.name This is Object stuff, which is a lot more natural to an natural language user than the half-RPN nature of SQL. SQL is really the assembly code of database programming. The Rails object relational mapping is the HLL. If you love programming in assembly code I'm not going to stop you. But most of the programmers I know use at least C or C++, if not Perl or PHP or Python, and Ruby is one of the more H of the HLLs. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
