Re: [Radiant] Hosting 0.7.1 site w/ Papperclipped
Brian Gernhardt wrote: I'm working on a website for a client and I'm attempting to find a decent host for them. I'm building the site locally right now, using Radiant 0.7.1, Paperclipped, and Styles 'n' Scripts. I've looked around but it's far too easy to find piles of negative feedback about everyone, and difficult to get an independent review. So I thought I'd ask the people actually using Radiant what they think. The site itself is fairly simple, but we'll need a small pile of e-mail addresses as well. Any suggestions, list? I highly recommend Linode VPS. Granted, its not for everyone, one has to wear his sysadmin hat for that. But it does provide you with freedom to pick what services you're going to run on that box, like your own mail server. Static IP included. Quite affordable. I've heard good things about Media Temple. For shared hosting, my experience is limited to Site5. We had some issues related to fast-cgi setup (doesn't everyone?). Lately, they switched to mod_rails, so I expect it will get better. Their support is quite responsive. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RADIANT_GEM_VERSION not set
Mohit Sindhwani wrote: Saša Babić wrote: Thus, I propose that we put in config/environtment.rb something like: RADIANT_GEM_VERSION = '0.7.1' unless defined? RADIANT_GEM_VERSION I thought be default if nothing is specified, it would use the most recent install of Radiant? Yes, and I think that can be a problem in some cases. Unless for some reason you want to force it to '0.7. 1' if the gem version is not specified. Let's say you have a couple of production installations of Radiant 0.6.9. You hear a new shiny Radiant is out, and you want to try it out. You upgrade your gem, and suddenly your production installations are broken. This is exactly what happened to me. In fact, it doesn't have to be you, your hosting provider could have upgraded the gem without notifying you. I admit, it is easily solved by specifying the RADIANT_GEM_VERSION in config/environment.rb, but you have to know that in advance. Clearly, in this case it would help if your Radiant was locked to the right gem version. I believe there is no compelling reason for the other way around. If you want to try a new version of Radiant, you could always comment out the above line. And nothing breaks. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] RADIANT_GEM_VERSION not set
The instructions for Radiant upgrade point to updating RADIANT_GEM_VERSION (or commenting it out), but it is not set in the config/environment.rb (you have to do it manualy). Yeah, I know, sometimes it helps if you put some effort into reading the instructions. But, in case you do NOT upgrade your existing radiant app, upgrading radiant gem can break it up. When you realize there is something wrong and go back to read the instructions, it might be a bit late. Thus, I propose that we put in config/environtment.rb something like: RADIANT_GEM_VERSION = '0.7.1' unless defined? RADIANT_GEM_VERSION -- Saša ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Which "Ba" ?
Anton Aylward wrote: I don't want to blow away my current application. I'm curious why do you find blowing it away such a problem? Can't you replicate the setup? Just branch* the application (you do use a repository, don't you?), clone the database, and you're set. -- * or copy the radiant dir ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Production Setup using Passenger and Linode
Saša Babić wrote: Its really simple: @mohit & all: I've made a draft page for the Summer Reboot: http://wiki.radiantcms.org/Deploying_your_first_site Someone should, please, do a sanity check on it. Also, english is not native for me, so maybe that should be checked, too. Side note: its kind of comforting to know that its summer on the southern hemisphere. :) ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Production Setup using Passenger and Linode
jason white wrote: hello all, I have downloaded and installed Radiant CMS. I followed the instructions in the handbook, and was able to get the application running using script/server -e production. Now i'm in the process of using Phfusion Passenger to server the application. What are the necessary changes that would need to be made to have the application function? The posts on setting up Radiant with Dreamhost are excellent, but i'm trying to do the same thing with Linode. Its really simple: Given that you have superuser privileges on Linode And that you have installed and configured Apache When you install passenger gem And run passenger-install-apache2-module Then you should see (and follow) the instructions In other words (: $ sudo gem install passenger $ sudo passenger-install-apache2-module ...follow the instructions... Restart the apache. If you happen to be running Arch linux on Linode as I do, then you're also running ruby 1.8.7. In order for Radiant to run under ruby 1.8.7 you need to add[1] at the top of your config/environment.rb: unless ‘1.9′.respond_to?(:force_encoding) String.class_eval do begin remove_method :chars rescue NameError # OK end end end You should also keep in mind that Radiant will now run under Apache privileges, so you'll have to give apache write permission to the cache dir (and everything in it). Again, restart the apache. Or, better, simply run: $ touch tmp/restart.txt (you'll need to create tmp dir, as radiant would not do this for you) Voila. -- [1] http://www.dreamhoststatus.com/2009/01/02/ruby-187-upgrades/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] rubyonrails.org on Radiant
rubyonrails.org runs on Radiant (through Passenger): http://weblog.rubyonrails.com/2008/12/21/mild-refresh-of-rubyonrails-org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] OT: Background colour
john wrote: The "Z-Man" has it backwards. If the user goes out of their way to set a custom background color the site should respect that, the same as with user selected fonts and css and whether images are shown and whether javascript is enabled and whether Flash and Java are available, etc. etc. and so on. As I understand it, the argument is that if you set the color attribute, you should set the background, too. Otherwise, user might pick the background to be the same as your color, thus making the content unreadable. So, its not only about the appearence. Sure, its a minor thing, but I belive there is some merit to it, however small it might seem. On the other hand, if Radiant never adopts this way of thinking, thats fine, too. It is only a minor thing, after all. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] OT: Background colour
Well, maybe not totally off topic, but probably not that important... Jeffrey Zeldman wrote[1] on his blog about "underwear showing" on many sites. In short, not specifying background colour might get you into an awkward situation if a user has some predefined background color in his browser. And Radiant is a bit showing-off in this sense. [1] http://www.zeldman.com/2008/11/07/is-your-websites-underwear-showing/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] looking for portal functionality
Joe E. wrote: Bubble busted, but pain was minimal. :) I'm new to rails but when proper ruby/rails skills are acquired, I shall consider your suggestion. If you choose to go that route, I've just stumbled on something that you might (or not) find useful: Mack framework. Its yet another Ruby web framework with perhaps a bit different goals then those of Rails. From the site (www.mackframework.com): "Mack is a Ruby web application framework that is being built from the ground up to aid in the development of distributed, portal-like applications that have a need for speed. Mack supports best of breed technologies in a modular way." ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Installing extensions
Jan frederik Poulsen wrote: I'm on a mac. Radiant is located in two places on my machine: 1. As "my app" - my specific site: ~/Sites/ and 2. As "the generator" Library/Ruby/Gems/1.8/gems/radiant-0.6.7 Wher are extensions supposed to be installed? In my specifik site of the "original" place? Gems are system wide, although they can be installed locally by a non-privileged user. You should never touch system wide gems, unless you really, really know what you're doing. And even then, better choices can be made. Your app should hold all of its extensions in the local ./vendor/extensions directory. In case of uncertainty, wiki.radiantcms.org may be helpful. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
